Information processed
- Correction content: affected page, issue category, description and optional evidence URL.
- Optional contact data: an email address supplied for clarification.
- Security data: a keyed request identifier used for correction-form rate limits; the raw IP is not stored in the correction queue.
- Operational logs: request, error and security information retained by the application or hosting infrastructure.
- Audience measurement: page-view and referral information when analytics is enabled.
- Administrator account data: authentication details required to access the protected review queue.
Why information is used
Information is processed to deliver the website, protect it from abuse, investigate corrections, communicate about a submitted report, maintain an audit trail, diagnose failures and understand aggregate use of the service.
Retention and public disclosure
Correction email addresses and rate-limit identifiers are cleared when a report is resolved, rejected or marked as spam. A public correction entry may retain the affected page, resolution and resolution date, but never the reporter's email, request identifier or private administrative notes.
Do not submit sensitive personal information. Evidence links should point to public sources and must not contain access tokens, credentials or private file URLs.
Service providers
Hosting, database, authentication, security and analytics providers may process limited data to provide their services. Their own terms and privacy practices apply to that processing.
Questions and privacy requests
Use the correction form with category Other and clearly label the submission as a privacy request. Include only the information needed to identify the relevant correction submission. An optional email is required if a reply is requested.