Security
Health data deserves boring, verifiable controls.
HerPattern handles symptom records, which are among the most sensitive things a person can write down. The controls below are enforced in the database and in server code, not only in the interface.
Isolation by default
Every table holding personal or health data enforces row level security, so a record is only readable by the account that owns it or a role explicitly granted access.
Secrets stay server side
External model, transcription, and search services are called from server functions. API credentials are never shipped to the browser and never written into logs.
Pseudonymous research data
Study exports use participant keys derived from a keyed hash. Researchers see coded identifiers and consented fields, not names, emails, or free text notes.
Audit and immutability
Consent records, export requests, and admin actions are written as append only entries. Shared report links are stored as hashes and expire on a fixed schedule.
Responsible disclosure
- 01Send a description of the issue, the affected page or endpoint, and the steps to reproduce it. Use the research enquiry form and mark the subject as a security report.
- 02Do not access, modify, or download data belonging to another account. A proof of concept on your own test account is enough.
- 03Give us a reasonable window to investigate and ship a fix before discussing the issue publicly.
- 04We acknowledge valid reports, keep the reporter updated, and credit them if they want to be named.
Your controls
- Export a full copy of your data in a portable format.
- Withdraw a consent purpose at any time without losing your personal tracking history.
- Delete your account, which removes health records through a server controlled workflow rather than hiding them.
- Revoke a shared report link, which invalidates the stored token hash immediately.