Cookie and local-storage notice

Essential session cookie

sayscope_session is a secure, HttpOnly, same-site session cookie used to keep a verified user signed in. Client-side scripts cannot read it. It expires with the authenticated session or is removed when the user signs out. Disabling it prevents the protected workspace from functioning.

IndexedDB and browser storage

Imported chats and extracted media are cached in IndexedDB on the device. The Android app uses the same site storage inside Android System WebView. Incoming shared content can remain in private app cache for retry across restarts until replaced, evicted by Android or removed with app storage; pending exports are removed after success, cancellation or a subsequent fresh launch. This is product data, not an advertising tracker. New imports can synchronize selected content to the user's account for access on another signed-in device when cloud storage is enabled. Older browser-only chats move only after explicit migration.

Clear uploaded data and Delete account clear account-linked IndexedDB copies on the current browser. SayScope cannot remotely erase an inaccessible or offline device; its copy can be removed only on that device. Legacy browser-only data that cannot safely be attributed to an account is preserved unless the user selects the separate all-local-data action.

Clearing Android app storage or uninstalling the app removes that app's local WebView and private-cache data, but it does not delete the SayScope account or cloud data. Use the account and data deletion page for that request.

Optional analytics and advertising measurement

Only after a visitor selects Allow analytics, SayScope may record privacy-safe first-party activity and load Google Analytics and the Meta Pixel to measure page visits, campaign performance and aggregated website use. It may retain approved campaign parameters and Meta browser/click identifiers across the SayScope website and application. First-party activity may include page paths, clicks, button or field labels, page coordinates, device category, scroll milestones and time on page. It never records text entered into a form. Raw first-party events and attribution records are automatically removed after 90 days. Rejecting optional analytics does not prevent registration, login, payment or workspace use.

After a consented account verifies its email, SayScope may send Meta a completed-registration event from both the browser and server. The server copy can contain a one-way hash of the verified email, approved campaign/browser identifiers, IP address, browser user-agent, the verification page URL without its token, and a random event identifier used to prevent double counting. SayScope does not send imported chats, prompts, filenames, contact names, transcripts, uploaded media, generated documents, plain-text email addresses or payment details to advertising analytics.

Your choice and provider storage

The choice is stored in local browser storage as sayscope_optional_analytics_consent_v1. When analytics is allowed, Google or Meta may set their own identifiers or cookies according to their services and the SayScope configuration. Select Cookie choices at any time to withdraw or change the choice, including Reject optional analytics. Withdrawal stops future SayScope analytics events and prevents the analytics scripts loading on later visits; it does not retroactively erase records already received by a provider.