Loading page
Security
How Zynapte Flow is designed to control access, protect credentials and keep an auditable record of every workflow run.
Compliance status
Security architecture
Each area shows its status. “Design” means it is part of the architecture we are building toward; nothing here should be read as a completed audit.
Role-based access so people can only build, run or approve what they should.
Protecting data in transit and at rest is an architecture requirement.
A record of who changed a workflow, who ran it and who approved what.
Credentials are kept apart from workflow definitions and masked in logs.
Workspaces are logically separated so one customer's data and configuration are not exposed to another.
Platform and execution monitoring so problems are noticed and investigated.
Connectors request the narrowest scopes they need and can be revoked at any time.
Controls larger organizations typically require.
AI and data
AI steps receive only the fields you map into them. Their inputs and outputs are recorded on the execution, and confidence thresholds and approvals keep uncertain results from acting on their own.
Responsible disclosure
If you believe you've found a security issue, contact us with details and we'll respond. A dedicated security contact and disclosure policy will be published before launch.
Contact the teamWe're happy to walk through the architecture and roadmap with your security team.