Privacy policy

Updated 22 October 2026

Your information, how we use it, and the choices you have.

RitRekha is provided by RITVE PRODUCTIONS OPC PRIVATE LIMITED (Ritve Productions). This policy explains information handling in the RitRekha app and its related website pages. Contact admin@ritveproductions.com about privacy. The app is currently in development and testing; we update this notice when our practices change. The planned free RitRekha Kundli service is not available on this website yet. We will publish its applicable information-handling and service terms before enabling it.

Information you provide

• Account information: your sign-in provider identity, email address, name, profile photo and account preferences. Email registration, verification and recovery use Supabase Authentication and Resend. Passwords and verification codes are not sent to AI model services.

• Birth and profile details: birth date, birth time or its uncertainty, birth place and any profile information you choose to provide, such as gender. We use these details to calculate and personalize your charts and readings.

• Your activity and content: reflections, diary entries, custom trackers, preferences, language selections and interaction with readings.

• Support messages: your email address and information you send when asking for help or requesting deletion.

Birthplace, timezone and device information

RitRekha does not request device-location permission or collect your current GPS location. You select your birthplace during onboarding; our server uses its coordinates and timezone to calculate your birth chart. We also synchronize your device timezone to determine your local day and schedule daily features. Birthplace information and a timezone are different from tracking your live location.

We process device and session identifiers, request/security records and subscription information needed to operate the app. Trial and introductory-offer eligibility follows the applicable app store’s rules. The current app does not collect Android ID or iOS vendor identifiers for trial matching, and we do not use birth details to match trial claims across accounts.

RevenueCat and the applicable app store handle purchases and subscription status. RitRekha uses entitlement and transaction information; payment-card details are handled by the store/payment provider rather than entered into RitRekha. Current development purchases use RevenueCat’s simulated Test Store. Real Play billing is not yet available.

How we use information

• Sign you in, maintain your account and protect sessions.

• Calculate birth charts, personalize readings and provide language translations.

• Save reflections, settings and timeline features.

• Deliver notifications you enable and manage subscription access.

• Protect the service, investigate errors and respond to support or deletion requests.

What is sent to AI services

Our own software calculates chart positions and profile numbers before an AI service interprets them. For You readings and Questions, the AI request uses derived chart information, age in whole years, gender when supplied, and calculated profile numbers. It excludes your name, email, account identifiers, photo, exact birth date, birth time, birth place, coordinates and timezone name. Only calculated numbers are shared, rather than the source name.

Daily Dynamics also uses calculated transit information, the reading date and time window, and recent scores for the standard reflection areas. Reflection notes and custom tracker names or questions are not sent to AI. Questions use a selected catalogue question and its internal category. Translation requests contain the saved reading or answer and the target language, without adding your profile or natal summary.

Derived charts, reflection scores and generated readings can still be personal data even without direct identifiers. Removing direct identifiers reduces the data shared; it does not guarantee anonymity. AI output can be inaccurate and is not professional advice.

We use OpenAI for readings, answers and translations. OpenAI states that API inputs and outputs are not used for model training by default unless the customer opts in. We do not opt in to sharing this content for model improvement. Abuse-monitoring logs may be retained for up to 30 days, subject to legal and safety exceptions. We disable optional storage of completions, but do not promise zero retention.

Read OpenAI’s API data controls.

Reporting AI content

If you report AI content, we store your selected reason, optional message, the reported reading or answer, its language and its link to your account so we can review the concern and improve content safeguards. Reports are stored in our private support queue and removed when your account data is deleted.

Crash reporting and diagnostics

RitRekha includes Google Firebase Crashlytics to help diagnose app failures and improve reliability. Crash reporting is enabled in the applicable diagnostic and production builds. Diagnostic reports are sent to Google when reporting is enabled.

Reports can include installation identifiers, app and operating-system versions, device information, network connection type, crash and error traces, relevant app state and session timing. Native crash reports can also include diagnostic memory data. These records can distinguish an app installation; they are not anonymous merely because we do not attach your account identity.

We do not intentionally attach your email, birth details, readings, reflections or authentication credentials to crash reports. Our JavaScript error reporting limits messages and source coordinates to technical diagnostics. Native diagnostics are processed separately and can contain additional technical information.

Google processes these diagnostics to provide Crashlytics. Its published retention policy keeps crash traces, extracted native diagnostic data and associated identifiers for 90 days before removal from live and backup systems begins. Raw native minidumps are kept temporarily while being processed. Deleting your RitRekha account does not instantly erase these separate diagnostic records. See Firebase privacy information, or contact admin@ritveproductions.com with questions or a privacy request.

Read Firebase’s privacy and retention information.

Service providers and sharing

