astrobodhaEffective date: [EFFECTIVE DATE]
App: Astrobodha
Responsible developer: Astrobodha Ltd
Business address: Kharadi IT Park, Pune, Maharashtra, India
Privacy contact: contact@astrobodha.in
Website: https://astrobodha.in
1. Scope and purpose
This draft describes the intended privacy notice for Astrobodha and its support website. Astrobodha provides personalized daily astrology and three positive daily tasks using birth details and AI-assisted content.
2. Information and its sources
The following is an owner verification checklist, not a claim that every item is collected. Confirm collection, required or optional status, recipients and storage for each item. Remove items not used.
| Information to verify | Possible source and purpose to confirm | Required or optional |
|---|---|---|
| Name | User profile; personalization and support identification. | [CONFIRM] |
| Phone number | User entry and authentication provider; login and account verification. | [CONFIRM] |
| User entry; profile or support replies. Confirm whether the app collects email separately from support. | [CONFIRM] | |
| Date, time and place of birth | User entry; astrology calculations and personalized insights. Confirm handling of unknown birth time. | [CONFIRM EACH FIELD] |
| Account identifiers | Authentication/backend systems; link profile, predictions and account access. | [CONFIRM] |
| Purchases and entitlements | App stores or subscription service; verify access and restore purchases. Confirm transaction IDs, receipt data and payment information actually received. | [CONFIRM] |
| Usage, device and diagnostic data | App/SDKs/server logs; reliability, security or analytics, only if enabled. Specify events, identifiers, IP addresses and crash data actually collected. | [CONFIRM] |
| Support correspondence | Sender’s email and message; respond to requests. Add form fields only if a working form is enabled. | [CONFIRM] |
3. Birthplace and device location
A place of birth typed into a profile is different from accessing a device’s current location. Do not infer device-location collection from the birthplace field.
[CONFIRM: Is location permission requested? Is current or approximate location collected by the app or SDKs? Identify the purpose, consent controls and whether declining affects functionality. If none, state that only after verification.]
4. How information is used
[CONFIRM the exact data used for each purpose: authentication; profile personalization; astrology calculation; AI prediction generation; saving predictions/tasks; support; fraud/security controls; subscription verification and restoration. Explain consequences of not providing required fields and available optional-field choices.]
5. Providers and AI processing
[OWNER CHECKLIST — not a confirmed provider list: Firebase/Google Cloud, Google Gemini, RevenueCat, Apple, Google Play and any astrology calculation service. Verify each against the released build, backend and contracts; list only providers actually used.]
For each confirmed provider, document its service, exact information received, purpose, processing location where known, relevant privacy terms and whether it acts on instructions or for its own purposes.
[AI DATA FLOW: Specify whether birth date/time/place, calculated planetary positions, name, account identifier, user messages or other fields are sent to the AI provider; whether calls go through your backend; and what prompts/outputs are stored. Confirm applicable provider retention and training settings. No claim about AI training or provider retention is made in this draft.]
6. Sharing and disclosures
[CONFIRM actual sharing with service providers, app stores, support processors and any other recipients. Explain legal-request, security and business-transfer disclosures if applicable. Verify advertising, sale or cross-app tracking practices; do not publish blanket “never share” statements.]
7. Storage, transfers and security
[CONFIRM database/storage regions, relevant international transfers and applicable safeguards. Describe implemented access controls, authentication protections and transport/storage security accurately; do not promise absolute security or unverified encryption.]
8. Retention and deletion
[SET ACTUAL RETENTION: account/profile data — duration or criterion; saved predictions/tasks — duration; support messages — duration; diagnostic logs — duration; purchase/legal records — purpose and duration; backups — expiration schedule. Identify exceptions and how provider deletion is propagated.]
The account deletion page describes the request process. Its pending details must be completed before launch. Submitting a request is not confirmation that deletion has finished.
9. Your choices and rights
[CONFIRM access, correction, deletion, consent withdrawal and any applicable portability/objection/restriction rights by launch jurisdiction. Describe verification, response time, escalation and regulator contact where required. Do not claim compliance with a law without review.]
Privacy requests will be directed to contact@astrobodha.in. Never send passwords, OTP codes or full payment details.
10. Children and eligibility
[CONFIRM minimum age, target audience, parental consent if applicable, age checks and the process for removing inadvertently collected children’s information. Align with store declarations. No age threshold has been assumed.]
11. Website contact, cookies and analytics
This draft adds no analytics, advertising scripts or contact-form collection. Contact is available by email at contact@astrobodha.in.
[AUDIT BEFORE PUBLISHING: hosting/CDN logs, WordPress plugins, cookies, embedded resources and any future contact integration. Identify the actual data, purposes, recipients and retention; add consent controls where required. Existing hosting behavior has not been verified.]
12. Updates and contact
Publish the effective date and explain how material updates will be communicated: [UPDATE NOTICE PROCESS]. Contact contact@astrobodha.in at Astrobodha Ltd, Kharadi IT Park, Pune, Maharashtra, India.