What Data We Collect
Hayrola collects only the information you choose to provide:
- Dream text you enter for interpretation
- Optional profile information: gender, age range, marital status, and religiosity level
This information is used solely to provide more personalized dream interpretations.
How Data Is Stored
Dream text, recordings and profile information are stored on your device. Interpretation runs locally. Dictation requires supported on-device speech recognition and has no cloud fallback. If local recognition is unavailable, type your dream. Device backups and exported copies are controlled separately. Purchase services and, when you allow them, usage analytics and crash reports process the metadata described below.
What We Do NOT Collect
- No dream content ever leaves your device
- No cloud synchronization
- No advertising identifiers
- No cross-app or cross-site tracking
- No precise location data
- No contact information
- No cookies or web tracking
Usage Analytics and Crash Reports
Two optional flows use Google Firebase: usage analytics (Google Analytics for Firebase) and crash reports (Firebase Crashlytics). Both ship switched off and stay off until the app has applied your decision. In the EEA, the UK, Switzerland and Türkiye — and on any device whose region cannot be determined — nothing is collected until you opt in. Elsewhere both are on by default and Settings carries a separate switch for each; a refusal is stored and survives restarts and updates. Analytics collects screen names, fixed event names, counts such as a dream's word count, purchase events, app language and Premium status, tied to a random app-instance identifier. Crash reports collect the stack trace, app and OS version, device model and a random installation identifier. Dream text, recordings, transcripts, profile answers, istihare questions, precise location and advertising identifiers are never sent, whatever you choose. Turning analytics off resets the analytics identifier and drops queued events. Turning crash reports off deletes reports that have not been sent yet.
İstihare, Prayer Times and Notifications
İstihare guidance runs on your phone: the question or intention you set, the ritual steps and the dream you log. Like every other dream, they stay on the device.
Prayer-time boundaries and the qibla bearing are computed on your phone from a city you pick in the app. The app does not ask for location permission and does not use GPS.
Notifications are local and scheduled by your phone: a daily morning reminder at 8:00 if you switch it on, the bedtime nudge and the morning check for an istihare night, an optional quiet mid-night cue, a next-day reflection after a reading, and a one-off reminder when a reading is waiting. They need notification permission and can be turned off in the app or in system settings. No notification content is sent to a server.
Data Deletion
Deleting a dream removes its local entry and associated recordings. Clear all dreams removes saved dream entries and their recordings. Cancelled or unused recordings are removed. Interrupted cleanup is retried when the app starts. Profile settings, saved people and pets, and Dream Target campaigns are separate records. Manage those separately. Backups and exports outside the app can retain copies. Turning a switch off stops further collection; it does not erase what Google already received. Analytics event records are deleted on the data-retention period set for this Analytics property, and aggregated reports are kept beyond it. Crash reports are kept by Crashlytics for about 90 days. Earlier releases collected analytics in some regions without asking; those records are still held under the same rules. No two-month deletion deadline is guaranteed. Contact devappgea@gmail.com for requests concerning provider-held records.
Third Parties
Interpretation and supported dictation run on your device. Apple or Google supplies the local speech engine. Older versions used system speech recognition without enforcing local processing and could send speech to the system speech provider. Apple, Google and RevenueCat process purchase identifiers, entitlement checks and device/network metadata, including during app startup. Google receives usage events and crash diagnostics only while the matching switch is on; with both off, the Firebase SDKs are initialized but send neither. Purchase, analytics and crash requests do not include your dreams, recordings or profile answers.
Purchases
Purchases are processed by Apple, Google and RevenueCat, which receive pseudonymous purchase identifiers — never your dream content.
Children's Privacy
Hayrola is not directed at children under the age of 13. We do not knowingly collect any information from children under 13. If you are a parent or guardian and believe your child has used this app, please contact us at devappgea@gmail.com and we will promptly address the concern.
Contact
If you have any questions about this privacy policy or how your data is handled, please reach out to us at: