Privacy Policy

Effective Date: 2026-10-05

Version: v6.3

Supersedes: v6.2

v6.3 change-log: Explains optional Android microphone dictation and distinguishes purchase-support retention from tax-invoice retention. Active from 2026-10-05; supersedes v6.2.

v6.2 change-log: Corrects the Yana calculation-packet disclosure and Android Google Play credit/report purchases and optional notifications. Active from 2026-10-03; supersedes v6.1.

v6.1 change-log: Adds the optional, privacy-minimised App city-location flow. A saved city wins. With no saved city, Astroyana may make one cookie-free request and use trusted Cloudflare edge headers to suggest a validated city; otherwise it visibly uses Ujjain. On Android and iOS, the App requests approximate foreground location only after you tap Use my current location, reduces the fix to a rough city-sized area (about 5 km) before transport, resolves a city through the Astroyana proxy, and discards the raw fix. It does not use precise or background location or keep a location history. The remaining v6 changes are retained: the complete Hindi publication and a current-law clarification. The DPDP Act's main processing, obligation and Data Principal rights provisions (sections 3–17), and Rules 3 and 5–16, commence on 13 May 2027; the Data Protection Board has already been established. Until those provisions commence, applicable duties include the Information Technology Act, 2000 and the SPDI Rules, 2011. Astroyana already offers the stated controls as contractual service commitments. Consumer-grievance acknowledgement is reduced from 72 to 48 hours. It also discloses a new privacy-minimised, server-side Yana weekly aggregate counter and the optional paid Yana voice unlock. The aggregate adds no user-level analytics record, individual profiling, offer tracking or Android capability. Google Cloud Text-to-Speech is added to §7 only for the narrowly scoped voice processing described in §5B.

1. Who we are

The operator and future Data Fiduciary is:

• Operator: Astroyana, a service brand operated by SNAZZYWORKS
• GSTIN: 27HXGPD1259E1ZL
• Registered / principal address: Ground Floor, Tejaswani Hsg Society, DP Road, Baner, Pune - 411045, Maharashtra, India
• General contact: [email protected]
• Customer care / grievance phone: +91 83903 38556
• Website: https://astroyana.com
• Android app: "Astroyana" on Google Play, application identifier com.astroyana.app, published by SNAZZYWORKS

1.1 Privacy and grievance contact

• Name: Mahesh Dhaifule
• Designation: Grievance Officer & Data Protection Lead
• Email: [email protected]
• Phone: +91 83903 38556
• Postal address: Ground Floor, Tejaswani Hsg Society, DP Road, Baner, Pune - 411045, Maharashtra, India
• Consumer-grievance timeline: acknowledgement within 48 hours and redressal within one month
• Other privacy requests: substantive response ordinarily within 30 days; the applicable GDPR period is in §16

When DPDP Act §§8(10) and 13 and Rule 14 commence on 13 May 2027, this contact will serve as the statutory contact unless a later policy names a replacement.

2. Scope

This Policy covers personal data processed when you:

• Visit astroyana.com or astroyana.in
• Use the Astroyana Android app
• Request a free or paid report or calculator
• Create an account or sign in by web magic link or app OTP
• Use Yana, the AI astrologer
• Save another adult in Family Vault when that feature is enabled
• Buy through web checkout or communicate with support

It also explains the controls we provide now, future DPDP rights, and additional GDPR / UK GDPR information for EU, EEA and UK users (§16).

It does not cover third-party sites, future astrologers or contractors not yet engaged, or the separate sister brand Rudrakshakavach.

3. Personal data we process

We limit collection to what the selected service and its security require.

3.1 Data you provide

Android purchases and notifications. Google Play Billing processes in-app credit and report payments and returns purchase evidence that Astroyana’s server verifies before fulfilment. Optional reminders and report-ready notifications require your action and OS permission; Astroyana sends an Expo push token and installation/build metadata to the Expo Push Service for delivery to the device platform.

3.2 Data generated automatically

