1. Imported source records
Approved repository syncs can add or update API records without a manual review of every new row. Source attribution and observation dates are retained. This automation is distinct from publishing a user comment or accepting a commercial claim. We can hide, correct or investigate a record when a concern is raised.
2. Submission and editorial review
Provider claims, promotion requests and corrections enter a private owner queue. Approval is required before a submitted change is applied publicly; approval status alone does not automatically rewrite the archive. Blog drafts require approval of the exact revision before manual or scheduled publication. AI-assisted drafts remain subject to that gate.
There is currently no public comments feature in this deployment. If comments are added, they must remain private until approved, clearly distinguish a public display name from private contact data, and provide a removal/report route. Moderation does not replace a privacy notice, lawful processing basis or retention policy.
3. Material we do not accept
Do not submit unlawful content, malware, scams, impersonation, fabricated endorsements, private credentials, unnecessary personal information, harassment or material you lack permission to share. Criticism and evidence-backed corrections are welcome; payment does not buy immunity from review.
4. Corrections, removal and rights reports
Identify the affected URL, the precise issue and supporting public evidence. For privacy or rights concerns, use the private contact centre rather than posting sensitive evidence publicly. Requests may result in clarification, a correction, restricted display, removal or a reasoned decision. Search engines and independently copied content are outside our direct control.
5. Reconsideration and accessibility
If you disagree with a content or privacy decision, request a second review and explain what was missed. Do not include another person’s private information unnecessarily. You may also report accessibility barriers and ask for the information or request process in an accessible format. We do not claim independent WCAG certification.