Privacy Policy
Last updated September 27, 2026
Operator and policy status
Antara is personally operated by Yashraj Jain, trading as Antara, in Bengaluru, Karnataka, India. For privacy questions or complaints, email support@antara.digital.
Business contact address: Haralur, Ambalipura, Bengaluru, Karnataka 560102, India.
Yashraj Jain is the complaints and privacy contact. We acknowledge formal complaints within 48 calendar hours of receipt and aim to resolve them within 30 calendar days of receipt. These timeframes include weekends.
Antara is in development. This page describes the current application. Complete processing locations and retention periods still need to be confirmed and published before public launch.
What we collect
- Account data — your email address and a hashed password, held by our authentication provider (Supabase).
- Birth details — dates, times, and places you save as profiles or submit for a chart, including any uncertainty you record about the birth time. These details support chart calculations and readings. Saved readings retain a copy of their birth inputs.
- Readings — your questions and the generated readings, kept so you can revisit them and so recent context can inform follow-up readings.
- Saved insights and private notes — passages you choose to keep, their source details, and reflections you write. Notes are stored for your account and are not sent to the reading model or used as reading feedback.
- Payment records — order and credit-ledger entries and payment references. Razorpay collects payment details; Antara’s payment records do not store full card numbers or banking credentials.
- Feedback and outcome reports — your reading ratings, comments, and any outcome reports you submit. Aggregate feedback helps identify material for review; it does not automatically change model weights or prove that a prediction is accurate.
- Support reports — the category and message you submit, an optional reading reference, review status, and any recorded response. Reports are linked to your account and are not used to train the model. Email sent to support is held separately by the mailbox provider.
- Coverage review — when source coverage is missing, the application can retain the question and chart-derived facts in a restricted review queue, linked to the reading and account.
What we don’t do
- No advertising, no selling of data, no third-party analytics trackers.
- Customer readings and private notes are not automatically used to train model weights.
- Birthplace search and chart calculations run on Antara’s server. Generating a reading uses the model inputs described below.
Services and model inputs
- Vercel — hosts the website and application API. Requests pass through Vercel to reach the application.
- Supabase — hosts authentication and the application database, including saved account data and readings.
- Ollama and ngrok — the current model service runs on Antara’s local computer. The application connects to it through an authenticated HTTPS gateway reached through ngrok. Model inputs include chart-derived facts, source material, your question, and relevant recent conversation context. Self-hosting does not establish a retention policy for the host, tunnel provider, or their logs.
- GoDaddy/Titan mail — provides the support mailbox and the configured sender for account emails.
- Anthropic — supported as an optional model provider, but not used by the current Ollama deployment. Enabling it would send reading inputs to Anthropic and require updated provider disclosures. This application does not itself control a provider’s retention practices.
- Razorpay — payment processing when recharges are enabled.
Retention and deletion
Saved readings, birth profiles and notes are kept until you delete them or your account, subject to the linked-content deletion rules below. We do not automatically delete this content merely because your account is inactive.
Account deletion closes access and removes profiles, conversations, readings, saved insights, notes, support reports, feedback, outcome records, and linked coverage-review entries from the application database. It also requests deletion from the authentication provider. If that request cannot be confirmed, the app reports authentication deletion as pending; account access remains closed. The sign-in identifier is retained to retry the provider request and cleared when provider deletion is confirmed. Contact support if authentication deletion remains pending.
Deleting a conversation removes its readings, saved insights, notes, linked support reports, and linked review entries. Deleting an individual insight leaves its original reading intact. Editing or deleting a profile does not rewrite birth details already stored with past readings.
Payment and credit records remain under a pseudonymous identifier for reconciliation. They are not fully anonymous: payment references may still link to records held by the payment provider. A pseudonymous closure marker prevents old login tokens from reopening an account. Aggregate feedback and outcome counters also remain after source records are deleted.
Deletion from the live database does not automatically remove external backups or provider logs. Their retention and deletion procedures, and the handling of older review entries without a recorded owner, remain launch requirements.
Your rights
You can access your data in the app, correct it by editing profiles, and erase it by deleting your account. You can edit and delete private notes, and download your account data as JSON from Settings. You can also export saved insights from Readings → Saved insights. For anything else — export requests, questions, complaints — write to support@antara.digital.