Effective date: October 24, 2026
Responsible company: Manas Macchina, Inc. d/b/a Legacii
Privacy and grievance contact: privacy@legacii.ai
Current WhatsApp setup uses a private one-to-one conversation. Each storyteller signs in with their own phone, connects WhatsApp in Legacii and sends the first message. Group setup and automated first contact are not currently offered. Maya asks permission before creating derived family memories; the original messages remain in the conversation.
1. What this notice covers
This Policy explains how Legacii collects, uses, discloses, retains, and deletes personal information through its website, checkout, accounts, Maya conversations, WhatsApp integration, family archives, and support. Legacii is a U.S.-based service operated by a Delaware corporation. It primarily markets to U.S. purchasers; Narrators, contributors, and other users may live elsewhere.
The person whose life is being recorded is the Narrator, also called the main Storyteller. A Purchaser pays. Authorized circle members may act as Keepers, contributing Storytellers, or Listeners, as described in the Terms. One person can have more than one role.
2. The Narrator decides
Buying a gift does not consent to participation on another adult's behalf and does not automatically grant access to their stories. The Narrator decides whether to participate and whom to authorize. We maintain billing access separately from story-access permissions.
Information sent in a WhatsApp group is visible to that group's participants regardless of the archive's separate circle settings. Do not share a private story in a group until everyone who should not receive it has left, or use an appropriately supported private conversation.
3. Information we collect and its sources
| Information | Examples and sources |
|---|---|
| Account and contact details | Names, email addresses, purchaser and Narrator phone numbers, language, relationships, verification records, and account preferences provided by you or the person arranging a gift. |
| Purchases and billing | Plan, amount, billing country, payment status, receipts, refunds, renewal consent, and limited payment metadata supplied through Stripe. Payment credentials are handled through the payment provider rather than requested through Maya. |
| Story Content | Messages, voice notes, photographs, and other supported material you or authorized contributors choose to send; biographical details about people, places, experiences, and relationships. |
| Generated and organized material | Transcripts, translations, summaries, titles, tags, timeline entries, and storybook material created to provide the requested archive experience. |
| Permissions and choices | Onboarding responses, consent versions and timestamps, circle membership and roles, access changes, stop requests, and privacy-request records. |
| Communications | Gift introductions, message-delivery information, support correspondence, complaints, corrections, and service notices. |
| Technical and security data | IP addresses, browser and device information, timestamps, account access events, cookies or similar storage, error information, and records needed to operate and secure the Service. |
We receive information directly from you, from Purchasers and authorized contributors, through WhatsApp and other contracted service providers, and from use of our website and accounts. WhatsApp integration does not give Legacii general access to your unrelated private chats or your complete contact list.
Stories can include sensitive details about health, religion, ethnicity, political views, relationships, or other personal experiences. Share only what you want preserved. Do not send passwords, full payment or financial-account numbers, identity documents, or unnecessary sensitive details about others. Where specific consent is legally required, we ask for it separately rather than treating a relative's purchase as permission.
4. How we use information
We use information to create accounts and gifts; verify access; deliver and document onboarding; conduct requested storytelling; transcribe, translate, organize, display, and search archive material; maintain the archive; and carry out permitted sharing, corrections, and exports.
We also use necessary information to process payments and refunds, manage subscriptions, provide support, diagnose service problems, detect misuse, secure accounts, comply with legal obligations, and establish or defend legal claims. Operational review of a reported error may require authorized staff to inspect the affected material; it is not permission to reuse stories for unrelated purposes.
We may send service communications about purchases, access, security, requests, and changes affecting an archive. Promotional communications, if offered, have their own choices and opt-out method. Agreement to storytelling is not a blanket opt-in to advertising.
5. Maya, AI processing, and no training
Maya is an AI storytelling guide, not a human historian. We use AI providers to process relevant messages, audio, and context for functions such as transcription, translation, follow-up questions, and organization. Only the providers and data relevant to a function need to be involved; not every message is necessarily sent to every provider.
Legacii does not use Story Content to train or fine-tune AI models and does not authorize its AI providers to use Story Content for that purpose. Supplying prior messages as context, or organizing an archive so it can be searched, is different from training a model. Service-provider processing can still involve retention for the contracted service, security, or legally required purposes; “no training” does not mean “no processing” or “zero retention.”
We do not sell Story Content or use it for targeted advertising. We do not create a voice clone, synthetic likeness, or posthumous digital replica under the ordinary storytelling consent. Any such future feature requires separate, specific permission.
6. WhatsApp onboarding and communication choices
You may meet Maya through a supported group introduction, start a conversation yourself, or receive a business invitation where the required permission to contact you has already been obtained. Approval of a message template by WhatsApp does not itself provide your opt-in.
Before participation consent, we may receive and use limited contact details, group and sender identifiers, delivery information, the introduction, and your reply to present the notice and record your choice. Ordinary story capture, transcription, and AI story organization begin only after the Narrator affirmatively agrees. If substantive material is sent too early, we limit its handling to what is needed to manage onboarding, discard or isolate it as appropriate, and ask for it again after consent rather than treating early submission as automatic agreement. Technical delivery systems may temporarily receive the material.
You may ask Maya to stop messages or contact support. A stop request is not consent to delete your archive and does not automatically cancel a Purchaser's subscription. Requests explicitly asking to cancel billing or delete data are handled as those requests, not ignored because a particular keyword was not used.
7. Who can receive information
Your authorized circle. People you authorize may receive archive access under their roles. Keepers administer within your permission; contributing Storytellers add material; Listeners view or listen as permitted. Inviting someone may grant archive-level access unless the interface expressly offers narrower controls. You can change or revoke authorization, including through support.
Our service providers. We use AWS for infrastructure, Meta/WhatsApp for messaging, Stripe for payments, and OpenAI, Anthropic, and Sarvam AI for relevant AI and language processing. On the website, we use Google (Google Analytics 4) for analytics, Meta (the Meta Pixel and Conversions API, separate from WhatsApp messaging) for advertising measurement, and Umami for cookieless analytics, as described in the Cookie Policy. See Service Providers. Providers receive information needed for their functions. A provider may also act independently for some activities, such as payment fraud prevention or operating its messaging service, under its own notice and law.
Authorized personnel. Legacii personnel can access Story Content when needed for operations, support, troubleshooting, security, abuse investigation, or legal compliance. This service is not a zero-knowledge vault that prevents all Legacii access.
Legal and protective disclosures. We may disclose necessary information to comply with a valid legal obligation or process, protect rights and safety, investigate fraud or security issues, or respond to a verified rights request. We assess the scope of a request rather than automatically providing an entire archive.
Business changes. Relevant information may be transferred in a merger, financing, reorganization, or asset sale, subject to applicable law and privacy commitments. A transaction does not itself authorize a buyer to train models on Story Content or materially repurpose it.
We do not make family archives publicly searchable. Access controls cannot prevent an authorized person from separately copying or disclosing content, and we cannot recall independently held WhatsApp messages or exported copies.
8. International processing
Legacii's primary cloud hosting is on AWS infrastructure in the United States. Service providers may process information in other countries, including for language processing, support, messaging, or their own legal obligations. Processing locations may differ from where you live.
Contact us for information about relevant processing locations and any applicable transfer safeguards. Your location may give you additional rights; those rights are not removed by our U.S. location or Delaware contract terms.
9. Retention and archives after cancellation
Canceling, receiving a refund, or reaching the end of a paid Capture plan does not by itself delete an archive. Under our current launch policy, existing stories remain available on a read-only basis to the Narrator and the people the Narrator has authorized, without a new storage charge. Paid story-capture and other paid features end when the applicable paid service ends. Permission to view the archive is separate from permission to manage billing.
This is not a promise of permanent free hosting or lifetime access. An archive with no activity by the Narrator or an authorized circle member for 24 consecutive months may be reviewed for deletion. Before deleting an archive for inactivity, we will provide at least 60 days' notice using the contact information we hold. During that period, the Narrator or an authorized archive manager can request continued retention or an export. An archive visit or a confirmed request to keep it counts as activity.
If we change this complimentary-access policy or plan an orderly discontinuation of archive hosting, we will give at least 60 days' advance notice and an opportunity to export existing content. We will not automatically enroll you in a paid storage plan. These notice periods do not prevent earlier action required by law, a valid deletion request, or an urgent security or abuse issue. Keep your contact details current and retain independent copies of irreplaceable material.
Account, billing, consent, security, support, and request records may have different retention needs from an archive. We keep only the records needed for their purpose, such as financial reporting, proof of permission, fraud prevention, support, or a legal claim, and review their continued need. These limited needs are not a reason to keep an entire deleted life-story archive. Legal holds are scoped to the records actually needed.
10. Access, correction, export, and deletion
Contact privacy@legacii.ai to request access to your information, a correction, an export, deletion, or help with a privacy choice. You may also write to our mailing address. Tell us the account or WhatsApp number concerned and what you would like done; do not send identity-document copies unless we determine they are necessary and arrange a suitable method.
We verify identity and authority proportionately to the request. A Purchaser can request their own billing information; that does not entitle them to the Narrator's archive. An authorized agent may need to provide evidence of authority. We may limit an export or request where needed to protect another person's information or comply with law, and explain the reason.
We aim to acknowledge a privacy request within five business days and to complete a verified access, export, correction, or deletion request within 30 calendar days of receiving it. These are service targets, not a reason to delay a request. Applicable legal deadlines control; we will not treat identity verification as automatically restarting a statutory deadline. If more time is lawfully available and necessary, we will explain the reason and timing.
Deletion is reviewed and carried out by our team; it is not an instant automated operation. Once authorized, we remove the relevant data from active systems and request deletion from service providers where appropriate. Residual copies may remain temporarily in restricted backups until those backups expire through their normal rotation. They are not available as an ordinary family archive. If a backup must be restored, we reapply recorded deletion requests before making the affected data available through the Service. We will explain any remaining retention when responding to the request.
Exports are arranged by our team using reasonably available, commonly usable formats for original files and stored text, subject to rights of other contributors and technical availability. We do not require a paid plan solely to request a legally required export or deletion. See Delete My Data for the process and exclusions.
11. Cookies, website technology, and privacy signals
Cookies and similar local storage can support sign-in, account sessions, preferences, security, referrals, and checkout. Hosting and payment providers can also receive technical information through their services. Payment providers may use information across the services they operate for security and fraud prevention. We do not place Story Content into advertising or website-analytics tools.
Our website uses Google Analytics 4 and the Meta Pixel to learn which pages, links, and ads bring families to Legacii, and Umami for cookieless visit counts. Where the law requires it (the European Economic Area, the United Kingdom, Switzerland, and Canada), we ask before Google Analytics or Meta store anything in your browser; elsewhere they are on by default, and you can turn them off with Cookie choices in the website footer. When a purchase is completed, our server reports it to Google Analytics, and, where you have allowed advertising, to Meta with your email address and phone number in hashed form. This is advertising measurement; it does not involve Story Content, and we do not sell Story Content or use it for targeted advertising.
See Cookie Policy for these technologies, the cookies they set, and browser controls. A browser's legacy “Do Not Track” signal does not turn off essential security, account, or payment processing. We treat a Global Privacy Control signal as an opt-out of advertising measurement wherever you are, and where applicable law requires us to honor another opt-out preference signal, we do so for the covered activity. Your browser controls and statutory rights remain available independently of this statement.
12. Rights based on location
Depending on applicable law and its coverage, you may have rights to access, correct, delete, obtain a portable copy, object to or restrict processing, withdraw consent, opt out of covered sale or sharing, limit certain uses of sensitive information, or appeal a refusal. Where applicable, you may complain to the relevant privacy authority. We will not unlawfully discriminate against you for exercising a right.
For processing subject to a law requiring a lawful basis, we rely on the basis appropriate to the purpose: performance of our agreement for requested account and service functions; consent where required for participation, sensitive information, or optional activities; legal obligations for required records; and legitimate interests, where available and appropriately balanced, for security and service administration.
Our privacy team at privacy@legacii.ai also receives grievances from Narrators in India. You may write in the language in which you ordinarily use Legacii; we will arrange appropriate assistance.
13. Children and security
Legacii account use and participation are intended for adults aged 18 or older. Adults may include family memories involving children when they have the necessary rights, but should minimize sensitive identifying details. We do not knowingly solicit account registrations or storytelling participation from children. Contact us if a child has supplied information directly so we can assess and take appropriate action.
We use access restrictions and safeguards intended to protect the information we handle, but no system is perfectly secure. An optional archive passcode adds an access check but does not prevent an authorized person from copying content. See Security & Trust.
14. Updates and contact
We will update this Policy when our practices materially change and show the effective date. For material changes, we will provide notice through the Service or available contact channels and obtain consent where required before a materially new use of information. We will not retroactively remove a no-training commitment merely by editing this page.
Manas Macchina, Inc. d/b/a Legacii
2261 Market Street, STE 67623
San Francisco, CA 94114, United States
Support: support@legacii.ai
Privacy and grievances: privacy@legacii.ai