Privacy Policy

Effective Date: September 2, 2026

This Privacy Policy covers the reDream mobile application and this website (redream.resoulve.eu). It applies to both reDream (eu.resoulve.redream) and reDream Pro (eu.resoulve.redream.pro), which are published on Google Play. They are the same application; Pro includes the complete statistics set. Neither collects your data nor transmits it anywhere. What you write stays on your device unless you move it yourself.

Privacy Policy for the Mobile App

Overview

reDream is designed to be a privacy-first application. The app collects no personal information about you and shares none with anyone. All data created through the app stays entirely on your device, and the app never transmits it to external servers or third parties. What your device itself may do with that data, through backup or transfer features that belong to your operating system or your phone's manufacturer, is a separate question, and is set out under "Backups and Device Transfers" below.

Data Storage

The app stores operational data, such as user preferences, as well as created Dreams and Tags, locally on your phone in an SQLite database. Under Android's normal protections this data is private to the app, so other apps on your phone cannot read it. It is deleted if you uninstall the app or clear its data.

Export and Import

The app includes optional export and import features that allow you to:

  • Export your data: Save your dreams and tags to a JSON file on your device or share them via other apps (email, cloud storage, messaging apps, etc.). You have complete control over where this data goes.
  • Import data: Load previously exported dream data back into the app from a JSON file.
  • Protect an export with a passphrase: You may choose a passphrase when exporting. The file is then encrypted with AES-256-GCM, using a key derived from that passphrase, and cannot be read without it. The passphrase is chosen per export, is never stored by the app, and cannot be recovered or reset by anyone, including the developer.

These features are entirely optional and user-initiated. The app never automatically exports or shares your data. When you use the share feature, data is shared through your device's native sharing system. The app itself does not send data to any external servers. Once you share exported data through another app (such as email or cloud storage), that data is subject to the privacy policies and practices of those services.

One detail of sharing is worth knowing, because it is not obvious. Sharing an export means handing a file to your device's sharing system, and that system keeps its own copy in a cache folder so that the app you picked can read it. reDream deletes the copy it made as soon as the share sheet is done with it, but the copy the sharing system keeps stays there until the next time you share anything out of reDream, an export or a diagnostic log, at which point reDream clears that folder first. So between one share and the next, a copy of that export exists in reDream's cache. It is inside the app's private storage, and it is deleted with everything else if you uninstall the app or clear its data. If the export was protected with a passphrase, so is that copy. Saving an export with "Export to File" leaves nothing behind: the file goes where you chose it to go, and nowhere else.

Diagnostic Logs

The app keeps a diagnostic log file on your device, so that a problem you run into can be understood after the fact. It records what the app did and what went wrong: the app version and your device's operating system version and build, database setup and upgrades, reminders being scheduled or cancelled, exports and imports starting, succeeding or failing, app lock errors, and internal error messages with their stack traces.

By design, the log holds nothing you wrote. It records no dream text, no dream titles and no tag names. Where an entry refers to a dream or a tag it uses that item's internal identifier, and where it describes what happened it uses counts: how many dreams a tag merge affected, how many results a search returned. A search is recorded with the length of what you typed, never with what you typed. Nor is the path of an export or an import written down, so a filename or a folder you picked yourself does not appear there either.

One limit is worth stating plainly rather than promising around. When something fails unexpectedly, the app records that error's own message and its stack trace as they arrive, without reading them first. Those come from the code that broke, not from your journal, and nothing in the app is written to put your text into one. It is the honest shape of the guarantee, though: everything above is what reDream deliberately writes, and an unexpected error is the one thing it passes through unexamined.

The file lives in the app's private storage. Each log file is allowed to grow to 5 MB. reDream checks the size when it starts up, so a file that passes 5 MB while you are using the app is set aside at the next launch rather than the moment it crosses; at that point reDream begins a new file and keeps at most the one it is writing and the one before it, so anything older than those two is gone. Both are removed when you uninstall the app or clear its data, and nothing in either of them is ever sent anywhere by the app.

Settings also offers "Share logs". This is user-initiated, exactly like an export: it hands a copy of the log to your device's share sheet, both files where a rotation has left two, so that you can send it to the developer when reporting a problem, and the copy reDream made is deleted afterwards. The copy your device's sharing system keeps behaves exactly as it does for an export, described above, and is cleared at your next share of either kind. If a log reaches the developer, it is because you chose to send it. You can read the file before you do.

Backups and Device Transfers