We use Google for sign-in; Supabase for identity, database and private photo storage; Render for the API; Resend for verification and recovery emails; Expo and Firebase Cloud Messaging for push delivery; Firebase Crashlytics for diagnostics; RevenueCat and the applicable store for subscriptions; and OpenAI for AI processing. Our websites use Cloudflare Pages, and Zoho handles support email. A daily-ready push can include your Current Rhythm text, so it may also be visible on your lock screen according to device settings.

The current Supabase project and Render API are hosted in Singapore. OpenAI and other providers may process data in other countries through their infrastructure and subprocessors. We do not promise that all data remains in India or Singapore. A selected email-sending region does not guarantee that every email record stays there. Contact us for details about processing locations and applicable international-transfer safeguards.

Storage, retention and deletion

Account/profile data, birth details, charts, readings, saved Questions answers and translations, reflections, notes and custom trackers are stored to provide your account and history. Personal content is not kept only on your phone: server records and some account-scoped device copies are used by these features. Signing out, uninstalling and deleting an account are different actions; uninstalling alone does not remove server-side data.

Account deletion removes the app profile and its associated birth details, saved personal content and derived per-user chart data. Profile-photo storage and authentication-identity cleanup are processed separately and may finish after the initial deletion request. Retrying or verifying these steps can take additional time; we do not promise that every copy is erased instantly.

Limited purchase/subscription history, transaction events and security/operational records can remain after account deletion for billing, fraud-prevention, security or legal purposes. Some historical records have their account link removed rather than being destroyed. RevenueCat purchase history is not automatically deleted when an app account is deleted. Provider logs or retained copies follow their applicable retention processes. We will explain retained categories and applicable constraints when responding to a deletion or privacy request.

Use the account-deletion page to request deletion without reinstalling the app. Deletion does not cancel a store subscription; manage that separately through the store.

Backups and operational records

Encrypted recovery copies can contain database records and profile-photo copies. The operator backup tooling targets 14-day retention for verified backup sets when it is run successfully; this is not a guarantee that every retained copy expires automatically. Failed or incomplete sets and separately retained copies need review. Account deletion does not edit older backups. Before a restored copy is returned to service, completed deletions must be reapplied. The minimal identifiers and deletion time needed to prevent deleted accounts from being restored are retained while recoverable copies may contain them.

Terminal operational records for AI requests, translation jobs, scheduled jobs and notification delivery are normally pruned after 30 days under the relevant expiry rules; this does not delete your saved readings or answers. Completed external deletion-cleanup receipts expire after 7 days, with private cleanup payloads cleared on confirmed completion. Session/security audit records and expired refresh-token history are retained for 180 days; active credentials and unresolved cleanup work have separate lifecycles. Infrastructure, authentication, email and crash providers have their own retention rules. Resend’s standard plans provide 30-day email/log retention. Account deletion is not a promise of immediate erasure from every provider log or backup.

Profile photos

Profile photos are stored in a private bucket and displayed using temporary signed links. A signed link can be used by anyone who possesses it until it expires, so do not share it. The app can retain an account-scoped offline copy; account-data deletion removes that local copy.

Adults aged 18 and over

RitRekha is for adults aged 18 and over. Do not create or use an account if you are under 18, including with parental permission. Give your own accurate birth date; do not change it to bypass the age requirement.

We use your birth date and, where required, record when you confirm that you are 18 or older to enforce this requirement. A recorded underage birth date overrides an age confirmation. This is self-declared age information, not identity verification; we do not ask you to upload identity documents for this check.

If an account is restricted because its recorded birth date is under 18, regular app access is blocked. Sign-out and account deletion remain available. If you believe the birth date is wrong, or information about someone under 18 was provided, contact admin@ritveproductions.com. Do not send identity documents, passwords or login codes by email.

Your choices and privacy requests

Depending on applicable law, you may request access, correction, deletion or a portable copy, object to or restrict processing, withdraw consent where processing relies on it, and complain to the relevant authority. Email admin@ritveproductions.com, including for a privacy grievance or an AI-processing consent request. We verify ownership and explain applicable exceptions and response times. AI processing begins after your agreement during onboarding; refusing that agreement prevents AI preparation. Account features require the relevant account and birth information, while notification permission is optional. We use information to provide the requested service, protect it, meet legal obligations and, where applicable, act on your consent or legitimate interests.

If you are concerned that information about a child was provided, contact us so we can investigate and handle the request.

Website and security

These RitRekha pages do not add advertising trackers, a website login or a data-entry form. Cloudflare hosts the website and may provide website analytics and process routine connection information, such as IP address and request logs, to serve and secure the site. An email link opens your own mail application; information is sent only when you choose to send the email.

We use HTTPS for app/API communications and restrict access to service data. No system is perfectly secure. Please do not send passwords, authentication tokens or payment-card details to support.

Contact and updates

Privacy contact: admin@ritveproductions.com. Changes will be published on this page with an updated date. This page describes current practices; a public app release will be accompanied by the applicable store disclosures.