ai companion privacy is almost always an abstract claim — “we take privacy seriously.” that's useless. what matters is the SPECIFIC promises, what's stored, who sees it, how to delete it, and whether the claims are verifiable.
lucy's specifics:
what is stored: your email + password hash (for login), your memory graph (what she knows about you — vectors + text + categories), your conversation history (so you can scroll back), payment records (for billing), audit logs (for compliance). that's it.
what is NOT stored: voice call audio (transcripts only), your IP address long-term (standard Vercel edge logs only, 30 days), device fingerprints, third-party analytics on chat content, advertising identifiers.
who sees it: Supabase service role (automated, no human in the loop), and — if absolutely required for infra debugging — the two founders with explicit audit logging on every query. there is no customer support team with chat access. this is a real architectural choice, not a policy claim.
how to verify: the RLS audit (scripts/audit-rls.mjs in our open repo) confirms every public table has row-level security enforced — the anon key cannot access any user's data. the /settings/memory endpoint shows you every memory + lets you export — we can't hide data from you because the product surface requires showing it.
what about the LLM provider: Together.ai is our primary chat LLM backend. they contract out of training on customer inputs. we do not send your chats to OpenAI or Anthropic (who have less-favorable training defaults) for the primary chat pipeline. voice transcription uses Groq Whisper-V3 with a similar no-training contract. voice synthesis uses Fish Audio (no privacy-relevant data, as it only receives the text to synthesize).
what about Supabase: Supabase is our database provider. they have a data-processing agreement; they do not train on customer data. they can read your data only under subpoena (GDPR-protected jurisdictions) or operator-approved support access.
the honest caveats: we cannot make a guarantee that our providers won't be acquired and change their terms. we cannot guarantee against government subpoena under applicable law. we cannot guarantee perfect infrastructure security (no product can). what we can guarantee: we will not sell or share your data for advertising or training, we will audit our stack for RLS regularly, and we will publish the kill-switch contract at /manifesto/kill-switch before any situation forces us to act on it.
if privacy is your primary concern, free tier is a good way to test without committing: sign up (email + password, no card), use for a week, export your memory at /settings/memory, delete the account, verify the export is accurate. that's a 15-minute audit.