Server-side Yana weekly aggregate analytics. Separately from the first-party web analytics above, when this feature is enabled the server counts only completed requests that reached the computation engine. It stores one counter per IST week (starting Monday), Engine response-domain enum, channel (web or whatsapp) and outcome (answer, degraded or redirect). The aggregate contains only those four dimensions and a count. It contains no account, user, conversation or request identifier, question or answer text, birth/chart data, IP address, device/campaign data or event timestamp.

We use these weekly totals only to improve Yana and investigate aggregate astrology-product demand. We do not use them for targeting, individual profiling, purchase attribution or cross-session journeys. Analyst results omit cells below 10 and publish no total that could reconstruct them. Because a counter cannot be linked back to an account, it survives account deletion and cannot be included in an individual export or erasure. This server-side aggregate is separate from first-party web analytics; the browser opt-out does not apply to it.

3.3 Android local data

The App keeps limited app-private state on the phone:

• Native cookie store: the secure server session cookie
• SecureStore: account ID/email marker, theme and Yana consent markers, and a question-only pre-auth Yana draft for at most 24 hours
• App-private SQLite: a saved city and its source (manual, network-estimated or approximate device location), up to eight manually searched recent cities and a small public Panchang cache. A network/device estimate stores only a coarse city centroid, not the raw fix or a location history. Ujjain fallback is visibly labelled and is not saved
• Account-scoped report PDFs until removed, app data is cleared/uninstalled, or sign-out purges them
• A data-export cache file only long enough to hand it to Android's share sheet, then best-effort deletion

Android backup is disabled. Sign-out requests server-session expiry and clears local account state, Yana draft/consent, query cache and downloaded reports. A copy you deliberately save or share is controlled by Android and its destination.

3.4 Data we do not collect or use

We do not use advertising or cross-app tracking SDKs, collect camera or precise/ background/continuous GPS data, sell personal data, create predictive marketing segments from birth data, or embed an engine/payment secret in the App. The App calls astroyana.com; a report may follow a short-lived authorised HTTPS redirect to Cloudflare R2. It never contacts the computation engine directly.

The optional location button uses only a one-shot approximate foreground fix on Android or iOS (When In Use with reduced accuracy by default on iOS). Denial leaves city search available and does not trigger repeated permission prompts. If no saved or validated inferred city is available, the App clearly labels Ujjain as its default calculation location.

4. Legal and service bases

The DPDP provisions cited here commence on 13 May 2027. Before then, Astroyana must still comply with applicable current law, including IT Act §43A and the SPDI Rules where they apply, contractual promises and consumer law.

4.1 Consent and actions you request

We record explicit consent where a feature asks for it, including Family Vault, Yana, marketing and reminders. The record can include scope, wording/version, time and available request metadata. Family Vault saving fails closed if its required attestation cannot be recorded.

Submitting a calculator, saving your own chart, requesting sign-in, downloading a report, paying, exporting or deleting is also an instruction to process the data needed for that action; it does not imply unrelated marketing consent. Feature-specific consent can be withdrawn in its controls or through [email protected], without invalidating earlier lawful processing.

4.2 Contract, law and security

We process what is necessary to provide a requested or purchased service, keep tax records, answer a binding legal demand and protect the service. From DPDP commencement, a §7 "certain legitimate use" will be relied on only when its facts fit a listed category. We do not treat "fraud prevention" as a free-standing §7 category or use §7 for marketing or unrelated profiling.

4.3 Authentication

• Magic link (web): valid for 24 hours, single-use
• One-time code (app): a 6-digit code valid for 10 minutes, single-use

Both produce the same server-side session and host-only cookie (§13).

5. Birth data and reports

Birth date, time and place are highly identifying and receive extra safeguards.

5.1 Stored encryption and transport

Birth columns are encrypted at rest with AES-256-GCM before PostgreSQL storage. The deployment key is separate in Coolify environment variables on a Hostinger KVM2 VPS and is not committed to source control. The same application- level encryption covers saved people's birth data and stored Yana text.

Connections from the client through Cloudflare to origin use TLS 1.2 or higher and Full (Strict) mode. The origin-to-PostgreSQL container hop is not currently TLS-enabled; both are on the same Mumbai host and private non-public container network. Sensitive columns remain application-encrypted before database storage.

5.2 Decryption boundary

