Privacy will be built in, not added later
TypeSprintly provides optional accounts for a private profile, settings, and minimized activity history. With your permission on the production site, Google Analytics 4 may receive aggregate usage events. A dormant Google AdSense foundation is installed but remains off unless the owner supplies and explicitly enables a valid Production configuration. Typed passages, typed input, names, email addresses, account IDs, certificate IDs, and sensitive URL parameters are never sent as analytics or advertising parameters.
What the site does today
Public pages and tools work without signing in. Supabase stores an authenticated session through its official browser client; guest theme and tool data remain local unless an implemented account setting is explicitly saved.
Optional private accounts
Registration adds a private profile and settings. Only new activity completed while signed in can start cloud history; guest history stays on the device.
Optional aggregate analytics
Google Analytics 4 loads only after analytics consent on the production site. Analytics and advertising choices are independent, and you can change either through Cookie settings.
Advertising is off by default
The site contains a consent-gated AdSense foundation, but no ad code loads without a valid explicitly enabled Production account, an approved placement, and advertising consent. TypeSprintly does not send typed content or account identity as ad parameters.
Account controls
Email confirmation, password recovery, protected routes, private defaults, sign-out, private result history, and offline retry are implemented. Export/deletion processing, public certificates, and shared-test controls remain separate work.
When data handling changes
TypeSprintly will update this notice before introducing material new data-handling features. Material changes will be described in plain language.
For questions about this notice, contact hello@typesprintly.com.