Privacy Policy

About you: your email address, and if you signed in with a provider, the name and avatar it gave us. That is the whole account record.

About the people you enter: a name or label, a birth date, a birth time and how sure you are of it, a birthplace with its coordinates, an optional note about where the data came from, and any relationship you record between two of them.

What you write: your notes, the tags on them, and the life events you enter for rectification.

Technical: ordinary server logs, and error reports if something breaks. Birth data is never written to a log.

There is no advertising, no tracking pixels, no third-party analytics following you around the web, and nothing is sold to anybody, ever.

To cast charts and run the techniques you asked for; to keep your workspace between visits; to take payment if you subscribe; and to email you about your account. Birth data is used for nothing else.

If you are in the UK or EU: the lawful basis is performance of a contract with you for the account and calculations, and legitimate interests for keeping the service secure and working. Where you enter data about other people, you are the controller of it and Jade is your processor.

Traffic is encrypted in transit. The database is hosted by a provider that encrypts its storage at rest, so the physical disks are protected. Every table holding your data is isolated at the database level by row-level security, so a mistake in the application cannot return another practice’s records.

What is not done yet: Jade does not currently encrypt birth data at the field level. That means the storage is encrypted, but anyone with legitimate access to the running database — which today means the operator — can read a name and a birth time in plain text. Field-level encryption is a stated commitment in Jade’s own engineering rules and it is being built; it is named here rather than glossed over, because “your data is encrypted” would let you believe something stronger than what is true today.

Jade runs on services that necessarily process some of this data:

• Hosting and database — to run the application and store your workspace.
• Stripe — if you subscribe. Stripe receives your email and payment details; Jade never sees your card number. Stripe never receives birth data.
• Email delivery — for sign-in links and account messages. Receives your email address only.
• Error reporting — receives technical diagnostics. Configured not to receive birth data.

No birth data is sent to any AI or machine-learning service. If that ever changes it will require your explicit, per-workspace consent, asked for separately — not buried in an update to this page.

Export is available on every tier, including the free one, and always will be. Everything Jade holds about any person downloads as a file, whenever you want it. It is deliberately not a paid feature: your data is not leverage.

Deletion is permanent. Deleting a person removes their record and their charts. Closing your account removes the workspace and everything in it. Backups roll off within 30 days.

Depending on where you live you may also have the right to correct your data, object to processing, or complain to a regulator. Ask and it will be handled — there is no form.

Your workspace is kept while your account is open, and deleted when you close it. Server logs are kept for 30 days. Payment records are kept as long as tax law requires, which is typically seven years, and contain no birth data.

Jade is not for people under 16. If you believe a child has created an account, say so and it will be removed.

Changes are dated at the top of this page. Anything that materially widens what Jade does with your data will be announced by email before it takes effect — and if it involves birth data leaving Jade, it will be asked for rather than announced.

Reply to any email from Jade and a person reads it. See also the Terms of Service.