Privacy disclosures you can inspect and verify.
Review approved ZoikoTax privacy, processing and data-protection disclosures, with direct routes to authoritative policies, processing terms, residency information and governed request channels.
View authoritative privacy documentsPrimary action goes to the document index on this page; it is not a legal download.
Authority notice
Plain-language summaries are navigation aids. If a summary conflicts with an approved privacy notice, DPA or other operative legal source, the approved source controls. Do not invent rights, legal bases, roles, retention periods or transfer mechanisms.
What can this page establish?
This is a dedicated public Trust route for approved privacy disclosures. Exact terms belong to legal sources. This view provides the reading structure, not replacement legal terms.
Operative approved source
Privacy notice, DPA or other operative legal source. Approval and scope must be established.
Source-grounded summary
Plain-language explanation stays within the approved source and its applicable context.
Navigation aids
Topic headings and Trust routes help you find the right source; they do not create obligations.
No approved policy details supplied in this design
The topics below are questions to verify against approved sources. They are not assertions that ZoikoTax implements these principles or particular privacy practices.
What data is in scope? Start with context.
These are content categories for source review, not an inventory of data ZoikoTax collects. Product, customer and website contexts remain distinct.
Category anatomy — inclusion and scope require an approved processing source.
A category does not establish permission to collect. No real values, sample payloads or field schemas are shown. Approved category scope, purpose and source are not supplied.
A purpose needs a source, not a generic basis.
The following are source-required content domains. They do not establish actual processing uses or legal bases.
- Approved source
- Source-defined purpose
- In-scope category
Text equivalent: an approved source establishes a purpose and identifies the categories within its scope. This conceptual linkage does not identify an actual ZoikoTax data flow.
Source must establish service scope and the categories involved.
Source requiredSource must establish any security-related purpose and its limits.
Source requiredSource must establish the support context and information in scope.
Source requiredSource must establish any actual analytics use; it is not presumed.
Source requiredSource must establish the applicable obligation and processing scope.
Source requiredController or processor? The context controls.
Controller, Processor and Customer instruction are relationship concepts to be defined by the applicable approved legal source. They are not universal ZoikoTax status labels.
Controller
The operative source must establish any controller role and the service or context to which it applies.
Approved wording requiredProcessor
The operative source must establish any processor role, including the scope of the relationship.
Approved wording requiredCustomer instruction
Any instruction relationship and DPA connection must come from the actual approved source.
Approved wording required- Service / context
- Not supplied
- Operative source
- Not supplied
- Approved role wording
- Not supplied
- Scope
- Not supplied
- Currentness
- Not supplied
Do not infer a role from product architecture.
No DPA terms, legal-approved relationship wording or universal controller / processor designation is supplied. The table is a disclosure structure, not a contract or legal advice.
Follow the lifecycle. Verify every rule.
The lifecycle is a reading map. Actual collection, processing, storage, retention, deletion and backup rules remain controlled by approved sources.
- 01 →Collection / receiptRule: Not supplied
- 02 →Use / processingRule: Not supplied
- 03 →StorageRule: Not supplied
- 04 →RetentionRule: Not supplied
- 05 →Deletion / returnRule: Not supplied
- 06Backup / archiveRule: Not supplied
Text equivalent: collection or receipt → use or processing → storage → retention → deletion or return → backup or archive. This map does not establish a sequence of actual operational practices.
Periods, exceptions and locations are source-controlled.
No retention duration, automatic deletion, restore or backup practice is established here. Legal holds and exceptions require an approved source. Storage does not establish geography; residency is a separate disclosure scope.
How should a privacy request be routed?
Use the request route identified in the applicable approved notice; a public request route is not established in supplied sources.
The applicable notice comes first.
No request form, mailbox or eligibility mechanism is provided here. A demo or sales channel is not a substitute for an approved privacy request route.
Applicable notice & eligibility
Approved notice and applicable scope: Not supplied
Destination & verification
Approved route and verification requirements: Not supplied
Supported request categories
Approved categories: Not supplied
Timing, agent & appeal
Include only where the applicable source provides them: Not supplied
Share only what an approved process requires.
Do not send identity documents, credentials, secrets, payment details, subscriber information, tax or ledger records, or sensitive request documents through a generic form. This page does not ask you to submit personal information.
Which third-party disclosure is authoritative?
A current approved source must establish identity, purpose and location. No vendor inventory, location list or subprocessor document destination is supplied.
Subprocessor source
Use a current approved disclosure for source-defined relationships. A missing or stale list must not appear current.
Approved source not suppliedCustomer-directed integrations
Keep integrations directed by a customer distinct from subprocessors. The actual relationship must be established by source.
Separate relationship scopeChange notices & access
Any change-notice process or controlled-access policy must be supported by the actual approved source.
Source requiredOwner review is required.
Before a list is presented as current, its approval, version, scope and review owner must be established. Review owner and currentness: Not supplied.
No current list shown
Privacy is not a universal hosting promise.
Data processing, residency and transfers have their own dedicated disclosure scope. A privacy summary cannot establish a location, customer choice or transfer mechanism.
Separate scope. Separate source.
Data Processing & Residency/trust/data-processing-residency/Location is not derived from product architecture. Any residency choice is context-specific, not universal.
Transfer mechanisms, support access and government lawful-request handling require governed, approved disclosures. No such terms are supplied in this view.
Independent approved source requiredUse the canonical controls disclosure.
Security owns the control summary. This page does not duplicate or invent cryptography, identity controls, certifications or security guarantees.
Security/trust/security/Actual implementation only.
Cookie policy, preferences and public tracking disclosures need an actual governed source and destination. Neither is supplied. No banner, consent mechanism, session replay or recording is presumed.
Information pending approved sourceDocuments-driven disclosure, not fabricated privacy guarantees.
Privacy topics cannot establish what tracking is deployed or what data is processed. This static view does not execute requests, consent, analytics or other website behavior.
Inspect the source. Check its standing.
This index describes the document categories needed for disclosure. It is not a published inventory of legal artifacts, current contracts or downloadable files.
Approved legal documents are not supplied in this view
No approved document titles, versions, effective dates or legal download destinations are supplied. Source-required categories are shown below without document links.
Applicable privacy terms and approved request route.
Operative processing terms, relationship and scope.
Approved identity, purpose, location and currentness.
Approved evidence access and control scope.
Source-controlled processing, residency and transfer terms.
Only an approved process can establish access and response scope.
Superseded versions must remain distinct from operative terms.
What an approved entry must show
Operative source, applicable scope, approval, version, effective date, owner, review state and access conditions. Explanatory summaries remain visibly separate.
Document metadata: Not supplied
Document states, clearly distinguished
Illustrative labels only, not assigned document statuses. Controlled access requires an approved process; no portal, NDA, response time or availability is promised.
Approval is not the same as availability.
Reviewed, updated and effective dates, version, owner and status must be taken from the source. Pending is not approved. Historical is not current.
Current public route
/trust/privacy/
The current route is not proof that a particular document is approved or operative.
- Reviewed
- Not supplied
- Updated
- Not supplied
- Effective date
- Not supplied
- Version
- Not supplied
- Review owner
- Not supplied
- Approval status
- Not supplied
Missing approval source fails closed.
An unavailable source is not replaced with generated law. Superseded versions remain historical; material-notice requirements come only from the operative source. No review date, approver or version is invented.
When a source is missing, keep the boundary.
Illustrative UI state patterns below are not reports of actual outages or a legal-document inventory. Recovery must preserve legal authority, not manufacture a substitute.
Approved source unavailable
Withhold the unsupported claim. Keep the source boundary visible.
Illustrative state patternDocument pending approval
Show a pending state, not an approved label or a document link.
Illustrative state patternRequest route unavailable
No invented fallback mailbox, form or sales substitution.
Illustrative state patternSubprocessor source stale
Require owner review. Do not present the stale list as current.
Illustrative state patternRole varies by context
Show scoped wording only; do not generalize the role.
Illustrative state patternHistorical document
Mark as historical and point to the current /trust/privacy/ route.
Illustrative state patternCore disclosure stays readable.
No-JS and print patterns retain legal boundaries and document destinations. If analytics is blocked, core content has no analytics dependency. No meaning is available only on hover or through motion.
Visible outline + label; no color-only state. This is a static visual pattern.
Direct answers. No inferred terms.
Every answer stays within the supplied sources. All answers are shown in this expanded reading state; no hidden legal content or interaction is required.
What privacy info is published?
This public route organizes approved privacy, processing and data-protection disclosures. Approved legal documents are not supplied in this view; the document index shows source-required categories, not published artifacts.
What personal data is processed?
The supplied sources do not establish the actual data inventory, scope, purposes or legal bases. Category headings are a review structure, not a claim that ZoikoTax collects every category.
Controller or processor?
The supplied sources do not establish an approved role. The applicable operative source must define the role for each service or context. Do not infer a universal role from product architecture.
How do I submit a privacy request?
Use the request route identified in the applicable approved notice. A public request route is not established in supplied sources. No request form or fallback mailbox is provided here.
Where are the DPA and subprocessors?
The document index identifies these source categories. An approved DPA, current subprocessor list and their destinations are not supplied. Evidence & Auditability is a related Trust route, not a substitute legal source.
How does privacy relate to residency?
Privacy and residency have independent source scopes. Use Data Processing & Residency at /trust/data-processing-residency/ for that scope; this privacy view does not establish hosting locations, transfer mechanisms or universal residency choices.
Take the next step toward the right source.
Start with authoritative documents and their source requirements. If an approved request route is later provided, use the route in the applicable notice. No sales gate is required to read this page.