No accounts or login
Pairutham has no user accounts and no login. You provide birth details only when you ask us to calculate an assessment.
Information you provide
For each person, you submit a name, birth date, exact birth time, and birthplace. The birthplace string is sent to the Open-Meteo geocoding API to resolve coordinates and a timezone for the calculation.
At checkout, payment information is entered on Stripe. Name, email, and card details go to Stripe for payment processing, not to us.
What is stored
Cloudflare D1 stores an assessment ID, creation time, purchase time when applicable, a Stripe checkout session reference when applicable, partner display labels, and the generated chart and compatibility result.
The partner label fields contain only each person's name and resolved birthplace. They deliberately do not store the exact clock time, coordinates, or utcIso. They also omit the submitted birth date and timezone. Separately, the generated result contains calculated chart data, including a derived UTC birth instant (utcIso), timezone, and calculated planetary and ascendant longitudes. It does not contain the submitted exact clock-time string or the geocoding coordinates.
Paid reports may also store a generated plain-English narrative in the report_narratives table, keyed to the assessment ID. That row is deleted with the assessment under the same seven-day cascade.
The report fulfillment record stores the Stripe session ID, assessment ID, Stripe event ID, and fulfillment time. In your browser, session storage temporarily keeps the current snapshot and Stripe session reference so the result can survive a reload in that browser session.
Seven-day retention
We retain assessment records for seven days after creation. After seven days, expired assessments are purged opportunistically inside normal assessment request processing. There is no cron job, so the purge runs when that request path next runs rather than at an exact scheduled second. Purging an assessment also removes its linked narrative row. The fulfillment record (Stripe session ID, Stripe event ID, and fulfillment time) is kept, with its assessment link cleared, so a payment can still be reconciled against a Stripe receipt.
Third parties
- Stripe processes the payment. Name, email, and card details are provided to Stripe, not to Pairutham.
- Open-Meteo geocoding API receives the birthplace string and resolves it to coordinates and a timezone for the astrology calculation. Requests identify the service as Pairutham.
- OpenRouter receives a privacy-filtered chart payload for paid reports so a third-party language model can draft the plain-English reading. That payload includes each person's name and resolved birthplace, nakshatra and pada, graha placements, Navamsa summary, Manglik status, and dated dasha periods. Pairutham requests that OpenRouter deny provider data collection for these calls. The prose is generated by a DeepSeek model via OpenRouter, not on Pairutham's own servers.
- Cloudflare hosts Pairutham and provides the D1 database where assessments, report fulfillment records, and report narratives are stored.
Cloudflare Web Analytics provides privacy-first, cookie-free aggregate page views and excludes URL query strings.
Questions
For privacy questions, email hello@pairutham.com.