1. Isolation and access control
Data is separated by organization and product. Authorization checks run on the server, roles limit available actions, and sensitive tokens are signed, scoped, and time-limited.
2. Application protection
- input validation and error responses without sensitive details;
- rate limiting on sensitive public routes;
- explicitly allowed origins and paths for the widget and consent;
- server-side secret storage and redaction of sensitive fields in logs.
3. Data and infrastructure
Structured data is hosted in PostgreSQL on Neon and files are stored in Cloudflare R2. File access uses temporary URLs, and services communicate over encrypted connections when supported by the provider.
4. Widget and integrations
The widget separates required functionality from analytics. Analytics permissions are tied to the product, origin, and a pseudonymous identifier. Integrations use limited permissions, signatures, or OAuth where supported.
5. Operations and incidents
Dependencies, migrations, and server boundaries are checked before release. A confirmed incident is contained, investigated, and communicated to affected people or customers according to its scope and applicable obligations.
Khony does not currently claim SOC 2 or ISO 27001 certification. This page describes safeguards that are actually implemented, not an external certification.
6. Report a security issue
To report a vulnerability or ask a security question, contact privacy@khony.app. Do not include personal data, passwords, or secret keys in your first message.