Discretica
Privacy
How Discretica handles browser-local data, optional sync, and service-worker caching.
none-by-defaultTrackingNo analytics are added by the generator.
6Managed areasScoped browser-local learner data.
backend-proxySync providerDisabled until server env is configured.
2026-06-17UpdatedReview before public production launch.
Analytics
Discretica adds no advertising trackers, analytics SDKs, or tracking pixels in its own code. If the host enables Cloudflare Web Analytics, it is cookieless and aggregate — it never profiles individual visitors.
- The study experience runs without user accounts.
- No cross-site tracking or advertising identifiers are used.
- Any future analytics would be cookieless and privacy-reviewed first.
Payments and Premium access
Premium is optional. When you buy it, checkout and billing are handled by RevenueCat and Stripe, who process your email address and payment details under their own privacy policies. Discretica never sees or stores your card data; only an anonymous purchase id is kept in this browser so your Premium access is recognised on this device.
Browser-local data
Progress, settings, saved records, workspace state, practice attempts, notes, and locale preferences are stored in this browser using scoped localStorage keys.
- learning progress
- practice attempts
- mistake review
- saved notes
- workspace settings
- selected locale
User data controls
The /data route lets users inspect, export, import, and reset generated browser-local data for this app without touching unrelated localStorage entries on the same origin.
Sync and media services
Account sync and media worker proxy routes are disabled until server-side environment variables are configured. When enabled, generated routes require authorization or allow-listed operations, apply rate limits, keep backend tokens server-side, reject backend URLs that fail the generated outbound URL policy, and reject cross-site browser POST signals before parsing request bodies.
Production review
These generated pages are a production-readiness scaffold. Confirm the final company name, support contact, hosting region, payment processor, and any analytics or backend vendors before public launch.