How Nakshatra uses data.

Overview

This policy explains the data Nakshatra may collect or process when a user creates an account, enters a birth profile, uses astrology features, asks questions, saves content, receives notifications, buys a subscription, or contacts support.

Data Nakshatra may collect

• Account and authentication data, such as email address, user id, sign-in provider, and session-related records. Passwords or auth secrets are handled by the configured authentication provider and should not be stored directly in Nakshatra product tables.
• Birth profile details, such as name or profile label, date of birth, time of birth, approximate birth time setting, birth place, timezone, latitude, and longitude.
• Current or saved location data when used for local sky, Panchang, travel timing, timezone, or location search features. Users can use manual city search instead of device location where available.
• Kundali and chart data, including calculated chart placements, rashi, nakshatra, pada, graha, house, Dasha, Gochar, Panchang, confidence, and related interpretation records.
• Ask Nakshatra questions, source-backed answers, conversation history, feedback, and saved insights if the feature is enabled and used. The first public release is planned to use source-backed/deterministic Jyotish guidance, not live OpenAI-backed Ask, unless a later release explicitly enables it.
• Generated or saved reports, report requests, report metadata, and report library records.
• Remedies, ritual check-ins, completion history, timing plans, goals, journal entries, decisions, bonds, and relationship profiles if those features are used.
• Push notification preferences, quiet hours, delivery records, and push tokens when notifications are enabled.
• Subscription status and entitlement records from RevenueCat and the App Store or Google Play, such as product id, entitlement state, purchase status, renewal/expiration dates, and store identifiers. Full payment card details are handled by the app stores, not Nakshatra.
• Internal usage events, request diagnostics, app version/platform details, API logs, IP address, user agent, crash or reliability records, and app event data where collected for security, debugging, store review, or reliability.
• Support messages, deletion/export requests, content reports, and related correspondence.

How data is used

• Create and secure user accounts.
• Calculate and display Kundali, chart facts, Panchang, Dasha, Gochar, reports, and timing guidance.
• Generate or assemble Ask Nakshatra answers, reports, safe remedies, saved insights, and journal flows.
• Provide Premium access, restore purchases, and reconcile subscription status.
• Send opted-in notifications and reminders.
• Support users, troubleshoot issues, prevent abuse, improve reliability, and maintain safety boundaries.
• Prepare required store privacy disclosures and comply with applicable operational obligations.

Service providers and processors

Nakshatra currently expects to use these service providers when configured:

• Supabase for authentication, user records, database hosting, and related backend data.
• API hosting/logging infrastructure for request processing, operational logs, security, and diagnostics.
• RevenueCat for subscription status, app-store purchase events, and entitlement mapping.
• Geoapify for place search, geocoding, and location/timezone support when enabled.
• OpenAI only for a future live Ask Nakshatra or AI-assisted answer generation if that feature ships live and is explicitly enabled in production.
• Apple App Store and Google Play for subscription purchase, billing, cancellation, and refunds.
• Expo push services or platform notification services for push delivery if notifications are enabled.
• Support/email provider once selected for support, export, deletion, and content concern messages.
• Analytics or diagnostics providers if the production build enables analytics, crash reporting, or diagnostics.

Ask guidance and future AI

The first public release is planned to answer Ask Nakshatra from Nakshatra's own source-backed app services. Live OpenAI-backed Ask is not planned for v1. If a later release ships live Ask Nakshatra with OpenAI or another AI provider, user questions, recent conversation context, saved signals, birth/profile context, location-derived timing context, Kundali/chart facts, Dasha/Gochar, and related astrology context may be sent to that provider to generate answers. Astrology-based content can be incomplete, imperfect, or inappropriate for high-stakes decisions. Nakshatra is for reflection and planning support, not medical, legal, financial, emergency, mental health, or other professional advice.

User choices

• Use manual city search instead of optional device location where available.
• Manage push notification preferences in the app and through device settings.
• Manage, cancel, or restore subscriptions through the App Store or Google Play account used to purchase.
• Request data export through support. Automated export downloads are not currently available.
• Request support, export, correction, or deletion help through support@nakshatra-app.com.

Retention and deletion

Nakshatra keeps account and product data while the account is active or while needed to provide the service, maintain security, support purchases, troubleshoot issues, meet legal or operational obligations, and protect payment integrity. Signed-in users can request staged deletion in the app, and users without app access can contact support through the account deletion page.

Deletion requests may require manual support review. The current app can create, show, and cancel deletion requests with reference codes and status. Processing data removal across Nakshatra product data, Supabase Auth, RevenueCat, provider logs, backups, and other processors may require verification, support review, and time to complete. Some records may be retained when required for legal, security, fraud prevention, payment evidence, support, audit, accounting, dispute, backup, compliance, or store/processor limitation reasons.