Privacy Policy

Reverie · Alpheta Labs · Last updated 30 September 2026

This policy sets out the categories of personal data Reverie processes, their recipients, retention periods, and how they are deleted.

1. Categories of data

Account. On first launch an account is created against a device identifier (Android ID on Android, identifierForVendor on iOS). No email address or real name is required. A display nickname is optional. If you sign in with Google or Apple, we receive that account's identifier and email address (with Apple, possibly a private relay address), used to recover your account after a reinstall or a change of phone.

Stories and conversations. The story settings and characters you create, and your conversations with AI characters. These live in the app's local database; once you sign in, the same content is also stored on our servers so your other devices can read it.

Images. Cover and character images you generate or upload from your photo library are stored on our servers and served from an unguessable URL.

Gems and purchases. A record of every gem earned or spent. Payments are processed by Google Play or the App Store; we receive the outcome — the product, the number of gems, and a transaction identifier.

Usage. Number of story turns generated, model tier, and token counts, used for billing and capacity planning.

Invitations. If you install from Google Play through a friend's invite link, the invite code in the install referrer is sent to us so we can give both of you gems; we record who invited you.

App activity. When the app is opened and moved to the background, the screens and buttons used (for example completing onboarding, opening the shop, changing model tier), the identifier of the story involved, the model tier selected, and the gem balance at the time. The text of stories, conversations and anything you type is not included. Recorded against your user number and not provided to third parties. You can turn this off in Me → Settings → Help improve Reverie.

Content you submit. Feedback, and the reason you write when reporting someone else's content, sent together with your app version and language.

Crash and error reports. Error message, stack trace, the screen you were on, device model, OS version and app version.

2. Recipients

AI model providers. To generate the next scene, the story's world setting, characters and recent messages are sent to one of the following, depending on the model tier you pick:

• Anthropic (Claude) · privacy policy
• Google (Gemini) · privacy policy
• DeepSeek · privacy policy

Not every tier reaches the model provider directly. On some tiers the request is forwarded by an API service provider we engage, which handles the same text in transit. How the text is handled on arrival is governed by the receiving party's own terms. These requests contain only the story text needed to generate; your account identifier, nickname and device information are not attached.

Image generation. When you ask for a cover or character image, the scene description you write is sent to BytePlus · privacy policy. The returned image is stored by us; your device does not connect to that service directly.

Moderation before publishing. When you publish a story to the plaza, its setting text is sent to a model provider for automated review. This step does not depend on the model tier you pick; the current recipient is DeepSeek.

The plaza. Publishing is voluntary and off by default. What is uploaded is the story's setting only: title, world description, characters, opening scene and tags; conversation history is not included. A published story can be withdrawn at any time from its detail page. Other users who import it receive a copy, unaffected by your later edits.

Otherwise. Apart from the above we do not provide your personal data to third parties, and we do not use advertising identifiers.

3. Retention and deletion

• Stories and conversations (on device) — until you delete the story, or uninstall
• Stories and conversations (server, once you sign in) — until you delete the story, or delete your account
• Images — until you delete your account; retained if someone else uploaded the same image, or it is still used by a published story
• Account, gem ledger, usage — for the life of your account
• App activity — 180 days
• Transaction records — the period required by tax and accounting law; severed from your identity when you delete your account
• Crash reports — until the underlying fault is fixed

Deleting your account. Go to Me → Settings → Delete account. There is a 24-hour cooling-off period, and signing in again within it cancels the request; once it passes, your account and the server-side data associated with you are deleted. If you can no longer open the app, email support@alphetalabs.com with the user number shown on your profile page. Full details are on the account deletion page.

Uninstalling and system backup. Android's automatic backup may already have copied the app's data to your own Google Drive. That copy is controlled by your Google account; uninstalling does not remove it.

4. Internal use

Internal test accounts have a tool that uploads a complete story, conversation included, so a quality problem can be traced. Ordinary user accounts do not have it. Snapshots are deleted once the problem is located.

5. Age

Reverie is for adult readers. We do not knowingly process the personal data of anyone under 18.

6. Security

Traffic between the app and our servers uses HTTPS. Model provider keys are held only on the server. Our database is not exposed to the public internet.

7. Changes and contact

If this policy changes materially we will update the date at the top and note it in the app's release notes.

Alpheta Labs · support@alphetalabs.com