Privacy

Frontier stores account data and assessment aggregates for the organization you belong to. Warehouse rows and Snowflake passwords stay in the customer environment and are rejected by the ingest API.

Account data

Email, password hash, organization membership, session cookie (`frontier_session`), and audit events for actions taken in the dashboard. Email verification uses a token; production does not send mail from this repository.

Assessment data

Completed runs include metrics, git metadata, validation names, and entity identifiers. When the runner hashes entity IDs, this service stores those hashes and a flag that they are hashed. Organization owners and administrators set how long runs are kept.

Cookies

The session cookie is HttpOnly and scoped to the dashboard. Local development may also set a short-lived cookie that points at the email-verification URL so you can complete signup without SMTP.

Sharing

Data is not sold. Optional error webhooks, if configured by the operator, receive redacted exception summaries without entity IDs or API keys.