Last updated: October 21, 2026
Still is made by Cadmus Labs LLC. This policy covers our apps, browser extensions, website and support service.
Still removes YouTube Shorts and Instagram/Facebook Reels and blocks the TikTok website for free on supported web surfaces. Blocking needs no account or purchase. Optional sign-in enables free settings sync. On iPhone and iPad, Still works in Safari websites, not native social-media apps.
Still does not collect your browsing history or the content of pages you visit. Access to the supported websites lets Still remove or block the features you select. Your blocking settings can stay on your device, and blocking works without signing in.
Usage data (below) covers how you use Still itself. Still never records which sites, pages, videos, accounts or searches you view, or when you visit a supported website.
Using Still without an account does not mean no information reaches service providers. The Apple app connects to RevenueCat before sign-in, and online requests involve connection information.
RevenueCat documents that customer country can come from a transaction or an IP-derived country, and that it discards the IP used for that derivation. This does not mean all services involved in Still keep no IP logs. See RevenueCat's customer documentation.
We use PostHog's AI features, including its automated "Self-driving" analysis, to review usage events, errors and our public GitHub issues and point out problems with Still. To do this, PostHog passes the usage data described above to AI model providers it contracts with (currently Anthropic, OpenAI and Google, with Microsoft Azure for search). PostHog's data processing terms prohibit those providers from using the data to train or improve their models. PostHog states it cannot yet guarantee that those providers keep no copy of the data they process. See PostHog's AI data documentation and its subprocessor list.
We do not sell your personal information or use it for advertising tracking, and we do not share usage analytics with advertisers or data brokers. We use it only to understand and improve Still. We do not collect browsing history. RevenueCat's purchase analytics are separate from browsing activity. Its only configured integration for Still sends events to our Supabase backend.
Providers may process information outside your country. For example, Resend documents that it stores customer email data in the United States; selecting an email sending region does not change that storage location. See Resend's processing information.
Settings remain on your device while you keep the local app or extension data. A minimal last-synced-account marker remains after sign-out or account deletion to prevent settings from one account being copied into another on a shared device. It is not an IP address or browsing history.
We keep your active account and synced settings until you delete the account. The deletion process and its limits are described below.
Our counter database stores a count, a short time window and a derived identifier for an account, email address or internet connection. It does not store raw IP addresses. Connection identifiers change between windows and are not linked to an account history. Deriving an identifier is a safeguard; it does not necessarily make the record anonymous.
Counters use one-minute or ten-minute windows. With cleanup operating normally, expired counters and their window-specific keys are removed by the end of the window plus up to one minute and five seconds: at most eleven minutes and five seconds in total. An outage can delay cleanup. These periods describe active counter records, not provider logs or backup copies.
Separate service logs can contain IP addresses and request information. Our sign-in verification audit messages contain a time and outcome without recording the IP address. Earlier versions recorded IP addresses; deploying the change did not erase existing logs.
Supabase's Pro plan advertises seven-day log retention. That does not establish the lifetime of separate audit records stored inside the database or guarantee erasure of every underlying copy. Database audit records and separately stored billing events are not covered by the temporary-counter cleanup schedule. See Supabase's plan details and audit storage documentation.
Supabase keeps daily physical database backups for recovery. Our plan provides a seven-day backup history; point-in-time recovery is disabled. Deleting a live record does not selectively erase it from an existing backup. Backup availability is not a guarantee that every underlying copy is erased at that exact deadline. See Supabase's backup documentation.
Resend documents 30-day retention for email and log data on our Free plan and separate seven-day backups. Deleting your Still account does not immediately delete those records. Earlier removal of a specific message can be requested through Resend. These periods do not describe copies in your email account or our support mailbox. See Resend's retention information.
PostHog keeps usage events for one year on our current plan (a paid plan would keep them for up to seven years). Turning off Share usage data stops new events and discards any still waiting on your device, and nothing more is sent. (Version 2.1 makes one brief attempt to record only that sharing was turned off.) It does not delete events already sent. In current versions, turning sharing back on (in Firefox, allowing its permission again) gives that device a new anonymous identifier, so its earlier signed-out events are not linked to the new ones; if you are signed in, the device's new identifier still carries your account email on our server. In Firefox, sharing follows Firefox's "technical and interaction data" permission, which Firefox offers when you install Still; you can also change it in Firefox's add-on settings. The Safari extension follows the Still app's setting. Version 3 uses the Share usage data control without a separate notice prompt; Firefox's own permission controls sharing there. If what Still shares changes, we update this policy and the date at the top. Your sharing choice stays as you set it. Deleting your Still account asks PostHog to delete the records linked to that account, including each device's identifier for it, along with their events. PostHog processes event deletions in weekly batches, and its own logs and backups follow its schedule. Usage from a device that was never signed in is not linked to an account; contact us to have it removed.
Optional Apple purchase analytics uses separate preparation and attribution records on our server. Preparation expires after ten minutes; attribution expires after 90 days and is removed by scheduled cleanup. This does not change how long financial purchase records remain.
Deleting a Still account does not automatically delete its RevenueCat customer identity, aliases, historical purchases, Stripe's payment records for a web purchase or separate backend billing-event records. Our current account-deletion flow sets no automatic expiry for those records. They support retained app identity and historical purchase services. You can contact us about removal. RevenueCat provides a separate customer-deletion operation; it does not erase Apple's underlying store records. See RevenueCat's customer-deletion documentation.
Messages in our Google Workspace mailbox remain until we manually delete them. We do not currently apply an automatic deletion schedule. Deleting a Still account does not delete that correspondence. You can request its deletion by contacting us. Deleting a mailbox message is not an immediate erasure guarantee for every provider copy. Google describes Trash, administrator recovery and any applicable Vault retention separately in its email recovery documentation.
You can use blocking without an account, stop settings sync by signing out, and request a copy of your account data by contacting privacy@stillapp.fit.
Usage sharing starts on in the iPhone and Mac apps and the Chrome extension. Turn it off at any time with Share usage data in Still's settings (in the Still app for Safari on iPhone and Mac), and on the welcome page in newer versions of the Chrome extension. In Firefox it starts off: nothing is sent unless you allow Firefox's "technical and interaction data" permission, offered when you install Still and available afterwards in Firefox's add-on manager.
Choose Delete account in the app's signed-in screen to remove the authentication account, synced settings, account entitlement record and account-linked security counters from our active application database, and to ask PostHog to delete the usage record linked to the account. Temporary connection counters may finish their existing short security window so deleting an account does not reset protection for other people using the same connection.
Deleting your account ends Still Pro access linked to that account and removes the account association from retained purchase records. Apple, Stripe and RevenueCat keep their own purchase and payment records. We retain purchase references needed to match later refunds or disputes; removing the account association does not erase those records or make them anonymous.
Local settings and the account-safety marker can remain on your device. Provider logs, database audit records, backups, email correspondence, RevenueCat history and underlying store records have the separate handling described above. Account deletion does not make all these records disappear immediately or guarantee that historical purchases transfer to a new account.
Contact privacy@stillapp.fit to request access, correction or deletion beyond the in-app process. We may need to verify that the request concerns your information. We will explain any records that cannot be removed through that request and the applicable limitations.
Still's use and transfer of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Still uses and transfers user data only to provide or improve its disclosed single purpose and user-facing features.
Still is not directed at children under 13 and does not knowingly collect their data. Contact us if you believe a child has provided personal information so we can review its removal.
When this policy changes, we will update its date. For privacy questions or data requests, email privacy@stillapp.fit.