Minimal collection
Privacy
The beta is designed to work without accounts, advertising profiles, or third-party analytics.
What the application collects
The application may record a short allowlisted event such as page view, search used, filter used, or record opened. Events contain an event name, page path, an approved coarse campaign label when present, and server time. After the server successfully creates an acknowledged synthetic research worksheet, it may also record the exact release, data mode, and a server-verification label.
What the application does not record
Its event store does not include names, emails, wallet addresses, raw IP addresses, full user agents, search text, selected record IDs, acknowledgement text, or persistent visitor identifiers. Search analytics records only whether a query was present. A worksheet activation is stored as an identifier-free event that may later be aggregated; it is not a unique visitor, customer identity, or pre-aggregated receipt.
Infrastructure logs
The hosting and network layers may produce limited operational logs needed for security and reliability. Retention and access should remain restricted under the deployment environment's operating policy.
Third parties and cookies
The origin includes only its first-party executable application script, plus non-executable release-bound JSON-LD metadata, and sets no application cookies. The current Cloudflare fallback edge may inject a browser-insights beacon tag; the release's script-src 'self' policy blocks that third-party request before a response is received or the script executes. Following an external link takes you to that site's separate policy.
Future features
Accounts, payments, or wallet features require an updated notice before release. They are not covered by an implication that they already exist.