Your information & your choices
Privacy policy
A personal story deserves a clear explanation of how it is handled.
Effective November 16, 2026
We process account information, conversations, stories and the media you choose to provide to operate Ancestor ID. Optional Clara and Echo features share relevant information with service providers, including third-party AI services. Google sign-in does not give us access to your Gmail. You can manage available privacy choices in the app and request account deletion.
1. Who this policy covers
Ancestor ID, LLC provides Ancestor ID. This policy describes how we handle information through ancestorid.com and the Ancestor ID app and related services. Ancestor ID helps people record and organize life stories with Clara and, where available, create an automated Echo using their likeness, voice, and stories. Features are still being developed. A feature’s availability does not change the information-handling explanation provided when you use it.
2. Sign-in and account information
When you choose Sign in with Google, we request the openid and email permissions. Google provides an account identifier and email information, including whether the address is verified. We use these to authenticate you, associate you with your Ancestor ID account, and help return you to your saved information. We do not receive your Google password or request access to your Gmail messages, contacts, Drive files, or calendar through this sign-in.
Our sign-in uses Amazon Cognito. Cognito processes the Google sign-in information, and the app stores session credentials in the device’s Keychain. Our account service associates your authenticated identity with your customer number, profile, saved preferences, and service access. We use Google account information for account operation and support, not to create advertising audiences or train an Echo.
You can review or remove the Google connection in your Google Account connections. Removing that connection or signing out does not itself delete your Ancestor ID account or previously saved stories. Use the in-app Delete Account option or contact us if you also want those deleted.
You can also sign in with Apple or a verified email address. We associate your identifier, email address and profile with your account so you can return to your stories. An Apple relay address can serve as your account email.
3. Stories, recordings & Echo creation
- Conversations with Clara: audio and conversation context are processed by the speech and AI services used for your session so Clara can respond and create a transcript. Saved sessions can include transcripts, your revisions, summaries, selected quotations, and story-progress information.
- Story saving: account-linked transcripts and related story information can be saved to our backend and AWS storage for syncing and recovery. Uploads that have not completed may remain only on the original device.
- Interview audio: the current company archive does not accept uploads of saved Clara interview audio files. Local recordings remain on your device; personal iCloud backup is a separate feature where available and enabled. This distinction concerns archived files, not the audio processing needed to operate a conversation.
- Echo captures: when you create an Echo, its training video includes your voice. That video, face-angle photographs, capture metadata, and display portrait can be saved in our account-linked AWS storage. Face, voice, and story material is processed to create and operate the Echo, including through Tavus and relevant AI providers.
- Display portraits: a front-facing capture may be processed by an image service to produce a themed portrait. This is separate from the original Echo training capture.
- Stories connected to an Echo: the Clara story history connected to your account, including current saved edits, can be processed into the background and knowledge used by your Echo. Transcripts can contain information about other people you mention. Share only information you are comfortable including and are entitled to provide.
Feature-specific explanations and recording agreements accompany capture and processing. This policy does not, by itself, give permission to record another person, create an Echo of them, or publish their story.
When you send a Clara chat, OpenAI processes the text, relevant conversation history and eligible memories to answer you. Your messages and replies can be stored with your account. With story saving enabled, eligible words can become stories you can review and edit. On a Clara telephone call, Twilio uses your phone number to connect the call and carries its audio. OpenAI processes speech and relevant context on the Clara voice route.
If you create an Echo, Tavus may process features of your face and voice, including facial geometry and voiceprints, to create and operate your replica. After you authorize Echo, eligible memories from Clara chats can help it answer questions. Your existing exclusions apply. A profile photo is stored with your account and can be shown to authorized family members.
4. Website visits, interest registration & the demo
If you register interest, we save your email, optional first name, registration source, and the time and version of your agreement to receive launch and availability updates. Contact us to leave that list.
The Annette demo sends microphone audio to Tavus and its conversation technology providers after you choose to connect. Your camera stays off. We request demo calls with recording disabled; this is not a promise that providers retain no processing data. You can mute or end the call.
The website uses a short-lived session cookie for the demo and technical request information to operate the service and limit abuse. Hosting providers may process IP addresses, device/browser information, request times, and operational logs. The interest form uses short-lived hashed request buckets for rate limiting. Service logs and app diagnostics can also record errors and technical status to help us troubleshoot.
5. Why we process information & who helps us
We use information to provide sign-in, interviews, story organization, account recovery, Echo creation and conversations, customer support, service reliability, and the updates you request. Information is processed by providers needed for the feature you use. These include Google for sign-in; Amazon Web Services for authentication, backend services, and account-linked storage; OpenAI for speech, conversation, text, and image features; Tavus for Echo creation and conversations, with Daily and LiveKit software supporting configured audio/video connections; Twilio for telephone connections; Stripe for hosted website payments; email delivery services for gift invitations; and website hosting and delivery services.
Private comparison testing may use Google AI services; this is separate from the ordinary customer Clara route. Providers receive the information needed for their part of the service, rather than unrestricted access to your Google account. Their processing and retention can be governed by their service terms and policies. Information may be processed on servers outside your state or country. An Echo is an automated representation and may produce inaccurate responses; it is not the person’s consciousness or a live conversation with that person.
Authorized operators may need access to account information and service records to provide support, investigate failures, or respond to an access or deletion request. We may also disclose information when required by law or necessary to address abuse or protect the service. Do not put passwords, payment-card details, or other secrets into an interview.
Family Circle uses names, invitation addresses and access records to manage who can use your Echo. We email invitations and account notices. A welcome email can also invite someone to explore Ancestor ID or download the app. Removing Echo access and removing a Family Circle member are separate choices.
Family Circle members can submit questions to the owner’s inbox. We store the question, sender and recipient associations and access context. Eligible questions can help personalize Clara’s conversations.
For website purchases, Stripe collects payment details on its hosted checkout. We receive payment and refund identifiers, order status, amount, purchased offer, account association and service access dates; we do not receive the full card number. For a gift, we also use the recipient email entered by the buyer to send the invitation and require the recipient to verify that exact address before claiming access. We track whether an invitation was accepted by the email provider and whether the recipient claimed the gift; provider acceptance does not prove inbox delivery. If a buyer deletes their account after paying for a gift, we retain the minimal payment, refund and gift records needed to honor that purchase and prevent another account from inheriting the buyer’s order history.
For Apple purchases, we store transaction identifiers, service access dates, call duration and time debits to credit purchases, recognize restores and show your remaining balance. Registered device notification identifiers support notifications. We also process device-admission identifiers and technical records, including session events, error reports, connection timings and response timings, to prevent abuse, operate service balances and investigate reliability problems. These records can be associated with an account, device or session.
The Help guide includes information you can read without sending a question. When you submit a Help question or use an interactive question option, your question, recent Help conversation and relevant guide information may be sent to OpenAI to prepare a reply. This service is available for signed-in users and guests. We retain support operation and security records; guest Help also temporarily retains an encrypted reply for recovery. Avoid including private stories, passwords or payment details in a Help question.
6. Storage, retention & security
We do not use app-origin personal information for cross-company targeted advertising or advertising measurement, or share it with data brokers. Our own welcome and product messages are separate from those activities.
We keep account information and saved story and capture material to operate your account and the features you use. Retention differs by data type: some working files are temporary, while account-linked archives and provider-created Echo resources can remain after a session ends. A temporary file expiring does not mean every account or provider copy has been deleted.
Deleting an item on one device, signing out, or uninstalling the app should not be treated as a request to erase every cloud or provider copy. To request account deletion, open Account in the app, open your account details, choose Delete Account and follow the confirmation steps. Contact us if you cannot sign in or need help. Backup copies, legal obligations, and provider retention may affect how long removal takes; we will explain applicable limits when handling your request.
We use authenticated account access and HTTPS connections for our cloud interfaces. No storage or transmission method can guarantee absolute security, and this service does not promise permanent preservation. Keep your devices and sign-in accounts protected.
7. Your choices
- Pause or end a conversation, skip a question, and use available story-review controls to correct or remove material.
- Review your Clara Talk and Chat choices in Account → Clara permissions. Withdrawing a processing choice is different from deleting previously saved material. You can request deletion using the account deletion controls.
- Control microphone, camera and notification permissions in your device settings. Notifications are optional.
- Manage Family Circle invitations and access in the app. Removing Echo access stops that person’s Echo access; removing a member and deleting your account have different scopes.
- Review or revoke the Google sign-in connection in your Google Account.
- Contact us to request access to, correction of, or deletion of your account information and saved content, or to stop launch emails.
We may need to verify that a request comes from the account holder before disclosing or changing private information. Requests involving another person’s story or account require appropriate authority. Your rights may vary with your location.
8. Children & changes to this policy
The current Echo creation flow requires the person creating it to be at least 18. Ancestor ID is not directed to children under 13. If you believe a child has supplied personal information without appropriate permission, please contact us.
We will update this page as our practices change and show the effective date. We may change the service providers used to operate a feature and will update the provider information in this policy. This does not give blanket permission for new uses of your information. Material changes will be explained through appropriate notices, and we will request additional permission when required before the changed processing begins.
9. Contact Ancestor ID
For privacy questions, account access, corrections, deletion, or removal from the interest list, email support@ancestorid.com. Include enough information for us to locate your account, but do not send your password or sign-in codes.