Од ·

Corrections

We publish guidance on privacy, GDPR, HIPAA, and AI compliance, and we would rather hold a correct record than a quietly edited one. This page explains how to report an error, how we handle it, and what we have corrected.

How to report an error

If you find a misstated fact, an outdated citation, a broken claim, or a number that no longer matches our product, tell us. Include the page and, if you can, the source that shows the correct position. We read and respond to every report, and you do not need an account to send one.

How we correct

When a report identifies a genuine error, we fix it promptly. Where the change affects the substance of the guidance — not a typo or formatting — we note the correction on the affected page and update its modified date to reflect the real change. We do not silently rewrite the record or reset dates to appear fresh.

Public corrections log

Material corrections are listed below, newest first. An empty log means no substantive corrections have been required since we began tracking them — not that the page is unmaintained. Routine copy edits and clarifications that do not change meaning are not logged.

Corrections log

  • 2026-06-19 — Blog articles (publication metadata): Audited every article's dates and corrected a number of posts that showed a future or inconsistent publication date. Each article now displays its true first-publication date, with a modified date that never precedes it. No article text was changed — only the dates were brought back into line with the actual record.

Report a correction

Spotted something wrong? Send it over and we will look into it and respond.