Security & Trust
Security posture, certifications, data handling, and vulnerability disclosure for Pteri-Auth.
Pteri-Auth secures authentication for users, devices, and AI agents. We hold ourselves to the standard we ask of our customers.
This page sets out our security posture, how we handle data, and how to reach us. For the underlying commitments, see our Privacy Policy, Terms of Service, and Service Level Agreement.
On this page
Certifications and compliance
| Standard | Status |
|---|---|
| SOC 2 Type II | Planned. KAKR Labs has not yet completed an independent audit. |
| SOC 2 Type I | Not currently pursued |
| ISO 27001 | Not currently pursued |
| GDPR | A legal requirement rather than a certification. A Data Processing Agreement is available on request. |
| EU AI Act, Article 12 | A record-keeping duty for providers of high-risk AI systems, not for KAKR. PTERI’s audit logging can help customers meet it. |
| HIPAA | Not applicable to our current services |
| PCI DSS | Not applicable. We don’t process cardholder data; Marketplace billing is handled by Google. |
We state certification status honestly and will update this page as audits are completed. Questions about our security programme: security@kakr.ai.
How we handle data
What we process. Authentication events only. Identity references, public keys, challenge and signature verification records, timestamps, event outcomes, and policy metadata.
What we never see. The content of authenticated actions. Message bodies. Transaction details. Any application data belonging to our customers.
Private keys. KAKR does not hold or store customers’ private keys. Keys stay with whoever controls the identity: the user’s device, the customer’s application, or the agent or workload. Only the matching public address is registered with PTERI. If an integration uses our SignMessage endpoint, the key is sent over an encrypted connection only to create the signature and is not stored.
AI training. Customer authentication data is never used to train artificial intelligence or machine learning models, and never sold.
Where data lives. The Pteri-Auth API runs on Google Cloud in the United States (us-central1, Iowa). Customer data is currently hosted in the United States.
Retention and deletion. Set out in our Privacy Policy and Terms of Service.
Infrastructure and controls
- Hosted on Google Cloud Platform in the United States (us-central1, Iowa)
- Encryption in transit using TLS 1.2 and 1.3 and at rest using AES-256
- Access controls and role-based permissions
- Multi-factor authentication for internal systems
- Logging and monitoring of access to production systems
- Secure development practices, including code review and dependency scanning
- Documented incident response procedures
Subprocessors
We publish a complete list of subprocessors with access to customer data.
Our current list is published in section 5 of our Privacy Policy.
We give customers reasonable advance notice before adding a new subprocessor.
Reporting a vulnerability
We welcome reports from security researchers.
Contact: security@kakr.ai
Please include enough detail for us to reproduce the issue. We will acknowledge your report, assess its severity, keep you informed of our progress, and tell you when the issue is resolved.
Safe harbour. We will not pursue legal action against researchers who report vulnerabilities in good faith, avoid privacy violations and service degradation, do not access or modify data belonging to others, and give us reasonable time to remediate before public disclosure.
Documents
| Document | Location |
|---|---|
| Privacy Policy | kakr.ai/privacy-policy |
| Terms of Service | kakr.ai/terms-of-service |
| Service Level Agreement | kakr.ai/sla |
| Data Processing Agreement | On request — see Data processing |
| Subprocessor list | Privacy Policy, section 5 |
| System status | kakrlabs1.statuspage.io |
Available under NDA: security architecture documentation, completed security questionnaires, and our SOC 2 report on completion. Request from security@kakr.ai.
Verify it yourself
Eight interactive demonstrations run real attacks against real cryptographic verification, in your browser, with no signup and no installation.
Recommended for security teams: MFA Attack Simulation and Your Number Is Not You. Combined review time is approximately twelve minutes.
Contact
| Purpose | Contact |
|---|---|
| Security enquiries and vulnerability reports | security@kakr.ai |
| Privacy and data protection | privacy@kakr.ai |
| Technical support | support.kakr.ai |
| Enterprise, carrier, and partnership enquiries | hello@kakr.ai |
Last updated: 8 October 2026