Privacy Policy

Effective Date: October 9, 2026 | Last Updated: October 9, 2026

This Privacy Policy explains how Timeslicer Studios LLC (“Timeslicer,” “we,” “us,” or “our”) collects, uses, discloses, and otherwise processes information when you access or use Timeslicer, including our websites and domains (including timeslicer.ai, timeslicer.app, timeslicer.net, timeslicer.org, timeslicer.co, and api.timeslicer.app), our desktop application, and our related browser extensions (collectively, the “Service”).

This Privacy Policy is intended to be read together with our Terms of Service. If you do not agree with this Privacy Policy, do not use the Service. Our Data Usage page is a short visual summary of this policy. If the two ever differ, this policy governs.

1. Key Points About How Timeslicer Works

Timeslicer reads limited information about what is on your screen. It does this for two reasons: to work out what tasks you worked on, and, if you use blocking, to decide whether what you are looking at is a distraction.

Your activity data is stored on your computer, not ours. Your timeline, your task history, and the text Timeslicer captures live in plain files on your machine. They are not synchronized to Timeslicer’s servers. The only exceptions are features you choose to use: the daily recap email, team sharing (which is end-to-end encrypted), and bug reports you send us. Section 2E describes each one.

Text is sent to AI model providers for processing. Processing is not local, even though storage is. Short excerpts are sent to OpenAI to name your tasks and to Google (Gemini) to sort a page into focus or distraction. The providers send back a short label. They are contractually prohibited from training models on your data and delete it after 30 days. Timeslicer does not store it.

What Timeslicer reads. Some sources are on when you install Timeslicer, and some are off until you turn them on:

  • On by default: the name of the app you are using and the title of its window; the title and URL of the browser tab you are actively looking at; up to 500 characters of text from that page; the prompts you type into AI coding assistants; and your local git history.
  • Off until you turn it on: text inside certain desktop apps (such as Slack, Discord, Notion, and Obsidian), and window snapshots on macOS.

Each source is described in Section 2D, and you can turn each one off in the app’s settings.

What Timeslicer does not do. Timeslicer does not log keystrokes, track mouse movement, or record video of your screen. It never saves screenshots. The optional window snapshots feature reads the text on a single image of the front window on your device and discards the image immediately. That image is never saved and never leaves your computer.

Important: on-screen content may contain personal or sensitive information depending on what is displayed. We use safeguards intended to reduce the likelihood of transmitting certain sensitive information, and we exclude certain categories of websites from capture entirely, but we cannot guarantee that personal information will never be processed.

2. Information We Collect

We collect information in the following categories.

A. Account Information

When you create an account or sign in, we collect:

  • Name (if provided through your authentication method)
  • Email address
  • Authentication identifiers (for example, identifiers provided by Google sign-in)
  • Account identifiers and timestamps (for example, user ID, creation time)

B. Subscription and Billing Information

Payments are processed by Stripe. We receive and store limited billing-related data such as:

  • Stripe customer ID and subscription status
  • Billing and payment status metadata (for example, active, past-due, canceled)
  • For team plans, the team the plan belongs to and its number of seats

We do not receive or store your full payment card number. Stripe’s processing of payment information is governed by Stripe’s own terms and privacy policy.

C. User Configuration Data

We store the settings you configure in the Service so they follow you between devices, such as:

  • Focus tasks and goals you enter for blocking
  • Schedules
  • Blocklists and allow lists (including “don’t scan” exclusions)
  • Subjective blocklists and allowlists
  • Customization and strictness preferences
  • Other feature preferences you choose to configure

The work context you write to help Timeslicer label your tasks (“What do you work on?”) is stored only on your device. It is sent to OpenAI with your labeling requests.

D. On-Screen Content and Task Data

Depending on your settings and which components of the Service you have installed, Timeslicer processes the following.

