LiveMemoriesAI
Privacy Policy
Version 1.0 · Last updated 19 July 2026
This policy explains, in plain language, how LiveMemoriesAI handles information when a family creates and shares a virtual memorial. We designed the service for a sensitive setting: grief, family history and private conversations.
1. Who is responsible
LiveMemoriesAI is responsible for the personal data processed through this service. For privacy questions or rights requests, use the public Opposition channel. It accepts requests from account holders, invited interlocutors and people who appear in uploaded material.
2. What information we receive
Depending on what you choose to use, we process account details such as email and name; consent records; memorial details; photographs, messages, documents and audio uploaded by a custodian; profile information extracted from those materials; invited interlocutor details; support messages; security and audit data; and public opposition requests. We do not need every category to provide the basic account.
3. Information about people in materials
Uploaded family archives can incidentally contain information about living relatives and friends. We minimise that information, mask identifiers in derived material where possible, restrict access, and do not expose a third party’s private details to an interlocutor who should not receive them. Anyone who appears in the materials can contact us through the Opposition channel.
4. Why we use it
We use information to authenticate accounts, create and operate the requested memorial, process and search materials, keep memories private between interlocutors, provide optional voice features, prevent abuse, answer support and legal requests, maintain security, and demonstrate consent. We do not use memorial conversations to build advertising profiles or engagement rankings.
5. Legal bases
Account and memorial operations are processed to perform the service you request. Security, abuse prevention, tenant isolation and handling a legitimate opposition use our legitimate interests, balanced against the rights of the people involved. Specific voice cloning and other optional features use specific consent. Legal records are retained where a law requires it.
6. Processors, storage and transfers
We use carefully selected infrastructure providers for authentication, hosting, secure storage, messaging and AI processing. Memorial data is stored in the European Union where the service architecture allows. If a provider processes data outside the European Economic Area, we use an applicable transfer mechanism and contractual safeguards, and document the arrangement.
7. Telegram and AI processing
When you choose Telegram, messages pass through Telegram and its systems. Telegram bot chats are not end-to-end encrypted. LiveMemoriesAI sends the minimum information needed to answer within the selected memorial and does not treat the AI output as a statement by the deceased. Synthetic voice is labelled and is never offered as an unrestricted download.
8. How long we keep information
We keep account and memorial data while the account or memorial is active. We delete active content after a valid deletion request within the stated technical period, then backups expire through their normal rotation. Consent and security records may remain for the legal limitation period. Opposition requests are retained for as long as needed to handle, document and defend the decision.
9. Your rights
You can request access, correction, deletion, restriction, objection and a copy of your information where the law provides those rights. You can also withdraw optional consent without affecting earlier lawful processing. Use the Opposition channel and tell us which person and memorial the request concerns. We may ask for proportionate identity or relationship evidence to avoid disclosing information to the wrong person.
10. Complaints and updates
If our response does not resolve your concern, you may complain to the Spanish Data Protection Agency (AEPD) or the authority in your country. We update this policy when the service or law changes, publish the version date at the top, and ask for renewed acceptance when a material change requires it.