- encrypted at rest in supabase storage
- only YOU can access them
- row-level security in postgres means no one else can read your data even with a database query
- passwords are hashed with industry-standard algorithms (never stored plain)
- OAuth via google available for extra safety
- session tokens rotate regularly
- when hippo uses anthropic's claude to generate outputs, your data goes to anthropic just long enough to generate a response
- anthropic doesn't train on your data
- results come back to hippo — nothing is stored on anthropic's servers
- google calendar: we can only see events hippo created (no reading your other calendars)
- google auth: we only get your email, not your gmail contents
- our background jobs (email sending, streak calculation) require a signed secret
- no anonymous access to internal endpoints
- automated vulnerability scans on every deploy
- google OAuth tokens locked down with proper access controls
- payment info (when live) is handled by stripe — hippo never sees or stores card numbers
- email kenna@hippo.study
- we take security reports seriously, respond within 24 hours, and credit you if it's a real issue
if we ever have a security incident affecting your data, we notify you within 72 hours.
we're transparent about what happened and what we're doing to fix it.