Private beta, clear choices
App privacy.
Last updated
How the Narravita closed beta handles account information, memories, connected services and your choices.
What this notice covers
This notice covers Narravita’s Android closed beta, its account and optional connected archive services. The beta is for invited adults testing with fictional memories and their own non-sensitive photographs and recordings. Your real sign-in address and technical connection information are still personal information.
The website and waitlist notice covers browsing this site and joining its separate optional mailing list. Joining the waitlist does not create an app account or connect an archive. Paid subscriptions and production release are not enabled by this notice.
Who is responsible
vcreative is responsible for the processing described here. Contact Vincenzo Romeo, Narravita’s creator, designer and developer, for support or privacy requests.
vcreative
Ferdinand Bolstraat 48
1072 LL Amsterdam
The Netherlands
- Chamber of Commerce (CoC)
- 73762326
- VAT number
- NL002514696B43
- Contact
- vincenzo@vcreative.it
Information and why it is used
Account identity includes the sign-in email, verification and session information needed to secure access. Narravita keeps its own account identity, consent choices and access roles.
Material you enter can include writing, voice, photographs, video, documents, transcripts, dates, names, relationships, places, chapters and editions. Optional Goals and Inner Life information is private to the archive owner. Source authorship, permissions, revisions and deletion state are used to keep the correct material available to the correct person. Even a fictional recording can identify its speaker.
The device keeps encrypted archive records and original files. Connecting an archive creates server copies and processes synchronization, invitations and retention requests. Cloud AI receives eligible material only when its relevant processing consent and request permit it. Support uses the message you choose to send. Technical connection, job, delivery and access records help operate and protect these services.
Providing the requested beta service and account controls relies on performance of that service; optional AI and other consent-based processing relies on your specific choice. Security, abuse prevention and responding to support rely on legitimate interests in operating a safe service, subject to your rights. Legal duties may require limited records. Do not submit real health, religious, sexual-life or other sensitive personal information, private information about other people, or children’s data during this fictional-only beta.
Device, cloud and AI choices
A saved device memory is not automatically a verified server backup. The archive owner chooses whether to connect the archive. Sign-in and account checks still contact the identity and account services even when story synchronization is off. Invited contributions use the connected service to reach their intended recipient.
Archive cloud AI and optional Inner Life processing have separate controls. Recording processing also requires its per-record choice. Eligible sources may be sent to the AI processor for transcription, organization, suggested questions or drafting. Suggestions can be wrong; review them before accepting or sharing them. They do not silently become original testimony.
Turning processing off prevents newly authorized work; it does not recall results or files already delivered. Optional notifications use operating-system permission and scheduling. Camera, microphone and file access are requested for the capture action you select. Maps do not request continuous device location tracking.
Services receiving information
- Hetzner: Narravita-controlled application storage runs on a server in Finland, with encrypted off-host recovery copies in Germany. Authorized server processing can read eligible sources.
- Clerk: account identity, verification and session security. Story records, media, relationship graphs, Inner Life information and Narravita permissions are not placed in Clerk user metadata.
- OpenAI: eligible source content and bounded job context when consented cloud AI work is dispatched. Provider retention policies apply to that processing.
- OpenFreeMap: the beta loads map resources directly from this service. Opening a map can disclose your IP address, device/network request information and the viewed map area. Narravita does not attach your memory text or account identifier to these map requests.
- Place search: submitted names, addresses or chosen coordinates go through Narravita’s authenticated location service. Search is sent only when you submit it. Do not search for a real private address in this beta.
- Resend: when transactional delivery is enabled, recipient addresses and the specific service message are used for delivery, bounce and suppression handling. Resend stores service data in the United States even when a different sending region is selected. Ordinary beta invitation email sending is currently off; private links can be shared deliberately. This is separate from the website waitlist.
- Google Play and Android: test enrollment, store distribution, device permissions and services you choose, under their own notices. No app purchase is required for this closed test.
Clerk, OpenAI and, when used, Resend may process information outside the European Economic Area, including in the United States. For information about their processing practices, read Clerk processor terms, OpenAI processor terms and Resend security information. Contact us for information about the safeguards applicable to your information.
How information is protected
Narravita uses encrypted transport, an account-partitioned encrypted device database and encrypted original-media storage. Display, upload and export can create temporary decrypted files. Cloud processing and authorized server work need readable eligible sources: this is not end-to-end encrypted cloud processing.
No advertising based on private memories or sale of personal stories is part of the service. This beta has no configured advertising SDK. Do not send passwords, sign-in codes, recovery keys, full archive exports or private logs in an ordinary support email. Optional visible technical support details include only the app version, build number and operating system.
Retention and deletion
Device-only memories remain until you remove them, clear app data or uninstall. Clearing or uninstalling can destroy the only copy; it does not by itself delete an account or a hosted copy. Connected records remain while needed for your requested archive or retained-original service, unless you use the relevant removal or account-deletion control.
An account-deletion request sets a date 30 days ahead. Processing requires confirmed subscription cancellation. Completion also depends on source, file, account and identity cleanup. Automatic server deletion is currently paused while we review how to protect contributors’ originals. A scheduled request is not confirmation of erasure; contact us to request deletion and check its status. An active recovery claim or failed cleanup can also hold processing. See the deletion steps and limits.
Encrypted recovery backups follow a daily, weekly and monthly recovery-point schedule. Separately retained recovery checkpoints require review and do not all expire automatically. A removed item can remain in isolated recovery copies; these are not active story archives. Ask us about recovery-copy expiry when requesting deletion; removal from the app does not immediately remove every backup.
Hashed deletion markers and limited access, audit, security, delivery and accounting records can remain where needed to prevent resurrection, abuse or unwanted delivery and meet legal duties. Some records retain identifiers and request information; they are not all anonymous. They are distinct from a live story archive. Contact us for the applicable retention and deletion status, including any legal hold.
Your privacy rights
Contact vincenzo@vcreative.it to request access, correction, erasure, restriction or a portable copy, to withdraw optional consent, or to object to processing based on legitimate interests. We may ask for proportionate account verification without requesting your password or sign-in code. Withdrawing consent does not change the lawfulness of earlier processing.
You can complain to the Dutch Autoriteit Persoonsgegevens or your relevant supervisory authority. Privacy requests are handled under applicable law; support and fictional test feedback are not consent to marketing.
Beta changes and contact
The beta’s available features, processors or safeguards may change. Material changes need an updated notice and a fresh choice where required. Paid services are not available in this beta. An app update does not replace your choice about optional processing.
For the beta’s content rules and access limits, read Beta terms. For website-only information, read Website and waitlist privacy.