Last updated: 11 June 2026
When you self-host YourPHR, everything it processes — imported FHIR records, uploaded documents, your account, and any provider credentials or tokens — stays entirely within your own deployment. By default the database is encrypted at rest. The application does not “phone home,” send telemetry, or transmit your data to the project or any third party. As the operator, you control storage, backups, encryption, retention, and access.
You may choose to connect a provider or patient-access API to import your records. When you do:
Because a self-hosted instance is often not reachable from the public internet, completing a provider sign-in uses a small public relay. The relay receives only the short-lived authorization code returned by your provider, keyed by an opaque one-time value, holds it in memory for roughly 60 seconds, and deletes it once your instance retrieves it. The relay never receives access or refresh tokens and never sees any health data; your instance exchanges the code for tokens directly with the provider.
Within your instance, your records are used for one purpose: to display and organize your own health information for you. YourPHR does not use your data for advertising, profiling, analytics, model training, or sale, and it shares your data with no one.
You are in control of your data at all times. You can delete individual records, disconnect a provider, or remove your YourPHR instance entirely — doing so deletes the associated data from the only place it lives. Because the project holds no copy of your data, there is nothing for us to delete on your behalf.
This is a static informational site hosted on GitHub Pages. It sets no cookies and runs no analytics or third-party trackers. GitHub may log standard request metadata (such as IP address) to serve the page; see GitHub's privacy documentation. This website never collects health information.
If you run a YourPHR instance that other people use, you act as the operator/controller of that deployment and are responsible for those users' privacy and for any applicable regulations (for example HIPAA or GDPR). This policy describes the software's behaviour, not a service operated by the project.
We may update this policy from time to time. Material changes will be reflected by the “Last updated” date above and published at this URL.
Questions about privacy or the project: open an issue on GitHub.