Security & trust
Your improvement data is business-critical. We treat it that way.
Security is built into the architecture — from how tenants are isolated to how connector secrets are stored.
Tenant isolation
Every record is scoped to an organization and every query is filtered by it on the server. There is no cross-tenant data access path in the application.
Role-based access
Owner, admin, member and viewer roles. Viewers are read-only; billing, members and integrations require admin.
Encryption
All traffic uses TLS. Integration credentials (database passwords, Databricks tokens, SAS URLs) are encrypted at rest with AES-256-GCM.
Credential hygiene
Passwords are hashed with bcrypt. Session tokens and API keys are stored only as SHA-256 hashes, and sessions are revoked on password reset.
Activity history
Projects, members, billing and integration changes are recorded in an activity log with user and timestamp.
Least privilege connectors
Connectors are designed for read-only access. We recommend dedicated, read-only database users and narrowly scoped SAS tokens.
Payments
Card data is handled entirely by Stripe, a PCI DSS Level 1 service provider. We never see or store card numbers.
Secure defaults
HTTP-only, SameSite cookies, security headers, framing protection and server-side validation of every mutation.
Responsible disclosure
Found a vulnerability? Email support@yokotra.com with details. We respond within two business days and will not pursue good-faith research.
Questions from your security team?
We'll walk through architecture, data handling and our security questionnaire with your reviewers.