Privacy Policy for DeepWork
Privacy PolicyThis policy explains how DeepWork collects, uses, stores, and shares information for the DeepWork website, account system, billing flows, and browser extension.
Last updated: May 29, 2026
Quick reviewer summary
DeepWork is a focus and website-blocking extension with optional account sync, billing, and Google Calendar sync.
Broad host access is used to let users block websites they choose on any domain. It is not used to read page text, images, form values, passwords, private messages, or emails.
The Chrome Web Store build does not inject content scripts into arbitrary websites and does not collect page content.
Google Calendar is optional and uses read-only calendar scopes only after the user connects Google Calendar.
DeepWork does not sell user data, use browsing data for ads, or use Google Calendar data for advertising or AI model training.
What DeepWork does
DeepWork helps users run focus sessions, schedule website blocklists, set reminders, review where time went, and optionally connect Google Calendar. The extension needs browser permissions and local storage to provide these features.
Information we collect or process
Account information
If you create or connect a DeepWork account, we process account identifiers such as your email address, name, user ID, extension client ID, access status, and plan or trial metadata.Billing and subscription information
Payments are processed by Stripe. DeepWork receives billing status such as plan, trial, subscription, customer, and entitlement metadata. DeepWork does not store full credit card numbers.Authentication information
The extension stores access tokens and credential status needed to keep your account connected, refresh your access status, sync settings, and revoke access when you sign out.Focus, schedule, and reminder data
DeepWork stores focus sessions, active focus timers, Focus Notes, Backlog, Dump, session types, schedules, reminders, notification preferences, focus streak settings, custom messages, and related settings needed to provide the product.Website and browser activity data
DeepWork reads tab URLs and domains to apply user-defined blocklists and redirect blocked navigations to the local DeepWork blocked page. In builds where website-time insights are enabled, it may also store domain-level activity timing, category overrides, background media timing, and related summaries. It does not collect page text, images, form contents, passwords, or messages.Optional Google Calendar data
If you connect Google Calendar, DeepWork processes selected calendar IDs, calendar names, account email/name, event IDs, titles, start and end times, all-day status, and event links so calendar items can appear in the extension and trigger reminders.Analytics and diagnostics
DeepWork may collect limited product events and diagnostics, such as signup, checkout, portal, or page events. PostHog analytics is configured without autocapture and without session recording.Server, security, and rate-limit data
DeepWork APIs may process IP addresses, request metadata, user IDs, and error details for authentication, fraud prevention, rate limiting, security, debugging, and service reliability.How we use information
Provide focus sessions, browser blocking, reminders, notifications, and website-time insights.
Authenticate users and determine trial, premium, lifetime, or admin access.
Process payments, open Stripe checkout or billing portal sessions, and update subscription status.
Sync selected settings across devices when account sync is used.
Display optional Google Calendar events and reminder notifications when calendar sync is connected.
Maintain service security, prevent abuse, debug failures, and improve product reliability.
Browser extension permissions
DeepWork requests the permissions needed for its visible extension features. Host access is broad because users can create blocklists for any website; the permission is used to match and redirect blocked navigations, not to read page contents.
Storage: saves local extension settings, focus state, reminders, blocklists, account connection state, and sync queues.
Alarms: schedules local reminders, focus timers, calendar refreshes, and cleanup jobs.
Notifications: shows reminders, focus notifications, and calendar-related notifications that the user enables.
Identity: supports browser-extension OAuth redirect handling for account and Google Calendar connection flows.
Side panel: displays the DeepWork extension interface inside the browser side panel.
Tabs and webNavigation: inspect the current tab URL and navigation URL so DeepWork can apply user-defined website blocklists.
Declarative Net Request with the <all_urls> host permission: redirects blocked navigations to the DeepWork blocked page when a user-defined rule matches.
DeepWork does not use these permissions to collect page contents, form contents, passwords, private messages, cookies, or full browser history.
Local storage and settings sync
Most extension state is stored in browser storage on your device.
Focus Notes, Backlog, Dump, and the last known Google Calendar snapshot may be backed up through browser extension sync storage when available, so the same browser account can restore recent local extension state after reinstalling the extension.
If account sync is available and enabled through your DeepWork account, synced settings may include blocklists, schedules, reminders, notification preferences, custom messages, enabled calendar IDs, session type preferences, protection settings, theme settings, and website category overrides.
Raw domain-level website activity sessions are kept locally for short-term insights and are not part of the settings-sync payload.
Focus session history is pruned after about 31 days. Website activity history is pruned after about 8 days.
When we share information
We do not sell user data. We share data only as needed to provide DeepWork, process payments, connect optional integrations, operate infrastructure, protect users, or comply with law.
Stripe is used for checkout, billing, and subscription management.
Google OAuth and Google Calendar APIs are used only if you connect Google Calendar.
PostHog may be used for limited product analytics and diagnostics.
Cloud hosting, database, storage, and rate-limiting providers may process data needed to operate DeepWork.
We may disclose information if required for security, abuse prevention, legal compliance, or to protect DeepWork and its users.
What DeepWork does not do
DeepWork does not sell user data.
DeepWork does not use user data to determine creditworthiness or for lending purposes.
DeepWork's use and transfer of Google user data follows the Google API Services User Data Policy, including the Limited Use requirements.
DeepWork does not use Google Calendar data for advertising or to train AI models.
DeepWork does not collect health information.
DeepWork does not intentionally collect personal communications such as emails, texts, or chat messages.
DeepWork does not collect website page content such as page text, images, videos, form values, passwords, or private messages.
Google API and calendar data
Google Calendar sync is optional. DeepWork does not access Google Calendar unless the user starts the connect flow and grants access.
DeepWork requests read-only Google Calendar scopes to list calendars and read selected calendar events.
Calendar data is used only to show calendar items in DeepWork, support reminder timing, and keep the extension timeline current.
DeepWork stores only the calendar and event fields needed for the product, such as calendar IDs and names, event IDs, titles, start and end times, all-day status, event links, and the connected account email/name.
DeepWork's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.
DeepWork does not sell Google user data, use it for advertising, or use it to train AI models.
Your choices and controls
You can sign out of the extension to remove the local access token from the extension.
You can disconnect Google Calendar from DeepWork.
You can clear local extension data from the browser extension settings or by resetting DeepWork data in the extension.
You can request account or data deletion by emailing jiankuang7@gmail.com.
Security and retention
We use reasonable technical and organizational safeguards to protect DeepWork data. No method of transmission or storage is perfectly secure. We keep data only as long as needed to provide DeepWork, comply with legal obligations, resolve disputes, enforce agreements, and maintain security.
Contact
For privacy questions or deletion requests, email jiankuang7@gmail.com.