Birth data is decrypted in memory for report computation, to derive chart facts needed by Yana, or for your export. Raw natal date/time/place fields are not included in Yana’s structured calculation packet. For Numerology, your entered name/current name and optional date of birth are used on Astroyana’s server; §5B explains that the provider receives resulting findings rather than those raw inputs. User-authored questions, history and clarification may themselves contain personal details. Decrypted fields are excluded from application logs and transactional/marketing emails. Error telemetry uses PII scrubbing and is not a copy of user data.

5.3 PDF storage

PDFs are encrypted at rest by Cloudflare R2. A download uses a short-lived, single-use bearer grant. PostgreSQL stores only its SHA-256 hash and atomic redemption. The raw grant remains in a URL fragment until submitted in a bounded POST body; successful redemption returns a bounded HTTPS redirect to R2.

Birth data remains while the account exists. Account deletion and backup handling are in §9 and §11.

5A. Family Vault

Family Vault is server-feature-gated; when disabled, saving and reading people does not occur. When enabled, you may save another adult's name/nickname, relationship and birth details for a reading. The details are AES-256-GCM encrypted. We do not collect their email or phone.

You must confirm that the adult gave permission. We record the wording, date and available request/device details under consent scope saved_person_attestation, version saved-person-v2. The shared web and Android validators reject anyone under 18, and Family Vault has no parent or guardian minor path.

An earlier entry created while the person was under 18 remains a delete-only list entry. It cannot be opened, edited, exported or used for a reading, and reaching 18 does not reactivate the old attestation. You may remove it and add the person again only after they are 18 and have given permission.

An unrestricted saved adult remains until you delete them or the account and appears in your export. Every entry is removed on account deletion. If the person contacts us directly, we may verify and remove their details. We use those details only for requested readings, never sell them and do not opt them into external model training.

5B. Yana, the AI astrologer

Yana is server-feature-gated. When enabled, an external language service receives your question, relevant recent conversation context (earlier questions and answers), any clarification question and answer, and a structured calculation packet containing the computed findings needed for the selected mode. The packet excludes raw birth records, account identifiers and account details. It can contain derived chart or calculation findings, including dates and placements.

For Numerology, the name/current name and optional date of birth that you enter are used on Astroyana’s server to calculate the reading. The structured packet sent to the external language service contains the resulting findings rather than those raw inputs. User-authored question, history and clarification text is sent as text; personal details included in what you type may therefore also be shared. The service removes unmistakable email, phone and account identifiers from that text, but this does not identify or remove every personal detail. Account email, phone number and payment data are not sent as account fields.

Astroyana does not opt conversations into model training. Under Anthropic's standard commercial-API terms, input/output is not used to train generative models by default and is normally deleted from its backend within 30 days, subject to material retained longer to enforce its Usage Policy or comply with law. Astroyana separately keeps encrypted conversation text for 180 days. You can delete one or all conversations; export and account deletion include them. The wallet ledger has no chat text.

After a completed answer, you may separately choose to spend one existing whole credit to create its private audio. Only the normalised, final answer text and a fixed locale/versioned voice configuration are sent server-to-server to Google Cloud Text-to-Speech. We do not send the question, birth or chart data, account identity, conversation history, payment data, or arbitrary client text to Google for this feature. Generation starts only after this explicit unlock. Google describes Cloud Text-to-Speech as stateless and resourceless and states that it does not log customer text or generated audio. Astroyana stores the completed private audio in Cloudflare R2 while its source answer exists, subject to the same conversation/account deletion controls and 180-day retention. An R2 lifecycle rule just beyond that period is a failsafe, not the primary erasure mechanism. De-identified character, request, cost and time totals may remain for the accounting/control window, without a user, answer, audio or conversation content link.

Answers disclose "Calculated by Ganaka, voiced by Yana". They are informational and not professional advice or a legally significant automated decision.

5C. Android app

The App is server-backed. Identity, money, credits, saved charts and report authority remain on astroyana.com. It holds no engine credential.

