What actually happens
to your data.

Verifiable deletion

Delete a conversation and Aethyro doesn't just remove it from your screen — the database deletes the rows, then builds a receipt describing exactly what was removed and signs it server-side (HMAC-SHA256) with a key that never leaves the database. You get the payload, the signature, and a "Verify" button that independently recomputes the signature to confirm the receipt is genuine and hasn't been altered.

Try it: sign in, delete any conversation, and the receipt modal appears immediately with a working Verify button.

Account & access security

• Row-level security on every table, enforced by the database itself, not just app code — your conversations, memory, and credit history are scoped to your account at the Postgres layer, so a bug in the frontend can't leak someone else's data.
• No standing admin access. Admin dashboard functions check membership in a table with zero client-readable policies — becoming an admin requires a direct database insert, not a hardcoded email or a flag anyone can flip.
• API keys are hashed, never stored in plaintext. A key is shown to you exactly once, at creation. Aethyro's own database only ever holds its SHA-256 hash — if our database were ever read by someone unauthorized, your key still couldn't be reconstructed from it.
• Leaked-password check at signup. Your password is checked against HaveIBeenPwned's breach database using k-anonymity (only a 5-character hash prefix ever leaves your browser — the real password never does) before your account is created.
• HTTPS everywhere, on every request, with no exceptions.

Payments

Checkout is Stripe-hosted. Aethyro's own servers never see, touch, or store your card number — a purchase becomes a credit grant on your account via a signed webhook, and that's the only thing that crosses back into our database.

What your conversations are used for

Messages are sent to Anthropic's Claude API to generate your response, and for nothing else. Anthropic's API terms are a no-training policy on API inputs — your conversations aren't used to train Claude or any other model. Aethyro doesn't sell, share, or otherwise monetize your conversation content.

Infrastructure

The frontend runs on Cloudflare Workers; data, auth, and access control run on Supabase/Postgres. Both are established infrastructure providers Aethyro builds on top of — this page describes what Aethyro itself does with your data on that infrastructure, not a claim about their own certifications.

Found a problem?

If you find a security issue, please email [email protected] with details before disclosing it publicly. Real reports get a real, personal reply — there's one person reading that inbox.