Privacy policy

A plain-language account of what Tabeerly collects, when private text is decrypted, which processors receive it, and what deletion can and cannot remove.

Tabeerly is not end-to-end encrypted. Authorized service processes must decrypt dream text to generate an AI draft and, when paid review is requested, make it available to the assigned reviewer.

What Tabeerly collects

  • Account data: name, email address, authentication records, preferences, and account status.
  • Dream and context data: the text you submit, intake answers, relationship context, optional information about deceased loved ones, tags, and journal metadata.
  • Interpretation data: AI drafts, source links, review status, reviewer changes, and delivery history.
  • Service and security data: request counts, failures, timestamps, device/network security information, and payment identifiers. Dream text must not be placed in product analytics or routine error logs.
  • Editorial feedback: a source-correction report, its optional supporting reference, workflow status, and reviewer resolution. The form instructs reporters not to include private dream text or unrelated personal information.

How dream content is processed

Tabeerly decrypts the content on its servers when needed to provide the service. The necessary dream text and context are sent to the configured AI processor—currently an Anthropic or OpenAI model—to generate intake questions or an AI draft. Those companies process the request as service providers under their applicable terms and data-processing commitments.

When human review is requested, an authorized reviewer assigned to the relevant tradition may access the dream, context, AI draft, and sources. Review content stays hidden until a reviewer claims the job, and access to an assigned review is recorded without putting dream text in the operational log.

Encryption and access

Dream content, interpretation payloads, and new human-review payloads—as well as reusable relationship and deceased-person context—are encrypted at rest with AES-256-GCM and are encrypted in transit with HTTPS/TLS. Per-user keys are derived by the application from a server-held secret. A keyed hash supports relationship-term upsert without retaining the term in a database-readable column. This protects stored data, but it is not end-to-end encryption: authorized Tabeerly systems can decrypt data to provide the service.

Passwords are hashed rather than stored in plaintext. Access should be limited to the account owner, service processes that need the data, and assigned reviewers. Shared gift links act as access credentials; anyone holding an active link can open the shared interpretation until it expires or is revoked.

Service providers

  • Neon: hosted PostgreSQL database infrastructure.
  • Anthropic or OpenAI: AI inference, depending on the model configured for the service. Requests may include dream text and context.
  • Resend: transactional email delivery, including account verification and password-reset messages.
  • Stripe: active payment, subscription, refund, and billing-portal processing. Tabeerly receives transaction and customer identifiers but does not store full card details.
  • Vercel: web application hosting, delivery, and runtime infrastructure.

Tabeerly does not sell dream content or personal information to advertisers and does not use dream text for advertising profiles.

Retention

  • Registered account data is retained while the account remains active, unless a shorter period is required for a particular record.
  • A protected daily cleanup removes dream and optional profile data from anonymous accounts after 30 days of inactivity. An empty, pseudonymous account shell may be retained when linked payment or subscription records are needed for accounting, disputes, or refunds.
  • Expired verification/reset credentials and old rate-limit records are removed according to operational cleanup schedules.
  • Source-correction records may be retained with their editorial decision trail. Account deletion removes the reporter link and redacts that account's report text and supporting reference; an unsigned reporter can contact Tabeerly about accidental personal information in a report.
  • After account deletion, Tabeerly may retain a pseudonymous local billing shell and transaction identifiers needed for refunds, disputes, tax, and financial reconciliation. Stripe and other processors may also retain records under their own obligations.

Your choices and rights

  • Export the data associated with your signed-in account from the export settings.
  • Request deletion through the account deletion page. Dream content, relationship context, credentials, and profile information are removed. Active subscriptions must first be canceled; minimal pseudonymous billing records may remain for legal, fraud-prevention, payment, dispute, and processor obligations.
  • Revoke active gift links and avoid including optional family or deceased-person context.
  • Contact Tabeerly to request access, correction, portability, restriction, objection, or other rights available in your jurisdiction.

Children and sensitive use

Tabeerly is not designed for children under 13 and should not be used to obtain medical, psychological, legal, or religious rulings. If dream content suggests an immediate safety crisis, Tabeerly may pause interpretation and display support resources; it is not an emergency service.

Contact and changes

Privacy questions and data requests can be sent to [email protected]. Tabeerly aims to acknowledge requests promptly and respond within the period required by applicable law.

Material policy changes will be posted here with an updated date and, where appropriate, communicated to registered users.