Respite: Screen Time Control

A gentle pause before distracting websites. Set daily goals, build streaks, and take back your time.

## Name Respite: Screen Time Control ## Short description (132 characters max) A gentle pause before distracting websites. Set daily limits, see where your time goes, and build streaks. ## Description Respite puts a short pause between you and the sites that eat your time, so opening them is a choice instead of a reflex. Pick your sites and a daily limit for each. When you open one, Biscuit the fox shows a brief pause: a question, a breath, a look at your time so far. Then you decide. Go back, or carry on. What you get - A pause before the sites you choose, on any website - Daily limits per site, with a little grace when you are just over - Streaks for days within your limit, and streak freezes for the days you slip - Stats by day, week and month: when you browsed, which sites, and how it compares - Pauses that adapt to you. Respite learns which kinds help you most - Three ways to pause: every time, at smart moments, or against a time budget you set - A lock for when the day's limit is used up, per site or for every site: the site's pages stop loading until midnight, with a "Continue anyway" that gets harder each time you use it - Strict mode: no way around a lock, no snoozing, no extra minutes. Switching it off only takes effect at midnight - A daily limit on YouTube Shorts, Instagram Reels, Facebook Reels and TikTok videos, counted one by one, or blocked altogether - Journey: acorns for every day within your limits, daily quests, badges, streak freezes and a shop for Biscuit - Leagues and friends, if you want them: a weekly league and a board with friends, ranked on consistency, never on raw screen time - One account for your browsers and the Respite phone apps (optional, sign in with Google or Apple): the same limits everywhere, and with the sync subscription from the phone app, time from all your devices together - Wellbeing: a look at the last seven days - Optional reminders, never more than three a day: a morning note, an evening review and news about your streaks - "Go back" takes you to the page you came from. Respite never closes your tabs - Light and dark themes, keyboard friendly, works with screen readers Private by design You don't need an account. Without one, everything stays in your browser and Respite makes no network requests. It records time only on the sites you add. Signing in is optional; it syncs your goals and a daily total per site, never the pages you visit. Anonymous usage statistics are off unless you switch them on. You can export everything Respite has stored, delete it all, or delete your account, at any time. ## Category Chrome: Productivity → Workflow & Planning. Firefox: Productivity. ## Single purpose (Chrome) Respite helps people limit time on websites they choose by showing a pause before those sites and tracking time spent on them against a daily limit. ## Permission justifications (Chrome) | Permission | Justification | |---|---| | Host permission `<all_urls>` | The user chooses which websites to limit; they can be any site. Respite injects its pause overlay only into sites the user has added. | | `tabs` | Reads the URL of the active tab to decide whether it is a site the user has added, and to attribute time to it. | | `webNavigation` | Detects navigations, including in-page (single-page app) navigations, so a pause appears when the user enters a limited site. | | `scripting` | Injects the pause, lock or Shorts/Reels overlay into the limited site, on demand. Registers one small content script for tiktok.com only while the user has TikTok's video limit switched on (its feed does not change the URL per video, so the URL alone cannot count them). | | `declarativeNetRequestWithHostAccess` | When the user has switched on "lock when the limit is reached" for a site and that site's daily limit is used up, a dynamic rule blocks top-level page loads (`main_frame` only) of that site until midnight or until the user overrides the lock. Rules exist only for sites the user chose to lock; there are no static rule sets, no rules for sub-resources, and nothing is redirected or modified. The blocked tab is taken to the extension's own lock page by the background (`tabs.update`), not by a redirect rule, so no page is web-accessible. | | `idle` | Stops counting time when the user is away or the device is locked. | | `alarms` | Periodic timekeeping, daily rollover of streaks at midnight, and 90-day cleanup. | | `storage`, `unlimitedStorage` | Stores the user's sites, limits, sessions and settings locally (IndexedDB and extension storage). | | `identity` | Only for the optional sign-in: `identity.launchWebAuthFlow` opens Google's or Apple's sign-in page (Apple through our API) and returns the result to the extension. `getAuthToken` is not used, so it gives no access to the browser's own Google account. Nothing happens unless the user presses a sign-in button. | | `notifications` (optional) | Requested only when the user turns on "Daily reminders" in Settings, and removed again when they turn it off. Used for at most three local notifications a day (morning note, evening review, goal and streak news). Nothing is pushed from a server. | | `history` (optional) | Requested only if the user chooses the one-time "your last 7 days" estimate during setup; removed again straight after. | Remote code: none. All code is in the package. Analytics uses the GA4 Measurement Protocol with a plain `fetch` from the background; no Google script is loaded. Sync talks JSON to our API (`pawse-api.liveintently.app`, Cloudflare Workers) with `fetch`; nothing it returns is executed. Install warning: none from page blocking. `declarativeNetRequestWithHostAccess` works through the site access Respite already asks for and adds no line of its own to the permissions Chrome lists at install. ## Data usage (Chrome privacy practices form) Sign-in and analytics are both opt-in, but the form asks what the extension *can* collect, so answer for a signed-in user with statistics on: - **Personally identifiable information:** yes (email address, and the name and profile photo Google or Apple share at sign-in; the display name the user picks for leagues and friends). - **User activity:** yes (which Respite features are used, choices on pauses, settings changed; days kept and the journey actions that earn or spend acorns). - **Web history:** yes, in the narrow sense that a daily total per tracked site is synced (minutes, visits, pauses shown, longest visit, under the site's domain or its app id), and analytics reports daily minutes per tracked site, naming only sites from the built-in list. No page URL is ever sent. - Health, financial, authentication information (no passwords or credentials leave the browser; the API's own session token stays on the device), personal communications, location, website content: **no**. - Free text: sync happens only after the user signs in with Google or Apple; data is kept on our server (Cloudflare) until the user deletes the account in the extension. Analytics is collected only after the user switches on "Share anonymous usage statistics", under a random id deleted on opt-out. Signed out with the switch off, the extension makes no network requests (`tests/e2e/chromium/analytics.spec.ts`). - Certify: no sale of data, no use unrelated to the single purpose, no use for creditworthiness. The single purpose still holds: sync and the journey exist to keep the user's limits and progress on their sites the same across their devices. A build made without `VITE_GA4_MEASUREMENT_ID` and `VITE_GA4_API_SECRET` contains no analytics and shows no switch; for such a build the answer to all of the above is "no".