Skip to content
SSayScopeOpen workspace

Legal information

Cookie and local-storage notice

How SayScope uses essential browser and Android app storage and optional, consent-gated analytics.

Version 2026-10-07 · Updated 7 October 2026

On this page
Essential session cookieIndexedDB and browser storageOptional analytics and advertising measurementYour choice and provider storage

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. When cloud storage is available, new imports synchronize selected content to the user's account only after the user chooses Upload to Cloud; Continue Locally keeps the import on that device. 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 website visitor selects Allow analytics, SayScope may record public marketing-page activity and load Google Analytics and the Meta Pixel to measure public page visits, campaign performance and aggregated website use. It may retain approved campaign parameters and Meta browser/click identifiers for registration attribution. Public-page activity may include page paths, clicks, visible button labels, page coordinates, device category, scroll milestones and time on page. Workspace, billing and administrator activity and authentication form interactions are excluded. Website signup and email verification support only content-free first-party registration events. Raw first-party events, attribution and conversion-delivery records become eligible for cleanup after 90 days. Cleanup runs through hourly application maintenance during service use; after inactivity, removal resumes on the next maintenance run. Rejecting optional analytics does not prevent registration, login, payment or workspace use.

Server-side Meta conversion measurement is currently disabled. If enabled after consent, a completed-registration event 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.

The Android app does not load these optional website measurement tools or record optional first-party marketing events, even if a previous website analytics choice is stored. Its essential session, local conversation storage, account, billing, security and operational usage functions remain available.

Your choice and provider storage

The website choice is stored in local browser storage as sayscope_optional_analytics_consent_v1. When website analytics is allowed, Google or Meta may set their own identifiers or cookies according to their services and the SayScope configuration. Select Cookie choices on the website 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. The Android app leaves any prior website choice unchanged and does not show these optional website controls.

Child safety and safe reporting

About SayScopePrivacyTermsRefundsAcceptable useCookiesAccount deletionChild safetyPAIALegal & contact
Back to top