Account data: your email address, and — if you sign in with Google — the identity Google shares with us (your email and a provider ID). Passwords are stored only as one-way hashes; we never see or store the password itself.

Evidence you write: the notes you record in Vorith, the Areas and Goals you create, and edits you make. This is the core of the product and its most sensitive data — treat it as a private journal, because that is what it is.

Operational data: server logs (request paths, timing, error traces), usage counts (for example, how many Evidence entries you write, used to enforce beta usage caps), and error reports if something crashes.

To run Vorith's core feature: AI analysis of your Evidence. Your entries are sent to AI providers (below) to produce the observations, scores, and recommendations you see. That is the product — there is no analysis without processing your text.

To keep the service working: authentication, security (rate limiting, abuse prevention), debugging, and capacity planning.

We do not sell your data, use it for advertising, or train our own models on it.

Vorith runs on a small set of infrastructure providers. Your data touches only these:

• DigitalOcean — hosts our servers and managed database (encrypted at rest, private networking).
• Anthropic — the language-model provider that analyzes Evidence text you submit.
• Voyage AI — computes text embeddings (numerical representations) of Evidence for similarity search.
• Sentry — receives error reports (stack traces and request metadata) when something breaks.
• Vercel — hosts this web frontend.
• A transactional email provider (planned: Postmark) — delivers security emails such as password resets and verification links.

Each provider receives only what its job requires. AI providers receive Evidence text; the email provider receives your email address; Sentry receives error context, not your journal.

Vorith's data model is append-only by design: editing an Evidence entry creates a new version and preserves the old one, and deleting hides an entry from the product rather than physically erasing the row. We are honest about this: during the closed beta, full physical erasure is not yet implemented.

If you want your account and data removed during the beta, contact us (below) and we will remove your account's data manually. A full self-serve GDPR-grade erasure pipeline is planned before public launch.

Backups are encrypted and retained on a rolling window as part of normal disaster recovery.

You can export or ask questions about your data, request correction, or request deletion by contacting the founder directly: 0nivip.dev@gmail.com. This is a small, founder-run beta — a human reads these.

This policy will change as Vorith approaches public launch (self-serve deletion, formal GDPR processes, a named email provider). Material changes will be announced to beta users by email.