Android has two separate routes for copying an app's data off a phone, and reDream treats them differently. Cloud backup is off: the app opts out of Android Auto Backup, the mechanism that would otherwise copy its data to Google's servers along with your device backup. Device-to-device transfer is allowed: when you set up a new phone from your old one, Android copies reDream's data across with your other apps, directly between the two devices, without it passing through Google or anyone else. It is left on because it sends your dreams nowhere the cloud-backup opt-out was protecting them from, and because it is what keeps a long journal from being lost to a routine phone upgrade.

A transfer is not a backup. It needs your old phone working and in your hands, so it does nothing for one that was lost, stolen or broken. The app's export is how you keep a copy you control.

Both of those settings are instructions to Android's own backup system, which is the limit of what any app can decide for itself. Phone manufacturers ship backup, cloud and phone-cloning software of their own, and an employer may add management software to a work phone. That software is part of the system rather than an ordinary app: it does not necessarily consult the settings reDream asks for, and reDream cannot detect it, prevent it, or tell you afterwards what it copied. The database itself is not encrypted, so software with system-level or root access to your phone can read your dreams as plain text. Ordinary apps cannot: Android keeps each app's files to itself. None of this involves the app or its developer, and neither receives your data through it, but it is not something reDream is in a position to promise about on your behalf.

If you want your journal to exist only where you have put it, check your device's own backup, cloud and transfer settings and exempt reDream there, then keep your own copy through the app's export, protected with a passphrase.

Permissions

The app requests the following permissions:

  • Notifications (Android): If enabled, the app can send you daily reminders to record your dreams. This uses the POST_NOTIFICATIONS permission, and you can allow or deny it within your device settings. The component that shows them also declares the VIBRATE permission, so a reminder can buzz rather than arrive silently. Notifications contain no personal data and are generated locally on your device.
  • Restart notifications after reboot (Android): The app can restore your scheduled reminders after your device restarts, so you don't need to reconfigure them. This uses the RECEIVE_BOOT_COMPLETED permission.
  • Biometrics (Android): If you turn on the app lock, reDream asks your operating system to confirm that it is you, using whatever your device is set up for: fingerprint, face, PIN or pattern. This uses the USE_BIOMETRIC permission, alongside the older USE_FINGERPRINT permission that Android versions before 9 expect for the same check; they are one prompt, not two. The check happens entirely inside your operating system. The app receives only whether it succeeded or failed, never your fingerprint, your face data or your PIN, and it records nothing about the attempt beyond an error in its own log if the check could not run at all.
  • Talking to itself (Android): The app holds one permission named after itself: eu.resoulve.redream.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION, or the same with .pro for reDream Pro. An Android support library declares it so that parts of the app can pass messages to each other without other apps listening in. It gives access to nothing on your device, and only software signed with the same key as reDream can hold it, which means reDream and nothing else.

Those are all of them. The app does not access or utilise sensitive permissions such as location, contacts, camera, microphone, or photo library access. It does not request internet access, which means it is not technically able to make network requests of its own. It also requests no storage permission: when you export or import, your device's own file picker opens, and the app is given the single file you chose and nothing else on your storage.

Third-Party Services

This app does not use analytics, advertising, crash reporting, or any other third-party services that collect user data. The app does not rely on platform-specific libraries that automatically collect user-identifying information, and it makes no network requests to external servers. It holds no internet permission, so this is not a promise about restraint; the app has no way to reach the network.

For the sake of completeness, three things in the app do hand off to something else on your device that is online, in the same way that tapping a link in any app does:

  • Links. A few places in the app link outwards, to this privacy policy, to pages on this website and to the reDream Pro listing on Google Play. Tapping one opens your browser or the Play Store app, exactly as a link in any other app would. reDream passes an address and nothing else.
  • The review prompt. At most twice in the life of an install, and at least ninety days apart, the app asks Google Play to show its own rating sheet. The decision of whether to ask is made on your device from how many dreams are in your journal, when the app was installed, and when it last asked. Nothing about you is sent with the request, and Google Play does not report back whether the sheet appeared or what you did with it. Settings also offers a way to open the store listing yourself.
  • Sharing. An export or a log you choose to share is handed to your device's share sheet, and from there to whichever app you pick.

In each case, the app that goes online is the browser, the Play Store or the app you shared with, under its own privacy policy, and reDream receives nothing back about you.

Purchase and Payment

