Trikona Privacy Policy
1. Who this policy covers
Trikona is a practice tool for astrologers. This policy describes what we collect about you, the practitioner (your account), and how we handle your clients' birth data on your behalf — the two are different relationships, covered separately below.
2. Your account data (we are the data fiduciary)
For your account, Trikona handles your email address, display name, password hash, hashed API tokens, browser or native sign-in sessions, subscription and payment references, settings, and consent records. If you choose Apple or Google sign-in, we also store the provider's account identifier and the email or name it supplies. We use this information to sign you in, run your account, record your choices, and manage any subscription.
Support requests contain the subject, messages, and account reference you provide. Operational logs and optional crash reports contain technical details such as the route, time, app version, error, and device or browser information. Trikona accounts are for adults (18 or older). If we learn that an account belongs to someone under 18, we will close it and delete its data; write to privacy@trikona.app.
3. Your clients' data (we are a data processor)
When you add a client — their name, birth date, birth time, birth place, and any consultation notes — you are the data fiduciary for that record; you are responsible for having a lawful basis (typically consent) to hold it and for telling your client what you use Trikona for. We process it only on your instructions: to calculate the chart, keep it available in your client list, and act on your export/delete requests. We do not use client records for any purpose beyond running the product for you, and we do not sell any data.
4. Optional AI processing
When you use Copilot, and only after you choose to allow AI processing in Trikona, we send the chart-derived information needed for your question and the question you enter to the configured AI provider to generate the Copilot answer. The provider is Anthropic or OpenAI, selected by Trikona's deployment. The input safety check sends your question to that provider before answer generation. When Trikona's draft safety check is enabled, OpenAI also receives the generated draft answer only to perform an independent safety check before release; this is separate from answer generation and may apply only to some answers. Trikona does not add your account password or email to this request. Avoid including unnecessary client-identifying details. You can decline or withdraw consent in Settings → Account; withdrawal blocks future AI calls. An AI call already dispatched may complete. Trikona records the purpose, notice version, decision, and timestamp in your account export until erasure.
5. Encryption and storage
Personally-identifying fields (names, birth details) are encrypted at rest; the database never stores this data in plaintext. API tokens are stored hashed and shown to you once at issuance. The live database is hosted on Railway with a persistent volume. Encrypted off-site backups can also be stored in Cloudflare R2. Other providers receive the limited data described in §7; storage and deletion periods are described in §8.
If a personal-data breach affects you, we will tell you and notify India's Data Protection Board without delay. We will explain what happened, what data was affected, what we have done, and what you can do. If your clients' data is affected, we will contact you promptly and help you notify them. You can reach us at privacy@trikona.app.
6. Export and deletion
You can delete a client record at any time from inside Trikona, which removes that client's stored data. For your entire account — including every client record you hold — sign in and open Settings → Account. Choose Export my data to download your data, including your consent history, or Erase account to delete your account and data. You can also email privacy@trikona.app for export or deletion; we acknowledge such requests within 24 hours and complete them within 15 days. Client deletion removes linked practice records from the live database; encrypted backups expire on their separate retention window in §8. You remain responsible for responding to your client's request and any records you hold outside Trikona.
7. Service providers
The providers below receive data when the corresponding service is used or enabled. A listing here does not mean every provider is active for your account. We do not store full card details, sell personal data, or run third-party advertising.
| Provider | Purpose | Data received | Processing location |
|---|---|---|---|
| Railway | Application and database hosting | Account and practice records, support records, and operational logs | The configured Railway service region; the app does not fix a country |
| Cloudflare Turnstile | Signup abuse protection, when enabled | Challenge token, IP address when supplied, and browser/device signals collected by the widget | Cloudflare's global network; no India-only processing guarantee |
| Cloudflare R2 | Encrypted off-site backups and deletion records, when configured | Encrypted database snapshots and deletion identifiers needed to prevent erased client/account data returning after a restore | The bucket's configured jurisdiction or placement; the app does not fix a country |
| Sentry | Optional server and app error diagnostics | Scrubbed error text, stack traces, app version, device/browser details, and technical context; app session replay and breadcrumbs are disabled | The Sentry project's region: United States or European Union |
| Apple sign-in | Optional account authentication and revocation on account deletion | Sign-in requests, provider tokens, and Apple account identifiers; Apple returns the email/name you choose to share | Apple's processing locations, which may be outside India; the app does not select a country |
| Google sign-in | Optional account authentication | Sign-in requests, provider tokens, and Google account identifiers; Google returns account email/name | Google's processing locations, which may be outside India; the app does not select a country |
| Have I Been Pwned (Pwned Passwords) | Check new passwords against known breaches | The first five characters of a SHA-1 password hash and the server connection metadata; never the password or full hash | The service's processing network; the app does not select a country |
| Brevo | Account email and operational alerts when selected; a separate waitlist form when configured | Recipient email, verification/reset links, and email contents; waitlist details you submit directly to its form | European Union hosting, including France and Germany |
| SMTP email provider | Account email and operational alerts when configured instead of Brevo | Recipient email, verification/reset links, and email contents | Depends on the configured mail host; contact us for the current provider and location |
| Razorpay | Indian subscription payments when checkout is enabled | Customer and subscription references, plan, amount, payment status, and payment details you enter with Razorpay | India |
| Dodo Payments | Subscription checkout and merchant-of-record services when enabled | Customer and subscription references, checkout details, amount, currency, and payment status | Dodo's processing locations, including international transfers; the app does not select a country |
| Stripe | Alternative subscription processing when configured | Customer and subscription references, plan, amount, payment status, and payment details entered with Stripe | Stripe's international processing locations; the app does not select a country |
| Anthropic | Copilot answers and input safety checks when selected and AI consent is on | Your question and the chart-derived context needed to answer it; the input check receives the question | The provider's processing locations outside India; the app does not pin a region |
| OpenAI | Copilot answers and input safety checks when selected; optional draft safety checks, with AI consent | Your question and chart-derived context for answers, your question for input checks, and the generated draft for draft checks | The provider's processing locations outside India; the app does not pin a region |
| Axiom | Central operational log storage when enabled | Redacted log lines and technical request/error details; email addresses, birth details, coordinates, tokens and URL query strings are removed before sending | United States |
We do not use your clients' birth data or notes to train our own AI models. AI providers handle API requests under their own data-processing terms; this policy does not promise a provider retention setting that has not been confirmed.
8. Retention
| Data | How long we keep it |
|---|---|
| Account and active practice records | While your account is open, unless erased with a client or by the timed purge below; individually removed notes and consultations can remain stored until client or account erasure |
| Soft-deleted saved charts and predictions | The scheduled daily purge permanently removes them once 30 days have passed since deletion or the last update while deleted; linked chart shares, prediction outcomes and conflict copies are removed with them |
| Expired share links and their stored content | Unavailable after expiry; the daily purge removes them once 30 days have passed since expiry |
| Expired sessions and unused verification, password-reset and reauthentication records | 30 days after expiry; used verification, password-reset and reauthentication records are removed 30 days after use |
| OAuth sign-in replay records | Removed as soon as a sign-in observes expiry; the scheduled purge removes stale records 30 days after expiry |
| Closed support tickets and messages | 30 days with no update while closed; an update while closed restarts that period |
| Encrypted backups | A rolling window, configured to 30 days by default; copies can remain after live deletion until that window ends |
| Central logs in Axiom | 30 days when enabled |
| Sentry diagnostics, email and payment-provider records | According to the provider's configured retention and its own record-keeping terms |
Deleting a client removes its linked practice data from the live database. Existing encrypted backups expire separately. After a restore we reapply recorded client and account deletions. Standalone chart and prediction deletions can remain in a restored backup until the backup window ends.
9. International transfers
Your data can be processed outside India by the providers in §7. The Railway service region, R2 bucket placement, Sentry region and SMTP host depend on the deployment configuration; Trikona does not promise that all data stays in India or in one country. Providers' own processing terms apply to their services. Contact privacy@trikona.app for the current locations and available data-processing terms before entering data that requires a particular location.
10. Your rights
As a data principal under the DPDP Act, you can access, correct, or erase your own account data, and withdraw consent, by writing to privacy@trikona.app. As the data fiduciary for your clients, the same rights belong to your clients through you — Trikona gives you the export/ delete tools to honor those requests; the underlying obligation to your client is yours.
11. Changes to this policy
We may update this policy; the effective date above changes when we do, and we will notify you in-app or by email of material changes before they take effect.
12. Contact
Privacy questions or data-rights requests: privacy@trikona.app. General support: support@trikona.app. See also our Grievance Redressal & Contact page.