Data flow
In the intended design, context is read from connected systems, normalized into a relationship model, analyzed, and presented for review. Proposed changes leave the platform only after explicit approval, and are followed by reassessment.
Security & trust
Clear boundaries, understandable decisions, human control.
This page separates what exists today from what is planned. Zarketo does not currently hold any security certifications or independent audit reports, and does not claim to.
Architecture overview
The conceptual architecture places human review between analysis and action. Every approved change is followed by a reassessment of the relationships it was meant to break.
Access boundaries
Integrations are intended to use read-only, least-privilege credentials scoped to the context an investigation requires. Write access, where it ever exists, would be separate, narrowly scoped and opt-in.
Human approval
Sensitive remediation is designed to be presented as a proposal. The owner of the affected resource decides whether to apply it. Nothing on this marketing website can change infrastructure.
Auditability
The product direction includes recording reviews, approvals, actions and reassessment outcomes so that decisions can be reconstructed later. Specific retention and export capabilities will be documented when implemented.
Data handling
The principle is to collect the minimum context needed for analysis. Detailed policies on storage location, retention and deletion will be published alongside product availability.
- 01Data Sources
- 02Context and Relationships
- 03Investigation and Risk Analysis
- 04Human Review
- 05Approved Action
- 06Reassessment
Implemented vs. planned controls
| Area | Control | Status |
|---|---|---|
| Website | Demo requests validated server-side and stored with restricted access | Implemented |
| Website | Spam protection on demo form (honeypot and timing check) | Implemented |
| Website | No third-party analytics or tracking cookies | Implemented |
| Website | Interactive explorer runs entirely in the browser with simulated data | Implemented |
| Platform | Least-privilege, read-only integration credentials | Planned |
| Platform | Approval gates before any remediation action | Planned |
| Platform | Audit trail of reviews and actions | Planned |
| Platform | Published data handling and retention policy | Planned |
Vulnerability disclosure
A dedicated disclosure channel is not yet configured. Until it is, please report suspected vulnerabilities in this website through the contact page, marking your message as a security report. Please do not include exploit details until we confirm a secure channel.
Security documentation
Architecture, data handling and access documentation will be published with product availability. Teams evaluating Zarketo can request the current design notes through a demo request.