Pre-launch draft updated on 10 September 2026
Privacy Notice
This notice explains how the AIVUM GEN service is expected to process personal data when you create and manage biographical timelines, publish memorial pages, use account security features, or contact us.
1. Who controls your data
The legal entity operating AIVUM GEN will be the controller for account, security, billing, support and platform-operation data. Its registered name, address, registration and tax details will be published here before commercial launch.
Privacy enquiries may currently be directed to privacy@aivumgen.com. This contact address must be confirmed before launch.
2. Scope and user responsibility
The account holder who creates and maintains a timeline is its custodian. The custodian is responsible for having a lawful basis and any required permissions to upload, describe and publish information about living people, photographs, documents and other third-party material.
Whether AIVUM GEN acts as an independent controller, joint controller or processor for particular user-uploaded content depends on the factual use of the service and must be confirmed in the final legal review.
3. Data we may process
- Account and profile data, including name, email address, language and account preferences.
- Authentication and security data, including session information, mandatory authenticator-app enrolment and verification status. We do not ask you to send authenticator codes to support.
- Subscription, plan, transaction and invoice information. Full payment-card details are handled by the payment provider rather than stored by AIVUM GEN.
- Timeline data, such as names, dates, relationships, biographies, life events, place names, map coordinates, visibility settings and linked people.
- Uploaded photographs and documents and their descriptive metadata. Initial image upload does not rely on embedded GPS metadata.
- Technical, security and usage records, including IP address, browser/device information, timestamps, authentication events and abuse-prevention logs.
- Support, complaint, content-report and moderation communications.
4. Purposes and legal bases
We process data as needed to provide the contracted service, secure accounts, operate subscriptions, respond to support requests, prevent abuse and comply with legal duties. Depending on the activity, the legal basis may be performance of a contract, compliance with a legal obligation, legitimate interests in security and reliable service operation, or consent where it is specifically requested.
Do not upload special-category or criminal-offence data about a living person unless you have confirmed an appropriate legal basis and the upload is necessary. Consent can be withdrawn prospectively where processing relies on consent.
5. Deceased and living people
The GDPR does not generally apply to deceased persons, but a timeline may also identify living relatives, contributors or other people. Information about those living people remains protected and must be handled lawfully, fairly and proportionately.
6. Service providers and disclosures
The planned service uses Supabase for database and authentication services, Stripe for payments, OpenStreetMap/Leaflet-based mapping with place-search or geocoding services such as Google Places and Nominatim, email delivery services, hosting infrastructure and dedicated media-storage infrastructure. Providers receive only the data needed for their role.
The final notice will identify the active providers, their locations and relevant safeguards. Data may also be disclosed where required by law, to protect users and the service, or in connection with a lawful corporate transaction.
7. International transfers
If personal data is transferred outside the European Economic Area, the operator will use an applicable adequacy decision or another lawful safeguard, such as approved standard contractual clauses. The actual transfer map and safeguards must be completed before launch.
8. Public and private content
A custodian can choose whether supported life events and media are public or private. Published timelines and public items can be viewed by anyone with access to the public page or QR code and may be copied or indexed by third parties despite technical controls. An unguessable URL is not a substitute for a private setting.
9. Retention, deletion and backups
A final category-by-category retention schedule has not yet been approved. Before launch it must define the purpose, legal basis, duration and deletion trigger for account records, timeline content, media, payment records, security logs, support records, derived/search data, backups and cold storage.
Identifiable data about living people will not be retained indefinitely without a lawful basis. Account or content deletion will be propagated through active systems and then backups or cold storage according to the approved deletion cycle, subject to legal obligations and valid exceptions. Statutory accounting records may need to be retained after account closure.
A permanent QR identifier or non-reused public URL does not amount to a guarantee that personal content will be preserved forever.
10. Security
Planned controls include encrypted transport, protected storage, owner-scoped authorization, mandatory app-based two-factor authentication for workspace access, audit and security logging, and restricted administrative access. No online service can guarantee absolute security.
11. Cookies and local storage
The service uses essential browser storage and cookies for authentication, security, language selection and workflow continuity. No advertising purpose is described in the V1 specification. This section and any consent controls must be updated if analytics, marketing or other non-essential technologies are introduced.
12. Your rights
Subject to the GDPR and applicable limitations, you may request access, correction, erasure, restriction, data portability or object to processing based on legitimate interests. You may withdraw consent where consent is the basis. Identity verification may be required before acting on a request.
You may complain to the competent supervisory authority. In Hungary this is the Hungarian National Authority for Data Protection and Freedom of Information (NAIH). Its current contact details are available at naih.hu.
13. Automated decisions and children
The V1 service does not describe decisions producing legal or similarly significant effects solely through automated processing. The service is not designed for independent use by a child who cannot lawfully enter into the agreement; a parent or guardian must act where required by law.
14. Changes and contact
We will publish material changes and, where required, notify account holders. Questions and rights requests may be sent to privacy@aivumgen.com until the final operator contact details are published.