Privacy Policy
Last updated: 16 November 2026
Ruuya is a dream journal for adults (18+) that can also offer a reflective reading of a dream. This policy explains what leaves your device, why, and for how long. Ruuya is published by an individual developer, Berkan Darbaz, who is the data controller ("we"). Contact: support@ruuya.app.
Person in charge of the protection of personal information (Québec, Private Sector Act s. 3.1), accountable individual (PIPEDA cl. 4.1.1), data protection officer / encarregado (Brazil, LGPD art. 41; Singapore PDPA s. 11; Nigeria NDPA): Berkan Darbaz, support@ruuya.app.
What stays on your device
Your journal, drafts, search, voice transcription and reading aloud with Listen (both done on the device), the list of recurring images in your journal and PDF exports stay on your iPhone. We do not receive them.
Privacy & data → Export encrypted backup makes a file of your journal (dreams, readings and their images), encrypted on your device with a passphrase you choose. It leaves your device only if you save or share it yourself; we never receive the file or the passphrase and cannot open or recover it. Restore from backup reads it back into the journal on this or another device.
Home articles
Home articles are downloaded from ruuya.app. The request carries the language of the articles, but no account, device or journal details, and nothing about what you read; like any web request, it shows your IP address to Cloudflare, which hosts the site. We keep no logs of it.
Listening voice
Listen reads a reading aloud on your device. In some languages it uses a voice that the app downloads once from voices.ruuya.app, after asking you; in others, a voice already on your device. The download carries no account, device or journal details, and nothing about what you listen to; like any web request, it shows your IP address and language settings to Cloudflare, which hosts the voice. We keep no logs of it. Ruuya never sends your dreams or readings anywhere to be spoken.
What we process, and why
| Data | Why | How long |
|---|---|---|
| Account identifier from Sign in with Apple (we do not request your name or email) | To run your account | Until you delete your account |
| An App Attest key: the public key the app creates on your device for your account, and its key id (not a device identifier; our server stores none) | To verify that requests come from a genuine copy of the app, and to limit abuse | Until you delete your account |
| A keyed code derived from your network address (never the address itself) | Rate limits | Up to about a day; Cloudflare's database backups expire within 30 more days |
| The dream text you send for a reading, from which our server removes phone numbers, email addresses and links as soon as it arrives, before it is stored or sent to an AI model; with it, the lens you chose, the dream's date, its time if you set one, its time zone, the languages of the dream and the reading, and a short list of themes our server draws from the text (such as places, feelings and colours, and whether it touches a sensitive subject) | To write the reading and paint its artwork | The text is encrypted and unreadable within 20 minutes and never logged; the rest is kept with the reading for 7 days |
| The reading and artwork | So the app can collect them | 7 days on our servers, then deleted (your copy stays on your device); a record of the request without any of its content (its number, status, times and any error code, such as a refusal's) stays up to 35 days; Cloudflare's database backups expire within 30 more days |
| The dreams you send for a pattern analysis: the text of up to 30 of your recent dreams, with phone numbers, email addresses and links removed, and their dates | To find what runs through them, under the same AI consent as readings | Not stored and never logged; a refused analysis keeps none of the text |
| A dream text our content policy refused (explicit sexual content, self-harm, or other unsafe content) | None for the text, which is not kept. The refusal and its reason are recorded in the content-free safety log below; a reading refused while it was being made also keeps the reason, so the app can tell you; and two daily counts of the texts refused as soon as you send them (one for self-harm and for sexual violence alone, one for the rest) limit repeated attempts | The text is not kept; the reason with a reading, 7 days; the daily counts, about a day |
| A content-free safety log (outcome codes, the language and the AI models used, timings, a pseudonymous account code; never any text or the lens you chose) | Security and abuse prevention | 90 days |
| Technical records of requests and readings (the route, the result and its code, timings, the app's build number, a reading's number and language, the AI models used, a short keyed code for the account; never any text, the lens of a reading or your IP address) | To keep Ruuya working and secure, and to find and fix errors | 7 days at Cloudflare |
| Account and device identifiers at RevenueCat, and purchase history: from your first sign-in with Apple, your account identifier and a device identifier (identifierForVendor); if you buy Premium, your purchase and subscription status and history (product, purchase and renewal dates, refunds) | To tell the app your plan, to provide Premium and its monthly allowance, and to prevent abuse. Held by RevenueCat as our processor; Apple sells the purchase | Our server keeps only whether Premium is active and until when, until you delete your account. RevenueCat deletes your account's record when you delete your account; Apple keeps its own purchase records as long as billing and tax law requires |
| Error reports and performance traces (app version, device model, iOS version, where in the code it happened, technical timings; not linked to your account, never your IP address) | To find and fix crashes and errors, and to measure how fast the app starts and opens screens on about one in fifty launches. Held by Sentry as our processor | At most 90 days |
Legal bases (EEA, UK, Switzerland). Your account identifier, App Attest key, readings and artwork, and your Premium status: performance of our contract with you (GDPR art. 6(1)(b)). Request-limit codes, the content-free safety log, technical records and error reports: our legitimate interest in keeping Ruuya secure, free of abuse and working (art. 6(1)(f)); you may object. The dream text you send and the lens you choose: your explicit consent (arts. 6(1)(a), 9(2)(a)), which you can withdraw at any time under Privacy & data → AI processing; what was processed before stays lawful.
Readings and pattern analyses are produced by AI models that run on Cloudflare's network (Cloudflare Workers AI, as our processor). Your text is not used to train any model. We do not profile you and make no automated decision about you; a reading or pattern analysis is produced only when you ask for it. We do not sell data, show ads or track you, and the app contains no analytics SDK.
Pattern analysis. When you ask Ruuya to find patterns, the redacted text and dates of up to 30 of your recent dreams go to Cloudflare Workers AI, under the same AI consent as readings. Our server does not store them, and a refused analysis keeps none of their text. The list of recurring images in your journal is worked out on your device and stays there.
Purchases. Premium is sold through the App Store, and Apple takes the payment. RevenueCat, Inc. (USA), as our processor, tells the app and our server whether Premium is active. The app first contacts RevenueCat when you sign in with Apple, never before. From then, RevenueCat receives your account identifier and a device identifier (identifierForVendor) so it can tell the app your plan, and your purchase history if you buy Premium. RevenueCat keeps this data until you delete your account. When you sign out or delete your account, the app logs out of RevenueCat: until the app is closed, its RevenueCat SDK runs as a new anonymous customer, without your account identifier; RevenueCat receives that customer's random identifier with the device identifier, and deleting your account does not delete that anonymous record. After a restart the app does not contact RevenueCat until you sign in again. We never receive your payment details. RevenueCat's revenue reports cover purchases only.
Error reports and performance. When the app crashes, freezes or runs into an error, it sends a technical report to our processor Functional Software, Inc. (Sentry, USA). On a sample of launches (about one in fifty), it also sends routine performance traces and profiles that measure how fast the app starts and opens screens. Both carry the app version, device model, iOS version, where in the code something happened and technical timings, and are not linked to you. They never contain your dreams, your readings, your account identifier, a screenshot or your IP address (they pass through our own server first), and they are kept for at most 90 days.
Sensitive information. A dream can reveal health, sexual life or religious belief, and the lens you choose (for example a religious tradition) can do so too. We process such information only with your explicit consent, which the app asks for before your first reading and again whenever this policy changes in a way that affects it. A refused text, including one about self-harm, is not kept; the table above lists what is kept about a refusal, and for how long. If you are in crisis, the app shows local help lines; please contact them or your local emergency number.
Where data is processed
We are in Türkiye. Our processors Cloudflare, Inc., RevenueCat, Inc. and Functional Software, Inc. (Sentry) are in the USA. Our database and stored artworks are in Cloudflare's Western Europe region (EU); our server and the AI models run in Cloudflare data centres anywhere in its network, including the EU and the United States. While your data is there, it is subject to the laws of those countries and may be accessible to their courts, law enforcement and national security authorities. The United States has no general data-protection law like the one in many countries (the Japanese Personal Information Protection Commission publishes a report on the US system: www.ppc.go.jp/files/pdf/USA_report.pdf). Cloudflare and Sentry are certified under the EU-US Data Privacy Framework, its UK Extension and the Swiss-US DPF; with all three processors we also have the EU Standard Contractual Clauses (Decision 2021/914) with the UK Addendum and Swiss amendments in their data processing agreements. For Switzerland: Cloudflare and Sentry are Swiss-US DPF-certified (adequate under Annex 1 of the Data Protection Ordinance since 15 September 2024); RevenueCat under the EU SCCs with Swiss amendments. Outside those regimes we rely on your explicit consent to the transfer and, for purchases, on its necessity for your contract with us. Write to support@ruuya.app for a copy of the clauses.
Recipients abroad.
- Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA, privacyquestions@cloudflare.com: readings, pattern analyses and artworks; processed when you ask, over an encrypted connection; stored in Cloudflare's Western Europe region (EU) and processed in Cloudflare data centres anywhere in its network, including the EU and the United States.
- RevenueCat, Inc., USA, compliance@revenuecat.com: account identifier, identifierForVendor, purchase history; sent at sign-in and purchase; your account's record is deleted when you delete your account.
- Functional Software, Inc. (Sentry), 45 Fremont Street, 8th Floor, San Francisco, CA 94105, USA, compliance@sentry.io: error reports and performance traces; sent when an error happens or on a sampled launch, kept at most 90 days.
- Google (USA) hosts our support@ruuya.app mailbox: what you write to us is processed there until your request is closed.
You can refuse by not using AI features (readings then stop), by not buying Premium, or by turning off error reports in Privacy & data.
Your rights
You can see, export and delete your data in the app (Account → Delete account deletes your account, readings, artworks and content-free safety log entries at once). You may also contact us to access, correct, restrict or object to processing, or to withdraw consent (future readings then stop), and you may complain to your data protection authority (in Türkiye, the KVKK Authority).
Deletion also removes your Sign in with Apple account identifier, so nothing on our server links the deleted account to you any more. What remains is a content-free record of the deletion (random account and reading numbers and their dates). If you sign in again with the same Apple account, you start a new, empty account. Cloudflare's database backups expire within 30 days; a restore from one re-applies deletions automatically.
When you delete your account, Ruuya asks Apple to revoke the app's Sign in with Apple access. Apple asks you to confirm this; if you cancel, your account is still deleted.
Deleting your account also deletes our copy of your purchase status at once, and your account's record at RevenueCat (your identifiers and any purchases; if that fails, write to support@ruuya.app). It does not cancel a subscription: cancel it in your Apple account settings. Apple keeps its own purchase records as billing and tax law requires.
You also have the right to receive your data in a portable form (Privacy & data → Export journal (PDF)) and to object to processing based on our legitimate interests. Requests: write to support@ruuya.app from the app's "Contact about my data" button, which adds your account identifier so we can find your account (we hold no name or e-mail). We answer within 10 days, free of charge, at most twice a year for the same request. If we refuse, reply with the word "appeal" and we answer the appeal within 10 days; a denied appeal tells you how to reach your data protection authority. You can complain at any time to the supervisory authority of the EEA country where you live or work, to the UK Information Commission, to the Swiss FDPIC, in Türkiye to the Personal Data Protection Authority (KVKK), in Washington to the Attorney General (atg.wa.gov), or to your country's authority.
Complaints. If you think we have handled your data wrongly, write to support@ruuya.app. We acknowledge your complaint within 30 days and tell you the outcome. You may also complain to your data protection authority at any time. You are not legally required to give Ruuya any data; a dream leaves your device only when you ask for a reading or for patterns.
How we govern personal information
One person, the developer, holds every role above. Retention is fixed in code and listed in the table. Complaints: write to support@ruuya.app; we answer within 10 days; you may also complain to the Commission d'accès à l'information or your authority. Incidents: we keep a register and notify the authority and the persons concerned when an incident presents a risk of serious injury.
Changes
When this policy changes in a way that affects your consent, the app asks you again before your next reading.
Effective date: 16 November 2026. Browser Do Not Track: neither ruuya.app nor the app collects information about your activity over time and across other sites or apps, so there is nothing for a Do Not Track signal to switch off, and we do not respond to such signals. No other party collects information about your online activity across sites or apps through ruuya.app or the app. When this policy changes materially, this page shows the new date.