Trust
Built to hold less.
Harpy is built for clinicians — it is not a system of patient records. Patients never create accounts and never type free text; feedback arrives as structured selections through short-lived links.
Our posture is simple: collect less, keep less. We hold no protected health information. Data is encrypted in transit and at rest, and interactions and analysis are composed from opaque math meant to be resistant to reconstruction by its fundamental format.
Questions, or something you think we should know about? Write to us — frank@harpy.rocks reaches the founders directly. If you find a vulnerability, we want to hear about it and we’ll respond quickly.
Subprocessors
We use a small number of infrastructure providers. We keep this list current as the product grows.
| Provider | What they do for us |
|---|---|
| Vercel | Application hosting |
| Neon | Database |
| Cloudflare | Abuse protection |
| Inngest | Guaranteed event delivery |
| Better Stack | Availability monitoring |
| Loops | Transactional email |
| OpenAI | Automated content-safety screening and no-store generative AI |