Frequently asked questions

Important: these pages are not legal advice. Dummy company name, address, CIN, GSTIN, and officer names are placeholders — have qualified counsel verify them, align subprocessors and retention, and complete any India DPDP / intermediary registrations before you rely on them commercially.

These answers describe the intended product architecture. Cross-check numbers, SLAs, and storefront-specific rules with counsel and live policy pages before launch.

What is Tara?

Tara is a devoted digital companion for your spiritual life — an AI-driven astrology guide, not a human. You receive chart-aware readings and ongoing guidance via text chat and voice. Natural language is generated with Google Gemini, while planetary positions and chart-style context rely on Swiss Ephemeris computation (for example through pyswisseph) — not improvised generic horoscope prose. Read how Swiss Ephemeris guides Tara on the homepage.

Does Tara employ human astrologers?

No marketplace of human astrologers. On the consultant side, Tara is intentionally a digital AI entity— she does not pretend to be a person. The product uses seeded “astrologer” personas (fourteen archetypes in seed data) so conversations stay styled and repeatable without gig payouts or scheduling workflows.

Which platforms are supported?

Mobile apps are Flutter builds targeting iOS and Android. A FastAPI backend powers APIs, Postgres stores durable records, Redis supports session/timer state and caching, Socket.IO carries real-time chat and streaming-friendly flows, and Firebase covers push notifications where configured.

How does authentication work?

Accounts authenticate with JWTs issued after SMS phone OTP and optionally Google Sign-In, aligned with typical India-first onboarding patterns.

How does billing work?

Sessions can be billed per minute for text chat and voice. Timing and margin curves should match what you documented in product economics. Wallet top-ups go through Razorpay; webhooks and wallet ledgers reconcile credits and debits without ad-hoc manual ops.

Is there referral or promo tooling?

The codebase includes scaffolding for promotions and referrals. Treat the exact rules, caps, fraud checks, and copy as configure-at-launch items your growth team validates.

What charts are computed?

Tara aligns with Vedic-style, ephemeris-backed planetary math — not vibe-only narration. Accuracy still depends on correct birth inputs; users should treat outputs as reflective guidance rather than deterministic fact.

How should I interpret Tara's answers?

Outputs blend structured chart context with language generated by models such as Google Gemini. Automated systems can misread nuance — cross-check important choices with trusted humans and regulated professionals where appropriate. Review the Disclaimer alongside this FAQ.

Refunds, disputes, wallets

Published rules live in our Refund & Cancellation Policy and Terms of Service. Razorpay, Apple, and Google each impose overlapping requirements — counsel should reconcile storefront-specific flows (especially subscription renewals and in-app purchase dispute windows) with those documents.

• Document INR tax display quirks on mobile stores.
• Spell out Redis timer edge cases — reconnects, clock drift, cancellations.
• Align SMS OTP costs and abuse throttles with your infra budget.

Where do I download the apps?

Buttons on the home page should deep-link to the live listings. Today URLs are placeholders — populate NEXT_PUBLIC_APP_STORE_URL and NEXT_PUBLIC_PLAY_STORE_URL.

Who do I contact?

Email [email protected] or visit Contact until in-app ticketing ships.