App names and window titles (Desktop App). On by default. The desktop app records the name of the application in focus and, where the operating system makes it available and you have granted the necessary permission, its window title. On macOS this requires the Accessibility permission.

Browser activity (Extensions). On by default when an extension is installed. For the tab you are actively looking at, the Timeslicer browser extension reads the page title, the URL, and up to 500 characters of visible text. The text is scrubbed in the tab before it is sent (see Section 7G). This occurs only in supported browsers where the extension is installed and enabled.

AI coding assistant transcripts (Desktop App). On by default. The desktop app reads the prompts you type into AI coding assistants such as Claude Code, Cursor, Codex, and GitHub Copilot, from the files these tools keep on your computer. Your prompts become part of the text used to label your coding work. Keys, tokens, and other credentials are removed first. You can turn this off in Settings, System (“Include coding assistant history”).

Git history (Desktop App). On by default. The desktop app reads the local history of git repositories on your computer to find when you pushed code, and links each push to the time you spent before it. This information stays on your device. It is never sent to Timeslicer or to the AI providers Timeslicer uses. You can turn this off in Settings, System (“Include code you shipped”).

Text inside desktop apps (Desktop App). Off until you turn it on in Settings, System (“Include app content”). For supported apps (currently Slack, Discord, Notion, Obsidian, Claude, and ChatGPT, plus WhatsApp, OneNote, and Outlook on Windows), the desktop app reads text displayed within the app. This includes direct messages, private channels, group conversations, and the contents of notes. It can include text written by other people. On macOS this also requires the Accessibility permission.

Window snapshots (Desktop App, macOS only). Off until you turn it on in Settings, System (“Include window snapshots”). It also requires the macOS Screen Recording permission. For apps whose text Timeslicer cannot otherwise read, the desktop app occasionally takes a single image of the front window (at most every few minutes, and at most 150 a day). It reads the text on that image on your device and then discards the image immediately. The image is never written to disk and never leaves your computer. Only the extracted text is used, in the same way as other screen text. Timeslicer never records video.

Task data. From the above, Timeslicer derives task records. Each record has a task name, a short written summary, start and end times, active time, and the applications, websites, and links associated with it.

Where this data is stored. All of it is stored locally on your device, in your Timeslicer application data folder (on macOS, ~/Library/Application Support/timeslicer; on Windows, %APPDATA%\timeslicer):

  • Task records and history are stored in a local SQLite database, task-events.sqlite.
  • Captured text is written to an append-only file, logs/task-spans.jsonl. Its surface_text field is the exact text that is sent for labeling.
  • Every outbound labeling request is logged with its time and size in logs/task-inference.jsonl.
  • Supporting files are stored in the same folder. These include the link between captured activity and tasks, your block history, your git push records, synced tickets from connected tools, and a diagnostic error log.

Except as described in Section 2E, none of this data is synchronized to our servers, and we cannot read your tasks, your history, or your captured text. Our Data Usage page shows how to check this yourself.

E. Features That Send Task Data Off Your Device

The following features send some task data off your device. Each one is a feature you choose to use.

Daily recap email. When the daily recap email is on, your app sends that day’s tasks to our servers during the day so the email can be sent even if your computer is closed. This includes task names, summaries, app and site names, times, and active time. At send time, OpenAI writes a short summary of your day and SendGrid delivers the email. After sending, the content is deleted and only a record that the email was sent remains. Content that was never sent is deleted within two days. You can turn the email off at any time.

Team sharing. If you join a team, your app shares an end-to-end encrypted daily summary of your work with the team owner and the managers they add. Timeslicer cannot read it. See Section 7H.

Work tool integrations. If you connect Jira, Linear, GitHub, or Attio, your app signs in to that service and downloads the tickets assigned to you. It stores them on your device. Your sign-in credentials are encrypted on your device and are not stored on our servers. To match your work to your tickets, your task names and summaries are sent to OpenAI together with the keys, titles, statuses, and short description excerpts of your open tickets. Timeslicer does not write to these services.

