Choose how optional technologies are used.
Control optional cookies and similar technologies used on ZoikoSuite public web experiences. Strictly necessary technologies remain active only for approved essential purposes. Your available controls may vary by region, purpose, and recognized privacy signals.
Set your choice by category
Strictly Necessary
Supports approved essential functions — security, authentication, routing, and storing your privacy choice itself. Not toggleable, but every item is inspectable.
Functional / Preferences
Remembers optional settings or enables non-essential convenience.
[ n ] technologies [ n ] vendors Last verified [ date ]
If disabled, some optional convenience settings may not be remembered between visits.
Analytics / Measurement
Measures visits, performance, content effectiveness, or interaction patterns.
[ n ] technologies [ n ] vendors Last verified [ date ]
If disabled, aggregate measurement of this visit will not occur.
Advertising / Marketing
Rendered only if the registry proves current use.
Not currently used
Signals are inputs to the same resolver — not a hidden system
Global Privacy Control
Effect: [ plain-language explanation of what the signal changes for this visitor. ] Where a stored choice conflicts with a stronger applicable signal, the interface shows which state wins and why.
What this choice applies to
| Question | Answer Pattern |
|---|---|
| What does this choice apply to? | This browser/device and the stated domain scope, by default. |
| How long is it remembered? | [ Registry/ruleset-defined preference duration — stated only when verified. ] |
| Does sign-in sync choices? | Not claimed unless implemented, legally reviewed, and explicitly disclosed. |
| What if storage is blocked? | The preference may not persist; the safe default behavior applies. |
| Does it control product telemetry? | Only public/web technologies within the defined scope — authenticated product telemetry has separate governance. |
A toggle is not a valid control until it's enforced
| Step | System Behavior | UI Feedback |
|---|---|---|
| 1. Resolve | Evaluate region/context, stored receipt, signal, current ruleset. | Load current effective state. |
| 2. Edit | User changes category/purpose state. | Unsaved-change indicator. |
| 3. Save | Validate allowed combination; create/update consent receipt. | Progress label; duplicate submit disabled. |
| 4. Enforce | Broadcast effective state to tag manager/client code/server-side systems. | Success is not shown before enforcement is acknowledged. |
| 5. Confirm | Store event/evidence with minimal data. | "Preferences saved" plus a summary of changed categories. |
| 6. Clean up | Stop disallowed optional technologies; remove optional storage where required. | Explains that blocking future use and deleting existing data are not always the same thing. |
Errors never silently default to acceptance
| Failure | Safe Behavior | User Message |
|---|---|---|
| Consent service unavailable | Necessary only in consent-required context; no optional activation. | "We could not load optional preferences. Necessary technologies remain active. Retry." |
| Save failed | Keep previous effective state; do not assume new acceptance. | "Your changes were not saved. Your previous settings remain in effect." |
| Signal detector error | Do not claim no signal; mark unknown. | "We could not verify your browser privacy signal." |
| Storage blocked | Choice may be session-only; necessary-only default on next load if no proof. | "Your browser may not allow us to remember this choice." |
On → Off is a first-class journey, never harder than On
| Action | Behavior |
|---|---|
| Turn category off | Persists new state, blocks future activation, stops eligible active scripts/SDKs where technically possible. |
| Reject all optional | Sets every optional category off in one action; preserves necessary-only state. |
| Reset choices | Deletes/expires the local preference receipt and re-runs the resolver — reset is never translated into acceptance. |
| Withdraw after prior accept | Shows confirmation and current effective state — no guilt or degraded core-content threat. |
Connected, not duplicative
Cookie Policy
Explains technologies, categories, purposes, vendors, and durations.
Privacy Policy
Explains personal-data processing, legal bases, sharing, transfers, and rights.
Do Not Sell or Share
Handles applicable statutory sale/share opt-out; may influence marketing/advertising state.
Consumer Rights Request
Handles access, deletion, correction, and portability workflows.
Subprocessor List
Lists processors in applicable service contexts — not every website vendor automatically belongs there.
Accessibility Statement
Explains the accessibility commitment and support route for this interface.
Common questions
Can I reject optional cookies? Yes. Where optional technologies are present, the interface provides a direct way to reject them, subject to the applicable rules for the technology and jurisdiction. | + |
Can I change my mind later? Yes — reopen Cookie Preferences from the footer and save a new choice. Withdrawal is designed to be as easy as granting consent. | + |
Why can't I turn off strictly necessary technologies? They support approved essential functions such as requested service delivery, security, authentication, routing, or storing the privacy choice itself. Each item remains inspectable. | + |
What is Global Privacy Control? GPC is a browser/device opt-out preference signal. Where applicable and supported, ZoikoSuite's resolver processes the signal according to the relevant privacy rules and shows the resulting state. | + |
Does rejecting cookies delete data already collected? Not necessarily. Rejecting/withdrawing controls future optional activation; separate privacy rights may apply to existing personal information. | + |
Why am I being asked again? A request can reappear after storage is cleared, the preference expires, the rules materially change, or a new purpose requires a fresh decision. | + |