AutoCore Consent Readiness and Security Checklist
A verification checklist for consent UI, receipts, withdrawal, and provider gating.
Verify consent in a clean browser profile and in a previously decided profile. Confirm that optional providers are absent before consent and are removed after withdrawal.
Release candidate source
This article reflects the audited AutoCore source revision 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60 and immutable release-candidate tag v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f. Configuration and external provider behavior remain deployment-dependent.
Source boundary
| Control | Source-verified behavior |
|---|---|
| Default | No optional provider is mounted before a valid category decision. |
| Persistence | Cookie attributes, policy version, locale, and expiry are visible in safe test evidence. |
| Withdrawal | Withdrawal removes optional effects and records the updated decision. |
| Privacy | Evidence contains category outcomes and timestamps, not real user identifiers or browser data. |
High-risk operation
Use explicit authorization, a written reason, a confirmation gate, and post-action verification. Documentation does not grant permission to change a deployment.
Operational controls
Use the smallest verified control for the task. Keep provider, host, legal, and operator responsibilities separate from application behavior. When a control is not implemented or not verified, leave it disabled or mark it as a limitation.
Result format
For each item, record pass, fail, or not_applicable, the evidence reference, the reviewer, and the next action. Do not paste credentials or raw provider payloads into the record.
Verification
Verify the route, relevant API or configuration state, negative path, audit/evidence result, and public effect before closing the task. Record unknown or configuration-dependent behavior as a limitation.