Accountable publishing
Corrections policy
Reports are prioritized by their effect on calculation accuracy, privacy, safety, accessibility, and the clarity of user guidance.
Responsible owner: ReadAstrology Editorial & Calculation Team
Reviewed: 2026-07-18
Core commitments
- Calculation and privacy issues first
- Minimum sensitive data
- Material updates change review dates
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.
What can be reported
Users may report incorrect calculations, broken references, misleading interpretation, outdated provider information, privacy concerns, inaccessible interactions, or typographical errors.
A useful report includes the page URL, the observed result, the expected result, and enough non-sensitive detail to reproduce the issue.
How reports are reviewed
Calculation and privacy reports receive the highest priority. The team checks source data, software behavior, historical timezone assumptions, calendar boundaries, and the published explanation.
Reports that include private birth data should be minimized. Users should never send passwords, payment-card numbers, access tokens, private keys, or full identity documents.
How changes are documented
Material changes update the page's reviewed date and, where useful, add a correction note. Cosmetic edits do not create a false impression that the underlying content was recently re-researched.
A correction can change a calculation, wording, source, disclosure, internal link, or interface behavior. It does not guarantee that search engines or cached copies update immediately.
Frequently asked questions
Will every correction request change the page?
No. The team first verifies the issue. Requests that conflict with the documented method or available evidence may be declined with an explanation.
How should I report a private-account problem?
Use the contact page and provide the minimum information needed to locate the issue. Do not include passwords, payment details, API keys, or unnecessary birth data.