• OTP sign-in sets the same server session as the Site
• Export and deletion are available in-app after a fresh OTP re-authentication making the session less than 5 minutes old
• Android offers in-app credit and report purchases through Google Play Billing. Astroyana's server verifies each purchase before crediting the shared wallet or fulfilling the report. Google Play processes payment; Astroyana does not receive full card or bank credentials.
• Optional reminders and report-ready notifications can be enabled in App settings. Registration requires an explicit user action and OS notification permission. The App sends an Expo push token and installation/build metadata to Astroyana; Expo’s Push Service relays notifications to the device platform
• The App includes the Google Play Billing and notification libraries needed for those features. It has no advertising, cross-app tracking, device-attestation or mobile crash-reporting SDK
• Store Data Safety declarations conservatively cover birth/astrology data, third-party AI processing and deletion

Optional microphone dictation. English dictation in the Android app starts only when you tap the microphone and grant the OS permission. Android's selected speech-recognition service processes your speech to produce editable text. Processing may occur on the device or through that service's network, depending on device support and settings. Astroyana does not receive or retain the raw microphone audio. Only text you choose to submit is sent to Astroyana; you can edit or discard the draft and use typing instead. The selected speech service's privacy terms and your device/account settings govern its own processing and retention. This input dictation is separate from the paid answer-audio playback described in §5B.

6. Uses

We use data to deliver the selected service, authenticate, support users and redress grievances, run limited first-party web analytics and operational events, monitor performance/security, prevent abuse, and comply with law/tax duties.

We do not market without separate opt-in, sell/rent data, create unrelated profiles, or opt birth data, saved-person data or Yana conversations into external model training.

7. Processors

Provider processing is governed by applicable service/data terms. This table does not claim that every provider signed a separately negotiated agreement. We update the Policy before adding a materially new processor or data use.

The processors relevant to these features are Google Play for Android in-app credit and report payments and purchase verification, Expo Push Service for optional notification relay, and Anthropic, PBC for the Yana question, relevant recent conversation and clarification text, and mode-specific structured calculation findings described in §5B. The Yana packet does not include raw birth records or account fields; details typed into user-authored text may still be present.

8. International transfers

Cloudflare, Sentry, Stripe, Anthropic and Google Cloud may process outside India under their applicable transfer terms, including Standard Contractual Clauses where they apply, plus data minimisation and encryption. Zoho and Hostinger use the listed India locations. If India restricts a country under DPDP Act §16, we will comply when that provision and restriction apply.

Google Play and Expo Push Service may also process the Android purchase or notification information described in §§5C and 7 outside India under their applicable transfer terms.

9. Your controls and rights

Astroyana provides these controls now as service commitments; the cited DPDP rights commence on 13 May 2027.

9.1 Access and export

Use https://astroyana.com/account/export or the App. The JSON includes decrypted birth data, saved people and Yana conversations; it is limited to once per 24 hours and needs a session authenticated within 5 minutes. An accessible encrypted email export can be requested from [email protected].

9.2 Correction and erasure

Correct profile data in account/App controls or email us. Delete the account at https://astroyana.com/account/delete or in the App after fresh OTP verification.

Deletion immediately disables the account, followed by a 30-day recovery grace period. If an active payment dispute requires a legal hold, hard deletion is deferred until final reconciliation and the account remains disabled. The daily hard-delete job then removes the user, birth fields, Family Vault and consent records, Yana text, R2 reports, consent grants, sessions and user-linked login/web/computation events.

We retain only what law or security requires: audit entries until one year after creation with the account link set to NULL; anonymised tax amounts/fields for the statutory period (typically 7 years); and support/refund records with free text redacted. Encrypted backups are purged within 30 days.

9.3 Grievance and nomination

Send a grievance to [email protected]. We acknowledge a consumer grievance within 48 hours and seek redressal within one month. From 13 May 2027, an eligible unresolved DPDP grievance may be escalated to the Data Protection Board of India.

You may nominate a person to exercise future DPDP rights on death/incapacity by providing their contact and notarised authority.

10. Children

Accounts and Android are for people 18 or older. Android Family Vault blocks minors. A website report form may presently accept a parent/guardian attestation, but we do not represent it as DPDP Rule 10 identity/age verification. Before 13 May 2027 we will deploy compliant verifiable parental consent or disable every minor pathway. We do not profile, behaviourally monitor or target ads at children.