AI apps you connect. If you connect Claude, Cursor, or another AI app to Timeslicer, that app reads your history from your computer through a local connection. Timeslicer’s servers are not involved. What that app does with your data is governed by its provider’s terms.

Bug reports. If you send us a bug report with diagnostics attached, the report includes the app’s error log and a status snapshot covering the last 48 hours. You can uncheck the diagnostics before sending. Diagnostics can include task names, summaries, and shortened website addresses (the site and the first part of the path). They never include captured screen text, credentials, or full URLs. Bug reports are kept for up to 60 days.

F. Usage Data, Diagnostics, and Analytics

We collect information about how you use the Service, including:

  • App and extension usage events (for example, feature usage, settings changes, blocking actions)
  • Technical data (for example, device type, OS version, app version, language, time zone)
  • Diagnostic and performance data (for example, error events, performance metrics)

This does not include the content of your screen, your captured text, or your task titles and history.

We use PostHog for analytics on the Website and in the Apps. We use Google Analytics and Google Ads on the Website, and cookies for marketing and for attributing UTM parameters to desktop app installs. See Section 8.

G. Communications

If you contact support or otherwise communicate with us, we may collect:

  • Your contact information
  • The content of your message and any attachments you choose to send
  • Support interaction metadata (timestamps, status)

We use SendGrid for transactional emails (for example, confirmations, security messages, daily recap emails, team invitations, and other operational emails) and Loops for marketing emails.

3. How We Collect Information

We collect information:

  • Directly from you when you create an account, configure settings, or contact support
  • Automatically through your use of the Website and Apps (for example, analytics, logs, device and usage data)
  • From third parties you choose to use to sign in (for example, Google sign-in)
  • From our payment processor (Stripe) regarding subscription status and payment outcomes

Screen-derived content is processed on your device and passes through our servers only in transit to AI model providers, as described in Section 7. We do not store it.

4. How We Use Information

We use information for the following purposes.

A. Provide and operate the Service

  • Create and manage accounts
  • Sync settings across devices and the Apps
  • Provide core app functionality and user-requested features

B. Classify content and infer tasks

  • Send page text to Google for distraction classification
  • Send screen-derived text, application names, window titles, page titles, and URLs to OpenAI to name your tasks, write task summaries, classify desktop apps for blocking, write your daily recap, and match your work to your tickets
  • Use classification results to block or allow content according to your settings
  • Use inference results to build your local task history

C. Improve, secure, and maintain the Service

  • Debugging, quality assurance, and performance monitoring
  • Preventing fraud, abuse, and misuse
  • Developing and improving features and reliability

D. Subscription administration

  • Manage subscriptions and access to paid features
  • Provide access to the Stripe customer portal for cancellation and billing management

E. Communications

  • Respond to support requests
  • Send transactional messages (for example, confirmations, security notices, service notices)
  • Send marketing emails about product updates and important changes (you can opt out as described in Section 9)

5. Legal Bases for Processing (EEA, UK, Switzerland and similar jurisdictions)

If you are located in the European Economic Area, the United Kingdom, Switzerland, or another jurisdiction that requires a lawful basis, we rely on:

  • Contract necessity. To provide the Service you request (for example, account functionality, syncing settings, subscription access).
  • Legitimate interests. To secure, maintain, and improve the Service, prevent abuse, and understand product performance, balanced against your rights.
  • Consent. For certain processing where consent is appropriate, including reading text inside desktop applications, window snapshots, reading AI coding assistant transcripts and git history, and joining a team. You can withdraw consent by turning these features off in Settings, leaving the team, or uninstalling the relevant component.
  • Legal obligations. To comply with applicable laws (for example, responding to valid legal requests).

6. How We Share Information

We do not sell personal information.

We share information only as described below.

A. Service providers and processors

