Back to home
Cookie Settings & Transparency
Cookie Policy
Effective Date: September 20, 2026
1. What Cookies We Use
EmmaPrep uses only strictly necessary cookies required to operate our authenticated service:
- Session Authentication: Secure encrypted HTTP-only session tokens to keep you logged in while studying.
- Security & CSRF Protection: Cryptographic tokens to verify that form submissions originate from your authenticated browser session.
- Paddle Checkout: Essential fraud-prevention and transaction cookies required by Paddle Merchant of Record when processing payment transactions.
2. No Third-Party Advertising Cookies
We do not use advertising cookies, cross-site trackers, or behavioral profiling ad networks. Your study activities remain strictly confidential.
3. First-Party Cookieless Web Analytics
EmmaPrep measures overall platform health and page usage using a first-party, privacy-first web analytics system:
- Zero Cookies & Local Storage: We do not place any analytics cookies, tracking pixels, or persistent local storage identifiers on your device.
- Daily Rotating Visitor Hashes: Daily unique visitor counts are estimated using a cryptographic HMAC-SHA256 hash that incorporates a private server salt, the UTC calendar date, your IP address, and browser User-Agent. Raw IP addresses are not stored in our analytics database. As standard across web hosting infrastructure, network providers may maintain temporary access logs. The hash automatically changes at 00:00 UTC each day, preventing cross-day tracking.
- Coarse Technical & Geographic Telemetry: Aggregated reports record coarse geography (country and city provided by serverless edge headers) and client technology (browser, OS, device category).
- Data Retention & Auto-Purging: Detailed event logs are retained for 95 days and automatically deleted thereafter. Long-term aggregates contain only non-identifiable counts.
- Temporary Dual-Measurement: During an initial transition period, @vercel/analytics remains co-mounted alongside our first-party analytics engine to benchmark ingestion fidelity, after which third-party analytics scripts will be removed.