Legal & Privacy · 02

Privacy Notice

This page is where Zoiko iD’s privacy
information will be published once it has
been approved. It is a publication shell: it
shows the structure, not the legal content.

Jump to contents

Approval gate. Terms of Use must
be approved before this notice
begins. Publication is blocked until
counsel approves the text.

Privacy documents on a desk

Document control

01

Document control and
identity

Identity and policy documents

This notice describes how Zoiko iD’s
privacy information is to be presented. It is
a publication specification, not the
operative notice and not a statement of
processing activity.

Public title
Privacy Notice
Legal entity and scope
Pending Legal
Effective date
Pending Legal approval
Last updated
Shown separately, once approved
Canonical URL
Pending route registry
Version
Pending

Blocked until approved. No
effective date, entity, retention
period or contact is shown until its
governing source is supplied and
approved.

Overview

02

Plain-language overview

Whiteboard outlining a plain-language summary

A short answer to “What is this notice
about?” will appear here once Privacy
counsel has approved the wording. Until
then, no summary is shown, so that it
cannot contradict the detailed clauses.

Summary rule

The summary never overrides the
detailed clauses. If the summary is
unapproved, the section is
omitted.

Contents

03

Contents

The contents list is generated from the
approved section headings. It has stable
anchors, works without JavaScript, and
prints as a list.

  • Keyboard-operable jump list with a visible
    focus target.
  • Collapsed by default on mobile; expanded
    state is announced.
  • Browser find and Back navigation keep
    working.

Controller

04

Controller and services

Office meeting room

The entity or entities responsible for each
processing purpose, and the services in
scope, will be listed only from the reviewed
registry. Where a role is not yet confirmed,
the row is withheld rather than guessed.

Controller

Exact legal entity per purpose.

Pending Legal

Processor roles

Only confirmed processing roles.

Pending Legal

Services in scope

Website, platform and enterprise services, kept
separate.

Pending Legal

Data categories

05

Information collected and
sources

Each category will show its purpose, its
source and the context in which it is
collected. Empty categories do not produce
placeholder rows.

Account information

Categories for account holders, only if verified.

Pending Legal

Technical information

Categories only where the inventory confirms
them.

Pending Legal

Communications

Enquiries and correspondence, as approved.

Pending Legal

Purposes

06

Purposes and lawful bases

Laptop on a desk

A purpose-to-basis matrix will appear here.
No general claim of consent or legitimate
interest is made in advance; each basis
must be matched to a purpose and
jurisdiction.

Matrix rule

Each row links to its reviewed
details. Rows without approved
bases are withheld.

Recipients

07

Sharing and recipients

Recipient categories and processing roles
are shown only where verified. No
statement that information is never shared
is made unless it is independently
evidenced.

  • Recipient categories: from the disclosure
    register.
  • Contractual references: only approved
    agreements.

Transfers

08

International transfers

Countries, receiving entities and
safeguards are shown only from the legal
registry. Where a transfer detail is not
established, it is omitted and the launch is
held if the law requires it.

  • Destination

    Country or region, verified.

    Pending Legal
  • Safeguard

    Mechanism named only when approved.

    Pending Legal
  • Receiving entity

    Entity identified from the registry.

    Pending Legal

Retention

09

Retention and deletion

Retention periods and deletion criteria
appear only once approved for each
purpose. Sample numbers are never
shown as actual periods.

Deletion criteria

Stated per purpose; a policy
conflict places the item on hold.

Pending Legal

Rights

10

Your rights and choices

Rights are listed by jurisdiction and by
eligibility. Each request type has a verified
route, an identity-verification explanation
and its limits. No response time is
promised.

  • Access

    Eligibility and route pending.

    Pending Legal
  • Erasure

    Eligibility and exemptions pending.

    Pending Legal
  • Withdrawal

    Only where a basis is consent.

    Pending Legal

Cookies

11

Cookies and tracking

The Cookie Notice explains the cookies in
use. Cookie Settings is where preferences
are managed. This section links to both
and does not list cookies itself.

Cookie Notice

Separate notice.

Route pending

Cookie Settings

Preference action, shown only when live.

Action only

Safeguards

12

Security and automated
processing

Digital padlock representing security safeguards

Only approved disclosures about
safeguards, profiling and automated
decision-making appear here. Assistance
from AI is not treated as automated
decision-making by default, and no
algorithmic rights are claimed.

Safeguards: only approved descriptions.

Automated processing: only where legally
required and verified.

Updates

13

Updates and previous
versions

Effective and updated dates are shown
separately. Earlier notices are kept as
archived versions, labelled as such, and
material changes are described from the
source registry.

Archive

No archive is listed until one is
approved.

No archive available

Contact

14

Privacy contact and
complaints

Team meeting discussing privacy enquiries

Privacy enquiries, rights requests and
escalation to a supervisory authority are
routed to approved destinations. No
contact address, data protection officer or
response time is shown until verified.

Privacy enquiries

Approved route only.

Pending Legal

Rights requests

Verified route, with identity checks.

Pending Legal

Authority escalation

Per applicable jurisdiction.

Pending Legal

Gate

16

Publication gate

Publication prohibited. The page
may be built for layout and
engineering review. It may not be
published until Privacy counsel
approves the notice, the controller
and region scope is verified, and
every legally required data row is
backed by the registry.

Developer working on the page build
Data review for the registry
Team reviewing the notice before publication