reDream Pro is a one-time purchase through Google Play. The app contains no in-app purchases, no subscriptions, and no billing code of its own. Payment is handled entirely by Google Play under Google's terms. reDream never receives your name, payment details, or any other information about the transaction.

There is also no licence check. reDream Pro is a separate build of the same app, sold as its own listing, in which the Pro features are simply present. The app never asks Google, or anyone else, whether you are entitled to them, and it could not do so without a network connection it does not have. Nothing about your purchase is stored in the app or checked while you use it.

Data Security

Since all data stays on your device, its security depends on your device's security measures. The app relies on the native security features of your operating system (such as device encryption and lock screen protection) to protect locally stored data. The app itself does not transmit or process any data online.

When you use the export feature, you are responsible for securing the exported files and controlling where you share them. You may protect an export with a passphrase of your choosing, which encrypts the file so that it cannot be read without it. Because the passphrase is never stored, a forgotten passphrase means that copy cannot be opened again.

Changes to This Policy

If future versions of the app introduce features that involve data collection or online functionality, this Privacy Policy will be updated accordingly and made available in the app and on the store listing. The Effective Date will also be updated to reflect when changes were made.

July 30, 2026: this policy was extended to cover reDream Pro. No data practices changed.

August 30, 2026: this policy was expanded to describe things the app was already doing but that were not written down here: the biometric app lock, the diagnostic log file and the option to share it, the passphrase on an export, and the handoffs to your browser and to Google Play. Backups and device transfers now have their own section, setting out which routes are switched off, which are allowed and why, and what reDream is not in a position to decide, and sharing an export now says what it leaves in the app's cache and for how long. No data practices changed; the description of them became more complete.

September 2, 2026: the list of permissions was completed. It named the three the app asks for on its own behalf, but not three more that come with the components it is built from: the vibration a reminder can use, the older fingerprint permission that Android versions before 9 expect for the app lock, and one the app holds over itself so its own parts can pass messages without other apps listening in. None of them reaches your data and none of them is new; the list now matches what the app installs.

Privacy Policy for this Website

Website Data Collection

This website (redream.resoulve.eu) is committed to the same privacy-first principles as the reDream mobile app. We do not use cookies, analytics, tracking scripts, or any other technologies to collect or store information about our visitors.

Server Log Files

The website provider automatically collects and stores information in server log files that your browser automatically transmits to us. These are:

  • Page visited on our domain
  • Date and time of server request
  • Browser type and browser version
  • Operating system used
  • Referrer URL
  • Hostname of the accessing computer
  • IP address

This data is technically required for us to display our website to you and to ensure stability and security. The legal basis for data processing is Art. 6 para. 1 lit. f GDPR, our legitimate interest in operating the site securely. These logs are kept only as long as they are needed for that purpose and are rotated and deleted automatically by the hosting platform. They are not combined with other data sources and are not used for any other purpose.

Cookies and Tracking

This website does not use cookies. We do not employ any tracking technologies, analytics services, or third-party scripts that collect user data. No personal data is saved or processed by this website beyond the standard server log files mentioned above, which are managed by our hosting provider.

External Links

This website contains links to external services (such as the Google Play Store). When you click these links, you leave our website and are subject to the privacy policies of those external services. We have no control over and assume no responsibility for the privacy practices of third-party websites.

Your Rights under the GDPR

Because reDream never receives what you write, there is usually nothing of yours for us to hold. Your dreams are on your device, and we have no copy to show you, correct or delete. In practice these rights concern the two things that do reach us: the server log files described above, and any email you send us.

For that data you have the right to request access to it (Art. 15 GDPR), to have it corrected (Art. 16), to have it erased (Art. 17), to have its processing restricted (Art. 18), to receive it in a portable form (Art. 20), and to object to processing based on our legitimate interest (Art. 21). Write to privacy@resoulve.eu. Exercising these rights is free, and we will respond within one month.

No automated decision-making or profiling takes place. We do not sell or pass on this data. Apart from our hosting provider, which operates the server on our behalf and processes the log files only for that purpose, it is not shared with anyone.

Right to Lodge a Complaint

If you believe we handle your data unlawfully, you have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). You may do so in the EU member state where you live, where you work, or where you believe the infringement took place. Each member state publishes the contact details of its own supervisory authority.

Who is Responsible, and How to Reach Us

reSoulve is the controller for the data described in this policy, covering both the app and this website. The full name and postal address are in the Legal Notice.

For anything about this policy, about either app, or about how this website handles data, write to privacy@resoulve.eu.