Consent Model
Learn how AutoCore records configurable consent choices without claiming legal compliance.
The consent model records a decision and its policy-version context. It is a configurable platform capability that must be reviewed for the target market; it is not an automatic GDPR, CCPA, KVKK, ePrivacy, or other legal-compliance certification.
Current receipt shape
ConsentReceipt stores a consent identifier, policy version, necessary,
functional, analytics, and marketing decisions, source, locale, decision time,
expiry, and timestamps. The schema intentionally does not store an IP address,
user agent, browsing history, or account identifier in this privacy-minimized
receipt model.
Lifecycle
- The public surface presents the configured consent choices.
- A decision is recorded with locale, source, policy version, and expiry.
- A later policy version can create a new receipt rather than rewriting the old decision.
- Withdrawal or change is represented by a new decision and downstream feature gating; the detailed interaction procedure is an Admin/privacy phase concern.
Necessary cookies are enabled by the current privacy-by-default design. Optional categories require affirmative choice in the current implementation. Exact categories must not be expanded beyond the source-backed model.
The policy relationship is contextual: a policy acceptance record answers what a user accepted, while a consent receipt answers what optional processing choices were recorded. Neither record is legal advice.