Sources and references

Responsible owner: ReadAstrology Editorial & Calculation Team

Reviewed: 2026-07-18

Core commitments

• Primary sources first
• Traditional claims are labeled
• Provider disclosures use official documentation

Official provider references

• Firebase and Google Cloud — Authentication, Cloud Firestore, backend infrastructure, hosting support, and security controls.
• OpenAI API — Optional AI interpretation and synthesis after structured calculation evidence exists.
• Stripe — Checkout, subscription, billing portal, payment processing, and payment-security responsibilities.
• Vercel — Production web hosting and delivery for the ReadAstrology frontend.

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.

Source hierarchy

Calculation claims should first use official software documentation, standards bodies, scientific agencies, calendar authorities, or source code maintained by the relevant project.

Secondary sources may provide historical or interpretive context, but they should not replace primary documentation when a technical claim can be checked directly.

Astrology and calendar references

ReadAstrology documents Swiss Ephemeris sources for planetary calculations, IANA timezone data for civil-time interpretation, NASA and JPL material for astronomy context, and official calendar tables for Chinese calendar boundaries.

Traditional interpretations are labeled as interpretive frameworks. A source can document a tradition without proving that symbolic claims predict real-world outcomes.

Provider and policy references

Privacy and AI disclosures link to official provider documentation when describing Firebase, Google Cloud, Stripe, OpenAI, or hosting behavior.

Source links are reviewed when a guide changes materially. Broken or superseded references can be reported through the corrections process.

Frequently asked questions