Contact & corrections
Help improve the record
The most useful reports are specific, sourced, and safe to discuss in public. Choose the route that matches what you found.
Dataset
Report a correction
Flag an incorrect date, milestone label, version, source link, or missing release. A prepared issue form will prompt for the evidence needed to verify it.
Open a correction reportProduct
Suggest an improvement
Report a broken page, accessibility problem, confusing forecast, or useful feature idea through the public project tracker.
Open a feedback reportWhat to include in a data correction
- The operating system and complete version number.
- The milestone label, such as Beta 3, Public Beta, RC, or Public Release.
- The date or value currently shown and the proposed correction.
- A direct Apple source when possible, or a contemporaneous independent source for an older record.
- Context about time zone, build revision, or audience if it explains an apparent conflict.
Read the sources and editorial policy for the verification process.
Public reports and private information
GitHub issues are public. Do not post email addresses, phone numbers, account details, credentials, private API keys, unpublished personal information, or sensitive security details. Remove tracking parameters from source links when practical.
For a privacy question that requires a private reply, email business@bradleyfosler.com. This role-based address is for site privacy matters, not Apple product support.
What happens after a report
Reports are reviewed on a best-effort basis. A correction is not accepted only because it was submitted; the proposed change is checked against the strongest available evidence. The record may be updated, annotated, left unchanged, or held until the conflict can be resolved.
There is no guaranteed response time. Please avoid filing duplicate reports or using several channels for the same issue.