Ru'ya AI is developed and operated by an individual developer based in Algeria. For any privacy questions or data requests, contact us at:
ruyaai.support@gmail.com.
The 13 and above designation (teenagers and adults) describes the app's intended audience. The app does not currently request a date of birth or independently verify a user's age. Ru'ya AI is not directed at children under 13; if we become aware or are notified that a child under 13 has created an account or submitted personal data, we will delete the associated account and records from the active database.
Purpose Note: Ru'ya AI provides reflective and cultural dream interpretation powered by curated references and AI; it is not medical, psychological, or predictive advice.
We collect or process only the information needed to provide account functionality, dream interpretation, and optional history storage:
- Account details: email address, authentication user ID, optional display name (
display_name), and history-saving preference (save_history). When signing in with Google, authentication runs through Google OAuth and Supabase Auth.
- Dream submissions and context: the dream text you submit, optional context fields (mood, timing, recurring status, general life context), clarification questions and answers, and preferred language.
- Saved analyses: when history saving is enabled, submitted dream details and generated interpretation results are stored in your history so you can review them later.
Ru'ya AI uses Supabase for user authentication (email/password, Google OAuth, and password recovery) and for storing user profiles and saved dream records.
- Access Isolation (RLS): Database tables use Row-Level Security (RLS) so authenticated users can access and manage only their own records.
- Retention & History Toggle: Saved dream records remain associated with your account while the account exists and the save-history option (
save_history) is enabled. Turning save_history off stops saving new analyses to your account history, while previously saved entries remain until you delete them.
- Deletion from the Active Database: Inside the app, you can delete an individual dream, clear all saved dreams, or delete your account. When you request deletion, the relevant records are deleted from the active database through the app's deletion functionality.
Backups & Infrastructure Logs Clarification: We do not promise a specific deletion period for backups or infrastructure logs. Retention of automated backups or infrastructure logs may follow the relevant service provider's retention practices, which may not be fully known to us.
Requests for clarification questions, dream analysis, dream history operations, and account deletion pass through our FastAPI backend hosted on Render.
Application logging is configured to record operational metrics (such as request status, errors, and timings) while intentionally avoiding logging dream text, user email addresses, AI prompts, or authentication tokens. Nevertheless, standard hosting and network infrastructure (such as Render HTTP/server logs, which may include IP addresses or request metadata) may retain logs under the hosting provider's retention practices, which may not be fully known to us; we do not promise a specific deletion period or claim that zero technical or provider logs exist.
To generate clarification questions and dream interpretations, the app may send the following through the backend to AIGrid for processing:
- The dream text you submit.
- Optional context fields and clarification answers you provide.
- Relevant reference excerpts retrieved from the app's built-in knowledge base.
Neither the app nor the backend intentionally sends your email address, user ID, JWT token, display name, or device ID to AIGrid. However, personal details are not automatically removed from dream content, so submitted dream text and context are not represented as anonymous and could still contain information that identifies a user if included in what you write.
Unconfirmed Provider Practices: AIGrid's internal practices regarding data retention, server logging, AI model training, and subprocessors could not be independently confirmed. We also do not represent AIGrid's processing as governed by a verified privacy policy (
ai-grid.io is linked solely as the provider's official website).
Microphone access is activated only when you explicitly tap the voice-input button while entering a dream:
- On Android: speech-to-text uses the Android operating system's speech recognition service.
- On Web: dictation uses the browser's
SpeechRecognition and getUserMedia APIs, and microphone tracks are stopped immediately once dictation stops.
Raw audio recordings are not uploaded to or stored on the Ru'ya AI backend or Supabase. Audio handling is governed by the privacy policy of your device OS, web browser, or speech-recognition provider (such as Google on Android).
The application stores essential preferences and session state locally on your device, including:
- Language preference (
app_language_code), dark/light theme preference (app_dark_mode), and onboarding completion state.
- Local history-saving sync and protected authentication session storage (such as
sb-gzydroqtjdwezwvggzfl-auth-token).
- Temporary password-recovery state keys (
pending_password_recovery and pending_password_recovery_uid) used to complete password reset safely.
This static Privacy Policy page and the download page do not set tracking cookies or load third-party analytics libraries.
The Android app integrates the Google Mobile Ads SDK alongside Google's User Messaging Platform (UMP) consent flow. Web and desktop builds use a no-op adapter and do not load Mobile Ads.
- Current release state: production ads are currently disabled (
USE_PROD_ADS=false), with only test ad unit IDs configured for development testing.
- 13+ request configuration: before initializing Mobile Ads, the app configures teen age-restricted treatment (
AgeRestrictedTreatment.teen) and a maximum ad content rating of PG (MaxAdContentRating.pg) for its 13+ audience.
- Consent gating: on Android, UMP consent is requested and resolved before applying configuration and calling SDK initialization, with a privacy options entry provided when required.
If production ads are enabled in future releases, ad delivery and consent signals will be processed under Google's privacy policies and your UMP consent choices; we do not promise that zero technical or advertising identifiers can ever be processed when Google Mobile Ads is active.
Because Ru'ya AI relies on cloud and AI infrastructure providers, data may be transferred to and processed on servers outside your country of residence. We do not assert fixed data-center regions where not directly verified. Official privacy policy links are provided below for Supabase, Render, and Google; for AIGrid, only the provider's official website is listed because its standalone privacy policy and internal data-handling practices could not be independently confirmed:
Supabase
Authentication, user profiles, and dream history database — Official Privacy Policy
supabase.com/privacy
Google
Google Sign-In (OAuth), Android Speech Services, Google Fonts (app UI), and Mobile Ads / UMP — Official Privacy Policy
policies.google.com/privacy
AIGrid
Clarification & interpretation processing (provider website only — standalone privacy policy not independently confirmed)
ai-grid.io
App Interface Fonts (Google Fonts): The Ru'ya AI Flutter application uses
Google Fonts (Cairo) to render its interface; because font files are not bundled inside the app assets and runtime fetching is enabled by default, the app may request font resources from Google Fonts (such as
fonts.gstatic.com) when launched before a variant is cached on device or on platforms without local file caching. Such requests may expose ordinary technical connection information to Google (such as IP address and standard request metadata), as applicable, under Google's official Privacy Policy:
policies.google.com/privacy.
(This static Privacy Policy webpage itself uses only system fonts and makes no external font requests.)
You can exercise control over your personal data directly in the app or by contacting us:
- Access: view your profile details and saved dream interpretations at any time in your account.
- Opt out of history storage: disable
save_history in settings to stop storing future dream interpretations.
- Selective or full deletion: delete individual dream records or clear your entire dream history in-app.
- Account deletion: permanently delete your account from settings to remove your live user and dream records.
- Ad consent management: where UMP regulations apply, update or withdraw ad consent via Privacy Options in settings.
We may update this Privacy Policy as features evolve, advertising settings change, or service providers are updated. Any update will revise the "Last updated" date shown at the top of this page.
For privacy questions, data requests, or account support, contact the operator at:
ruyaai.support@gmail.com.