Privacy policy
Last updated: October 20, 2026
This policy describes how Genogram Builder at genogrambuilder.org handles information when you draw, sign in or use account features.
Drawing and saving
You can use the manual editor without an account. With local auto-save enabled, your genograms are stored in this browser. Downloaded exports are files on your device. Signing in does not automatically upload your local genograms.
When you choose to save a project to your account, its contents and project information are stored on our server so you can access them on another device. Genograms may contain sensitive information about other people; include only information you have permission to use.
Google sign-in and account information
If you choose Google sign-in, we receive your Google account identifier, name, email address and available profile picture, together with authentication records. We use this information to create or recognize your account, sign you in and provide account features. We request only basic identity permissions: openid, email and profile. We do not request access to your Gmail, Drive files or contacts.
We do not sell Google user data or use it for advertising or to train AI models. Google sign-in data is used to operate your account, protect the service and respond to support requests. You can revoke the connection in your Google Account's third-party connections settings; this does not by itself delete your Genogram Builder account.
Email accounts also store an email address, account name and a password hash. Session cookies keep you signed in. Local browser storage remembers editor settings and local genograms.
Optional features
If you explicitly submit an AI request, the supplied text, images and relevant diagram context may be sent to the configured AI provider, such as Google Gemini or an OpenRouter model provider. Opening the editor or signing in does not by itself send your genogram to an AI provider. AI features may be unavailable when a provider is not configured.
If you publish to the Community, the information you choose to publish becomes visible to others. Feedback and support requests store the content you submit and may include your account information. When paid checkout is available, Stripe processes payment details; we store subscription and transaction records, rather than full payment card numbers.
Service providers and security
Cloudflare serves the application and stores account and account-project records in D1. Resend delivers account emails. Google handles Google authentication; optional AI and payment providers process the requests you send through those features. These services may process information in countries other than your own.
Hosting and security services process technical information such as IP addresses, request information and errors to deliver and protect the site. Account traffic uses HTTPS. Server-stored account projects are not end-to-end encrypted; local saving and account saving have different storage properties.
Retention and deletion
Account data is retained while your account and saved projects remain active. You can export projects, permanently delete projects from Trash, or delete your account in Studio settings. Account deletion removes the account and its associated account projects. Removing an account does not erase downloaded exports or copies already stored on your devices.
To remove local copies, use the editor's local-data controls or clear this site's browser storage. Deleted records may remain temporarily in service-provider backups. Published copies, security logs and billing records can have different retention requirements; contact us about a specific record.
Questions and updates
Email support@genogrambuilder.org for privacy questions or deletion assistance. You can also use Send feedback in Studio. For questions about Google authorization, the support contact on the Google consent screen is also available. Changes to this policy will appear here with an updated date.