Report suspected child data to [email protected]. We will suspend processing, delete unless a specific law requires retention, investigate and respond within 7 days.

11. Retention summary

Android purchase-support records. Operational records supporting purchase verification, notifications and recovery become eligible for reviewed deletion no earlier than 180 days after verified final resolution. Store financial-event records are retained for at least 8 years after the relevant Indian financial-year end; later statutory deadlines, unresolved payments, refunds or recovery work, and legal holds may extend that period. These controls do not delete orders, purchases, credits, reports or tax invoices, which follow their separate lifecycle and legal-retention requirements. Eligibility is reviewed; it is not a promise of automatic deletion on a fixed anniversary.

12. Security and breach response

Controls include AES-256-GCM sensitive-column encryption; R2 encryption; TLS from client through Cloudflare to origin; passwordless authentication; host-only HttpOnly cookies; rate limits; Turnstile; Coolify secret storage; gitleaks; bounded audit logs; HIGH+ dependency scanning; encrypted backups; and a documented incident runbook.

The same-host private database and internal engine hops are not described as end-to-end TLS. A quarterly restore procedure exists, but the first full isolated live restore has not yet been completed; we do not claim verified live restore readiness.

Affected individuals are notified without delay when required. From the applicable DPDP commencement, the Board receives initial intimation without delay and further particulars within 72 hours unless it allows more time.

13. Cookies and browser storage

These are strictly necessary. We use no advertising or third-party tracking cookie and no cross-site profiling. First-party analytics uses a temporary per-tab browser-storage ID and published opt-out. Where applicable law requires prior consent for non-essential storage, the analytics client must be consent- gated or disabled; opt-out alone is not treated as consent.

14. Policy changes

We publish a new version at https://astroyana.com/privacy and record its hash in policy_versions. Before a material expansion we give advance email notice, seek fresh acceptance where required and allow deletion before it applies. Previous versions are available from [email protected].

15. Contact

Use [email protected] for privacy rights and grievances and [email protected] for general questions. Contact details and response times are in §1.1. The Data Protection Board exists; relevant complaint provisions commence on 13 May 2027 and we will publish the filing route when available.

16. EU / EEA / UK users

For these users, SNAZZYWORKS is controller. Processing to calculate/deliver a service or web payment relies on contract (GDPR Art. 6(1)(b)); optional Family Vault, Yana personalisation and communications rely on consent (Art. 6(1)(a)); proportionate security/operations and aggregate analytics rely on legitimate interests (Art. 6(1)(f)); tax retention relies on legal obligation (Art. 6(1)(c)).

Subject to law, you may access, rectify, erase, restrict, port, object, withdraw consent and avoid solely automated decisions with legal or similarly significant effect. Astrological/Yana output has no such effect. We answer within one month, extendable by two months for complexity with notice. You may complain to your local supervisory authority, including the UK ICO. International transfers use the safeguards in §8.

17. App connection summary

The App calls astroyana.com. Report redemption may follow a server-authorised HTTPS R2 redirect. Private Yana voice playback instead streams through an Astroyana same-origin endpoint using a short-lived, single-purpose header token; the App is not given a direct R2 URL. Identity, credits, purchases, saved charts and report access remain server-authoritative. The App stores only §3.3's limited local state. It has no advertising, cross-app tracking, device-attestation or mobile crash-reporting SDK. Android credit and report purchases use Google Play Billing. Optional reminders and report-ready notifications are available after user action and OS permission; the App sends an Expo push token and installation/build metadata through Expo Push Service.

Appendix A: Legal references

• DPDP Act 2023 — https://www.indiacode.nic.in/indiacode/handle/123456789/22037?view_type=browse
• DPDP Rules 2025 and commencement — https://www.meity.gov.in/documents/act-and-policies/digital-personal-data-protection-rules-2025-gDOxUjMtQWa
• IT Act 2000 §43A and SPDI Rules 2011 — India Code
• Consumer Protection Act 2019 and E-Commerce Rules 2020 — India Code / Department of Consumer Affairs
• GDPR / UK GDPR — Regulation (EU) 2016/679 and UK data-protection law

Appendix B: Document control

END OF DOCUMENT.