Account and session data
For allowlisted testing, the application stores user email, email verification status, session metadata, and current toolkit consent status in Cloudflare D1.
Development privacy placeholder
This page describes the current development implementation. It is not final legal copy.
For allowlisted testing, the application stores user email, email verification status, session metadata, and current toolkit consent status in Cloudflare D1.
The application uses a secure session cookie to keep users signed in. It does not store raw cookie values, raw session tokens, or plaintext IP addresses in the application database. Session tokens and request-derived abuse-control values are stored only as hashes.
The search disclaimer acknowledgement may be remembered in the user's browser localStorage so the same browser does not need to show the gate on every search. This preference is not stored in the application database.
The site uses Cloudflare Web Analytics to measure aggregate visits, page views, referral sources, broad country, device, and browser categories, and page performance. According to Cloudflare, this service does not use cookies or localStorage for analytics, does not fingerprint visitors, and does not collect or use visitors' personal data. To display the site-wide traffic counter, the application retrieves a cached aggregate of page views from the previous 30 days. The application does not receive or store visitor-level analytics records in Cloudflare D1.
The anonymous survey stores broad category responses separately from user accounts and sessions. The application does not store user ID, session ID, email, plaintext IP address, or user agent with survey responses.
The current stack uses Cloudflare Workers, D1, and Cloudflare Email features. Final subprocessor, hosting, retention, and support language still needs legal review.