Privacy for family history data

Family data can be personal. This policy keeps the promise simple: collect what the product needs, keep analytics content-free, and make sharing roles understandable.

What We Store

We store the family trees, people, relationships, photos, captions, notes, access grants, contributor drafts, support requests, and audit/version history that users create in the app.

What We Do Not Track

Analytics are anonymous and product-focused. We do not send names, emails, tree IDs, person IDs, captions, photo URLs, object keys, biographies, addresses, or raw family content to analytics.

Sharing And Roles

Owners decide who can view or suggest edits to a family. Contributors and Family Members see only the family data their role allows. Private fields should remain protected by server-side permissions, not only hidden in the interface.

Uploads And Cleanup

Uploaded media can be reused in the same family and may remain while current trees, drafts, pending requests, or retained versions reference it. Unreferenced objects become eligible for cleanup after the configured grace period.

Support Requests

Support requests are connected to your account so you can track replies. You should avoid adding private family content unless it is necessary for the support issue.

Exports And Deletion

Owners can export family data and move families to deleted state before permanent deletion. Versions, audit history, and media cleanup rules may temporarily preserve data for safety and recovery.