We use third-party providers to operate the Service:

  • OpenAI (AI model provider). Receives screen-derived text, application names, window titles, page titles and URLs, coding assistant prompts, your work context, and your team’s context if you are on a team. It uses them to name tasks, write task summaries, classify desktop apps for blocking, write daily recaps, and match work to tickets. Under our terms with OpenAI, this data is not used to train models and is retained for up to 30 days before deletion.
  • Microsoft Azure (AI model hosting). Some requests to OpenAI models are served through Microsoft Azure, which receives the same information as OpenAI for those requests.
  • Google (classification provider). Receives page text (up to 500 characters) and the page’s URL for distraction classification. Under our terms with Google, this data is not used to train models and is deleted after 30 days.
  • Vercel (website hosting and AI request routing). Hosts the Website. Vercel’s AI Gateway also routes our requests to OpenAI and Microsoft Azure. Under our terms with Vercel, the content of those requests is not used to train models and is deleted after 30 days.
  • Supabase (infrastructure and authentication). Manages accounts and stores user configuration data and operational data. It also stores the limited data described in Section 2E: temporary daily recap content, encrypted team summaries, and bug reports. AI requests pass through Supabase-hosted functions in transit and are not stored.
  • PostHog (analytics). Used for analytics on the Website and Apps, subject to configuration.
  • Google Analytics and Google Ads (website measurement and advertising). Used on the Website for traffic measurement and campaign attribution.
  • Stripe (payments). Processes subscription payments and billing.
  • Loops (marketing emails). Used to send marketing emails.
  • SendGrid (transactional emails). Used to send transactional emails such as confirmations, daily recaps, and operational messages.

B. Your team

If you join a team, your daily work summaries are shared with the team owner and the managers they add, as described in Section 7H. If your team owner has added the team’s own OpenAI API key, AI processing of your activity runs on the team’s OpenAI account instead of ours. In that case, the team’s agreement with OpenAI governs that processing. You are told which account is used before you join and whenever it changes.

C. Legal, safety, and compliance

We may disclose information if we believe in good faith that disclosure is necessary to:

  • Comply with law, regulation, legal process, or governmental request
  • Protect the rights, property, or safety of Timeslicer, users, or the public
  • Detect, prevent, or address fraud, security, or technical issues

We cannot disclose your task history or captured screen content in response to a legal request, because we do not have it. We also cannot read encrypted team summaries, because we do not hold the key.

D. Business transfers

If we are involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that transaction, subject to standard confidentiality protections.

7. Screen Content Processing: Details and Safeguards

A. Browser activity (Extensions)

For the tab you are actively looking at, the Timeslicer browser extension reads the page title, the URL, and up to 500 characters of visible text. It scrubs the text in the tab. The text, title, and URL are then sent to OpenAI to label your tasks. The text and URL are also sent to Google to classify whether the page is a distraction. This occurs only within supported browsers where the extension is installed and enabled.

B. Desktop application capture (Desktop App)

The desktop app records the name of the application in focus and, where available and permitted, its window title. It also reads AI coding assistant prompts and, if you turn them on, text inside supported desktop apps and window snapshots, as described in Section 2D. Each captured excerpt is limited to 500 characters.

This text is stored locally on your device and sent to OpenAI for task inference under the terms described in Section 6.

You can stop each kind of desktop capture in Settings, pause all tracking for a set time, or uninstall the desktop application to stop it entirely. While tracking is paused, nothing is recorded.

C. What is stored on your device

  • Task records: a local SQLite database containing task names, summaries, durations, and associated applications and websites.
  • Captured text: logs/task-spans.jsonl, append-only.
  • AI request log: logs/task-inference.jsonl, one line for every labeling request.
  • Supporting files in the same folder, including task links, block history, git push records, synced tickets, and diagnostic logs.

These files are readable by your operating system user account. They are not encrypted at rest beyond the protections your operating system provides. Sign-in credentials for connected work tools and team encryption keys are additionally encrypted with your operating system’s secure storage.

