Velum Contact

Data Retention Policy

Effective date: Apr 26, 2026
Product: Velum
Owner: Velum
Contact: hello@dreamvelum.com

1. Purpose

This Data Retention Policy explains how Velum retains, stores, and deletes user data. Velum is designed around privacy, local ownership, and user control. Dream data and dream work data are stored locally on the user's device until the user chooses to delete them.

2. Scope

This policy applies to data associated with Velum, including:

This policy does not apply to third-party platforms, app stores, cloud identity providers, analytics providers, or AI model providers except where Velum controls the data sent to those services.

3. Data Categories and Retention

3.1 Dream Data

Examples: dream journal entries, dream titles, timestamps, tags, personal notes, symbols, themes, and any user-entered dream content.

Storage location: locally on the user's device.

Retention period: retained locally until the user deletes the data or removes the app from their device.

Velum does not automatically delete local dream data on a fixed schedule. The user controls retention by editing, deleting, or removing their local app data.

3.2 Dream Work Data

Examples: saved reflections, completed dream work results, generated interpretations, method outputs, bookmarks, and any saved dream-analysis material.

Storage location: locally on the user's device.

Retention period: retained locally until the user deletes the data or removes the app from their device.

Dream work data belongs to the user and remains on the user's device.

3.3 Dream Work Intermediate Steps

Examples: temporary Q&A flow responses, step-by-step prompts, working context, draft reasoning, and temporary generation inputs used to produce a final dream work result.

Storage location: not persistently stored by Velum.

Retention period: not retained by Velum after generation is complete.

Velum may temporarily use user-provided dream content and Q&A flow responses to generate dream work through Claude or another AI model provider. These intermediate steps are used for generation only and are not saved as durable Velum records unless the user explicitly saves the resulting output.

3.4 User Account Data

Examples: email address, account identifier, authentication provider ID, subscription status, account creation date, plan status, app entitlement status, and basic account settings.

Storage location: Velum-controlled backend systems and/or third-party authentication, subscription, or app platform services.

Retention period: retained while the user account remains active.

After account deletion, Velum will delete or de-identify account data within a reasonable operational period, unless retention is required for security, fraud prevention, legal compliance, payment records, dispute resolution, or legitimate business records.

3.5 Payment and Subscription Records

Examples: subscription status, purchase confirmation, renewal status, cancellation status, transaction identifiers, and app store entitlement data.

Storage location: app store platforms, payment processors, and Velum-controlled entitlement systems, where applicable.

Retention period: retained as required by the relevant app store, payment processor, tax rules, accounting obligations, fraud prevention needs, or legal requirements.

Velum does not store full payment card details directly.

3.6 Support Communications

Examples: emails, support requests, bug reports, screenshots voluntarily submitted by the user, and troubleshooting details.

Storage location: support inbox, help desk tool, or Velum-controlled records.

Retention period: retained for as long as needed to provide support, maintain service quality, resolve disputes, investigate bugs, and preserve business records.

Support records may be deleted or anonymized when no longer needed, unless retention is required for legal, security, or operational reasons.

3.7 Operational, Security, and Diagnostic Logs

Examples: crash logs, error logs, security events, authentication logs, abuse-prevention signals, and basic technical diagnostics.

Storage location: Velum-controlled systems and/or third-party infrastructure providers.

Retention period: retained only as long as reasonably necessary for security, debugging, fraud prevention, reliability, and legal compliance.

Velum does not intentionally include dream content or dream work content in operational logs.

4. Local-First Retention Principle

Velum's default design principle is that user dreams and dream work stay on the user's device until the user deletes them.

Velum does not treat dream content as ordinary analytics, training material, or product telemetry. Dream content is personal, sensitive, and psychologically meaningful and is handled with heightened care.

5. AI Generation

Velum may use Claude or another AI model provider to generate dream work outputs.

When the user runs a dream work flow, Velum may send the minimum necessary dream content, user responses, and method context to the AI provider for generation. Intermediate Q&A flow content is used to generate the requested result and is not persistently stored by Velum as a separate record.

Velum does not use dream data or dream work data to train Velum-owned AI models.

Velum's use of third-party AI providers is described in the Privacy Policy, including relevant provider-side retention, processing, and data-use terms.

6. User Deletion

Users may delete their dream data and dream work data from within Velum where deletion controls are provided.

When a user deletes locally stored dream data or dream work data, Velum removes that data from the local app database or local storage.

Deleting the app from the device may also remove locally stored app data, depending on the operating system and user device settings.

7. Account Deletion

Users may request deletion of their Velum account where accounts are supported.

After account deletion, Velum will delete or de-identify account data within a reasonable operational period, except where retention is necessary for:

Account deletion does not necessarily delete records controlled by app stores, payment processors, identity providers, or other third-party services.

8. Backups

If Velum maintains server-side backups for account, subscription, or operational systems, deleted data may remain in encrypted backups for a limited period until backups expire or are overwritten.

Velum does not create server-side backups of local dream data.

Backup restoration is not used to reintroduce deleted user data into active systems except where necessary for security, disaster recovery, or legal compliance.

9. Data Minimization

Velum collects and retains only the data needed to provide the product, maintain security, support accounts, process subscriptions, and improve reliability.

Velum does not collect unnecessary personal data, especially sensitive dream content, psychological reflections, or intimate personal material.

10. Analytics

Velum may collect limited product analytics, such as feature usage, app performance, crash events, or subscription funnel events.

Analytics do not include raw dream content, dream work content, Q&A flow responses, or saved reflection text.

Where possible, analytics are aggregated, minimized, and de-identified.

11. Legal Holds

Velum may preserve certain records if required by law, court order, subpoena, regulatory request, security investigation, or active dispute.

A legal hold may temporarily override normal deletion or retention periods for the specific records subject to the hold.

12. Cloud Sync or Backup Features

Velum is currently a local-first product. Dream data is stored on the user's device and is not synced to Velum-controlled cloud servers.

If Velum introduces cloud sync, cross-device backup, or similar features in the future, those features will clearly disclose what dream data is uploaded, where it is stored, how long it is retained, how deletion works, and whether users can opt out. This policy will be updated accordingly before any such feature launches.

13. Contact

Questions about this policy may be directed to hello@dreamvelum.com.