WAZU is provided by Agentic1 Labs, Inc., with operational support from JigSaw Labs (Pty) Ltd.
This page is a plain-language overview, not a certification or security guarantee.
Core Safeguards
- Encryption in transit using TLS
- Encryption at rest for core data stores
- Role-based and scoped access controls
- Separated production environments and managed secrets
- Logging, monitoring, patching, and incident-response procedures
- Backups and recovery controls appropriate to the service layer
AI and MCP Connector Controls
- Connector requests must be authenticated before WAZU tools run.
- WAZU resolves the permitted user, agent, personal, organisation, and cohort context for each request.
- Clients receive only the data needed for the authorised tool response.
- Write tools are separated from read tools and should return a result or receipt.
- Connections can be revoked when a user no longer wants a client to access WAZU.
Operational Access
Authorised personnel and service providers may access limited information when necessary for support, security,
legal compliance, or service operation. Access is restricted according to role and operational need.
Responsible Reporting
To report a suspected vulnerability or data-security issue, email
hello@wazu.me with enough detail for us to investigate. Do not include
unnecessary personal data, credentials, or live secrets.
More Information
See our Privacy & Data Policy for data categories, providers, retention,
international processing, and privacy rights.