Contact the
Zoiko iD security
team.
Use this page to find the appropriate Zoiko iD security route for an enterprise enquiry, potential security concern or trust-related question. Suspected vulnerabilities use Responsible Disclosure; service condition is reported through Availability / Status. Contact methods and response processes appear only when confirmed by Zoiko iD security operations.
Route and ownership, not a live dashboard
Monitored components
Timestamps shown
Support routes
Planned maintenance
Do not send passwords, tokens, private keys, personal records or exploit payloads through ordinary contact fields.
This page is not an emergency line. For an active incident affecting your operations, use the routes below and follow your own escalation process.
Passwords
API keys and tokens
Private keys
Exploit code or payloadsSix intents, each with its own owner
Select the intent that matches your question. Each one leads to the team that owns that work, so your request
reaches the right place.
Ask a security question
General security or architecture questions from an enterprise.
Report a product vulnerability
A suspected flaw in a Zoiko iD product or integration.
Report suspected account
You believe a credential, token or account may be misused.
Find a security advisory
You are looking for a published notice about a security issue.
Report a service availability issue
A service appears to be unavailable or degraded.
Ask about privacy or data
Questions about personal data or data-rights requests.
One entry point,
six destinations
This page does not hold your case. It sends you to the owner.
Each spoke below is a separate system with its own rules and
records.
Vulnerabilities
Advisories
Status
Trust Center
Privacy
Support
Gather these details first
Having the right information ready helps the owning team respond. None of it should include secrets.
Which Zoiko iD product or integration is involved.
When you first noticed the issue, in your own timezone.
What you observed, described in your own words.
Whether you have already taken protective steps.The form is shown only when it islive
No form is rendered on this layout. The fields below describe what the approved intake will ask, so you can prepare.
Each field carries a validation rule and a disclosure limit.
Where each route goes, and who owns it
These destinations are separate on purpose. Each owns its own work, so a question about one is never handled asif it were another.
Responsible Disclosure
Suspected product vulnerabilities and coordinated researcher reporting.
Security Advisories
Published security notices, remediation and disclosure history.
Availability / Status
Service health, maintenance and incident status.
Trust Center
Security, privacy and assurance evidence, with restricted access.
Privacy
Privacy architecture, data rights and approved privacy enquiries.
Sales and Support
Commercial enquiries and standard account support, without sensitive incident data.
Every state has a clear next step
Submitting
The form stays filled. The button is busy andcannot be pressed twice.
Outcome unknown
Do not resubmit. Check the status of your earlierrequest first.
Attachment rejected
Other fields are kept. The reason is shown in plainlanguage.
Service unavailable
A readable fallback explains what to do. Nosupport address is invented.
Permission denied
Sensitive context is removed. A generic routeremains.
Rate limited
A neutral message appears with retry guidancefrom the service.
Receiving a request is not the same asresolving it
A receipt confirms that a request was created. It does not confirm triage, action or resolution, and no response timeis promised.
Submitted
Request sent once.
Received
Reference shown only if returned.
Triaged
Owner reviews the request.
In progress
Work is under way.
Resolved
Outcome recorded by the owner.
Security evidence
goes through the
Trust Center
Enterprise reviewers can find controls and request approved
evidence through the Trust Center. Access is authorized, and no
document is downloadable by default.
Review the public security and privacy information.
Request a specific, approved document.
Access is granted only after review.
What this page does and does notpromise
Routes are verified
Each destination is checked before it appears.Unverified routes are shown as pending, never aslinks.
No severity claims here
This page does not decide how serious an issueis. The owning team classifies it after review.
Minimal data collected
Only what the owning team needs. Analyticsrecord categories, never your message or youridentity.
Frequently asked questions
Start with the route that
matches your question.
Vulnerabilities go to Responsible Disclosure. Advisories,
service condition and evidence each have their own page.
Enterprise discussion follows once your question is routed.
Trust Center
Responsible Disclosure
Security Advisories