D. What Timeslicer’s servers receive

Timeslicer’s servers do not store your captured text, your task history, your durations, or the list of applications and websites you use. There is no cloud synchronization of task data. Text sent for labeling passes through our servers in transit to the AI provider and is not stored. The only task data we hold is what you choose to send through the features in Section 2E. That data is temporary daily recap content, team summaries we cannot read, and bug reports.

We also hold operational metadata about classification and inference requests (for example, timestamps, request counts, and which account initiated a request). This metadata does not include the content of those requests.

E. What AI model providers retain

OpenAI and Google each receive the text described above, and Vercel routes the requests sent to OpenAI. Under our agreements with all three, your data is not used to train or improve their models, and is deleted after 30 days. The providers return only a short label or summary.

F. Sources that are never captured

Certain categories of websites are excluded before any capture occurs. These include government sites (including .gov domains), health and hospital sites, banking and payment sites, and sign-in and identity sites. They are never turned into activity records. Their text is never stored on your device and never sent to any provider.

Any site you add to your personal “don’t scan” list is excluded on the same basis.

G. Information removed before transmission

For content that is captured, we attempt to remove certain personal information before transmission, including email addresses, payment card numbers, and ID numbers such as US Social Security numbers. For AI coding assistant prompts, we also remove keys, tokens, private keys, passwords, and other credentials.

These safeguards are not foolproof. Depending on what is displayed on your screen, processed content may still include personal information.

H. Teams

Team sharing does not change where your data lives. It adds an encrypted relay of a daily summary of your work.

  • Joining is your choice. You join a team only by entering its invite code yourself. No manager, administrator, or anyone at Timeslicer can add you. Before you join, you see who will be able to see your data and you can preview exactly what will be shared.
  • What is shared. For each day, your app shares task names, a written summary of each block, app and site names, page titles and full URLs, the times each block started and ended, how much of it was active time, and any tickets your work was linked to. Your app shares the last 7 days on a rolling basis, never any day before you joined, and never days with under 30 active minutes.
  • What is never shared. Screenshots, the raw text captured from your screen, and the work you are doing right now.
  • Encryption. Your app encrypts each day’s summary with the team’s public key before anything is sent. Our servers pass the encrypted summary along and delete it after 30 days. We do not hold the key and cannot read it. Only the team owner and the managers the owner approves hold the key. Their apps decrypt the summaries and store them on their own computers.
  • Who can see it. The team owner and up to five managers the owner adds. Before a manager gets access, the owner and the manager confirm a matching code on their screens.
  • What we store unencrypted. To run a team, our servers hold the team’s name and team context, members’ display names, when each member joined and last shared, and manager invitations, including the invitee’s email address.
  • Team AI key. If a team owner adds the team’s own OpenAI API key, we store it encrypted on our servers and use it only for that team’s AI requests. It is never stored on anyone’s computer.
  • Leaving. You can leave a team at any time. Leaving, or being removed, deletes your summaries still waiting on our servers and stops sharing. Summaries the owner’s or a manager’s app already received stay on their computer.

8. Cookies, Tracking, and Analytics

We use cookies and similar technologies on the Website for:

  • Essential operation
  • Analytics, via PostHog and Google Analytics
  • Marketing and advertising measurement, via Google Ads
  • UTM attribution, via a tracking cookie that helps attribute a Website visit to a desktop app install

You can control cookies through your browser settings. Some features may not function properly if cookies are disabled.

9. Your Choices and Controls

