Data practices

Privacy notice

ReadAstrology is designed to minimize public-calculator retention and keep saved profiles, readings, and account controls inside authenticated workflows.

Review how the system works

Responsible owner: ReadAstrology Editorial & Calculation Team

Reviewed: 2026-07-18

Core commitments

  • Public previews are not saved
  • Private data stays in authenticated flows
  • Provider processing is disclosed

These pages describe current product and editorial practices. They are operational disclosures, not legal advice, certification, or a guarantee that every provider or feature will remain unchanged.

Information the service may process

Depending on the feature, ReadAstrology may process account details, birth date and time, birthplace or coordinates, names supplied for numerology, saved profiles, reading outputs, usage status, support messages, and billing status.

Public calculator endpoints are designed to return a focused result without writing the submitted birth data to Firestore or local storage. Network and security logs may still contain technical metadata such as time, route, status, and IP-derived rate-limit information.

Private workspaces and service providers

Saved profiles and readings use Firebase Authentication and Cloud Firestore with server authorization and security rules. Google Cloud runs backend calculation services, Vercel serves the production web interface, and Stripe processes checkout and billing data.

AI-enabled features may send the minimum structured context needed for the request to OpenAI's API. Payment-card details are handled by Stripe's payment interfaces rather than stored directly in ReadAstrology application records.

Choices, retention, and contact

Users can avoid saving a public calculator result, delete supported saved records through the product, and request account or privacy assistance through the contact page. Some records may be retained where necessary for security, billing, dispute resolution, or legal obligations.

ReadAstrology does not intentionally sell personal information. Provider processing, locations, and retention are also governed by each provider's published terms and configuration.

Frequently asked questions

Does a public calculator save my birth details?

The public calculator endpoint is designed not to write those inputs to Firestore or local storage. Technical request logs and provider infrastructure may still process limited metadata needed to operate and secure the service.

Who processes payments and AI requests?

Stripe processes payment flows. OpenAI may process structured prompts for AI-enabled features. Firebase, Google Cloud, and Vercel support authentication, storage, backend, and hosting functions.