Not legal advice. This site is an editorial reference. Laws change — always confirm with a qualified attorney in the relevant jurisdiction before recording, and check each page’s last reviewed date.

Corrections log

When we get something wrong on this site, we fix it, log it here with a date, and update the relevant page’s Last reviewed line. This page is the public record of those fixes.

How to report a correction

If you believe a page on this site contains a material error — a wrong consent-rule classification, a misquoted statute, a citation to a repealed section, a misstatement about a court holding, or a platform behavior we have described incorrectly — please report it. Include the page URL, the specific claim you believe is wrong, and, if possible, the primary source that supports the correct version.

Report via the contact page or by email to corrections at recordphonecall dot com.

Substantive legal corrections are queued for re-verification against primary sources and published with the next page revision. Typos and broken links we fix immediately.

What counts as a correction

A correction is a substantive change to the meaning of a page: a wrong statute citation, a wrong consent classification, a wrong description of a case holding, a wrong claim about a platform’s notification behavior. Routine updates — legislative amendments that change the controlling text, regulator guidance issued after our last review, OS releases that change platform behavior — are tracked in each page’s own Update history block, not here. The line we draw: if we got it wrong on our review date, it is a correction; if it changed after our review date, it is an update.

Recent corrections

None to log. As we make corrections, they will appear here, most recent first, each with the page affected, the date, and a one-sentence description of the change.

Severity

Where a correction is consequential — the kind that could lead a reader to make a decision they would not otherwise have made — we add a visible note at the top of the affected page for at least sixty days after the fix, in addition to the log entry here.