You can control the following:

  • Choose what the desktop app reads. In Settings, System, you can turn AI coding assistant transcripts, git history, text inside desktop apps, and window snapshots on or off.
  • Pause tracking. You can pause all tracking for a set time from the app. Nothing is recorded while it is paused.
  • Exclusions and allow lists. You can add websites to your “don’t scan” list to exclude them from capture entirely, and configure allow lists.
  • Daily recap email. You can turn the daily recap email off in Settings.
  • Teams and integrations. You can leave a team, and disconnect a work tool integration, at any time.
  • Stop desktop capture. Uninstall the desktop application to stop all application name, window title, and application text capture.
  • Stop browser capture. Uninstall or disable the browser extension.
  • Delete your local data. You can delete the files described in Section 7C directly from your Timeslicer application data folder.
  • Marketing emails. You can opt out of marketing emails by using the unsubscribe link in the email. You may still receive transactional or operational emails (for example, billing or security notices).
  • Account data deletion requests. You can request deletion of the account and configuration data we hold by emailing us. See Section 11.

10. Data Retention

A. Local data

Captured text, task records, task history, and supporting files remain on your device until you delete them. There is no automatic expiry. You have full and direct control over this data: you can delete it at any time by removing the files described in Section 7C from your Timeslicer application data folder.

We cannot delete this data for you, because we do not have access to it.

B. Data held by AI model providers

OpenAI, Google, and Vercel retain transmitted content for up to 30 days before deletion, and do not use it to train models, as described in Sections 6 and 7E.

C. Server-side data

  • Account and configuration data. Retained while your account is active and as needed for support, compliance, dispute resolution, and enforcing agreements.
  • Daily recap content. Deleted as soon as the email is sent. Content that was never sent is deleted within two days.
  • Encrypted team summaries. Deleted after 30 days, or earlier when you leave or are removed from the team, or when the team is deleted.
  • Bug reports. Retained for up to 60 days.
  • Analytics and operational data. Retained as necessary for product analytics, security, and system integrity, subject to configuration and deletion requests.

11. Your Privacy Rights

A. Access, correction, deletion

You may request access to, correction of, or deletion of the personal information we hold by contacting us at the address in Section 17. We may need to verify your identity before fulfilling requests. We can delete data on request, subject to any legal retention requirements.

For locally stored data, you have full and direct control. You can access or delete it at any time through your filesystem.

B. GDPR and similar rights (where applicable)

If you are located in the EEA, UK, Switzerland, or another jurisdiction with similar rights, you may have the right to:

  • Access your personal data
  • Rectify inaccurate data
  • Request deletion (right to erasure)
  • Restrict or object to processing
  • Data portability
  • Withdraw consent where processing is based on consent
  • Lodge a complaint with a supervisory authority

C. U.S. state privacy disclosures (general)

We do not sell personal information. We do not share personal information for cross-context behavioral advertising in a manner intended to qualify as a “sale” or “share” under certain state laws.

12. International Data Transfers

We are based in the United States and may process and store information in the United States and other countries where our service providers operate. These countries may have different data protection laws than your country. Where required, we use appropriate safeguards for international transfers.

13. Security

We use reasonable administrative, technical, and organizational measures designed to protect information. No system is completely secure, and we cannot guarantee absolute security.

Data stored locally on your device is protected by your operating system’s file permissions and by whatever disk encryption you have enabled. If your device is shared, other users of that device may be able to access Timeslicer data depending on your operating system configuration. Data transmitted between the Timeslicer applications, our servers, and our service providers is encrypted using TLS. Team summaries are also end-to-end encrypted, as described in Section 7H.

14. Eligibility

The Service is intended for adults only. You must be at least 18 years old to use the Service. We do not knowingly collect personal information from individuals under 18.

15. Not Medical or Mental Health Advice

Timeslicer is not a medical device and does not provide medical, psychological, or therapeutic advice. It is not intended to diagnose, treat, cure, or prevent any disease or condition, including ADHD, ADD, or OCD. If you believe you may need professional help, consult a qualified provider.

16. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. The “Last Updated” date above indicates when it was most recently revised. If changes are material, we will provide notice through the Service or by other appropriate means.

17. Contact Us

Timeslicer Studios LLC

30 N Gould St, Sheridan, WY 82801, USA

Email: [email protected]