Privacy
Last updated 4 October 2026
Who is responsible for what
When a clinician uses jpedigree to record a family history, the clinician and their employing service are the data controller for the clinical content of that pedigree. jpedigree stores and processes it on their instruction — a processor role.
We do not decide what goes into a pedigree, we do not use pedigree content for any purpose of our own, and we do not sell or share it.
What this website collects
This marketing site runs no advertising scripts.
We measure visitor numbers with a privacy-focused analytics service that sets no cookies and does not fingerprint visitors or build a profile across sites. It records aggregate page views, referrers and coarse country-level location.
Cookies
We use two kinds of storage on this website:
- Strictly necessary — your cookie choice itself, kept in your browser’s local storage so we don’t ask again. This is not a cookie and is never sent to us.
- Analytics cookies (optional) — set only if you click Accept in the cookie banner. They let our analytics provider count visits and see which pages are read, from which referrers and from roughly which country. They last up to two years. The lawful basis is your consent.
If you click Reject, or make no choice, no analytics cookies are set. You can change your choice at any time with Cookie settings in the footer; withdrawing consent deletes the analytics cookies.
What the application collects
The application at draw.jpedigree.com is separate from this site and stores:
- Account data — your email address and an authentication identifier. If you sign in with a third-party account, we receive your email address and basic profile, not your password.
- Pedigrees you draw — individuals, relationships, affected status, conditions and any free text you enter.
- Reports and report templates — generated PDFs and your clinic’s branding details.
Special category data
A pedigree records health information about people who are not the account holder — family members who have not signed up and cannot see what is written about them. Under UK and EU data protection law that is special category personal data.
jpedigree does not require patient names or identifiers to work. Pedigrees can be drawn and recurrence figures computed using initials, codes or nothing at all. Whether identifiers may be entered is a decision for your service’s information governance policy, not ours.
Where data is stored
Account data, pedigrees, reports and templates are stored with established cloud infrastructure providers, in data centres located in the European Economic Area. Data is encrypted in transit and at rest.
Some of our service providers, including our website analytics provider, may process data outside the UK and EEA. Where they do, the transfer is protected by appropriate safeguards, such as the European Commission’s standard contractual clauses, the UK International Data Transfer Addendum, or an adequacy decision.
Retention
Pedigrees, reports and templates are retained for as long as the account exists. Deleting a document removes it from your library. To delete an account and everything in it, write to us.
Your rights
If you are in the UK or EU you have rights of access, rectification, erasure, restriction, portability and objection. For pedigree content, exercise these through the clinician or service that recorded it — they are the controller. For your own account data, write to us.
Sub-processors
We use carefully selected service providers for hosting, data storage, authentication, content delivery and website analytics. Each is bound by a data processing agreement and may process data only on our instructions.
A current list of sub-processors is available to customers and their information governance teams on request.