Privacy Policy
Last updated 25 July 2026 · Hackathon prototype
The short version. We collect the least we can. We never sell anything. We never share with law enforcement, employers, or insurers. Every event we record is visible to you inside the app — there is no hidden log. You can delete everything at any time.
Why privacy is a safety feature here, not a formality
Using alone is the single largest risk factor in a fatal overdose. Any system that makes people feel watched pushes them toward using alone, which makes them less safe, not more. So restraint about data is not a compliance checkbox in this product — it is the thing that keeps the product from backfiring. That reasoning shaped the architecture, and this policy describes the result.
What we store
- Account: username and a salted scrypt hash of your password. We never store your password itself and cannot recover it.
- Profile: the details you enter for your emergency script — address, unit, entry code, cross street, substances, whether you have naloxone. This exists so a 911 script can be read aloud for you.
- Ladder configuration: your tier settings and contact tree.
- Event log: tier changes, what triggered them, and what the system did. Append-only, and fully visible to you at any time.
- Memory Vault: recordings made by your caregivers, and their transcripts.
What we deliberately do not store
- No continuous audio. This build is push-to-talk; the microphone is not always listening.
- No background location. Location is acquired only during a Tier 4 or 5 emergency, for the purpose of telling responders where you are.
- No advertising identifiers, no third-party analytics, no tracking pixels, no social media SDKs.
- No sobriety score. We do not rate you.
Who sees what
Your caregivers see exactly what your ladder configuration permits, and the caregiver interface tells them explicitly what they cannot see, so there is no ambiguity in either direction. Tiers 0 through 3 are yours to control. Tiers 4 and 5 always notify — disclosed at onboarding, stated in the Terms, and repeated here.
The generative layer
Text generation is performed by Google Gemini via OpenRouter. When a generation runs, the relevant prompt content is sent to that provider and is subject to their terms. We do not send your password, your session token, or your full event history. If you would rather nothing left the device, do not use the generative features — the escalation ladder, the emergency flow, and the legal information all work without them, because none of them depend on a model.
Law enforcement, employers, insurers
We do not share your data with any of them. In the United States, substance use disorder treatment records carry confidentiality protections stricter than ordinary health data under 42 CFR Part 2 — a distinct consent regime, partially aligned with HIPAA following the CARES Act but still separate. This prototype is not a covered treatment program, but it is built to be compatible with that posture rather than against it.
Security
Passwords are hashed with scrypt and a per-user salt. Session cookies are HMAC-signed, HttpOnly, and SameSite. API keys live only in the server environment and never appear in a response body or a log line. This is prototype software and has not had a formal security audit; we would rather tell you that than imply otherwise.
Retention and deletion
Data persists until you delete it. Deletion is immediate and total. Delete your data here.
Children
This prototype is not intended for users under 18. Minors and mandatory reporting raise genuinely difficult questions that we did not attempt to solve under hackathon constraints, and we would rather scope out honestly than handle it badly.
Contact
Privacy questions: contact us.