Trust & safety
Security at Orgero
Your workforce data is sensitive. We treat security as a first-class concern — not an afterthought.
Encryption everywhere
- TLS 1.3 for all data in transit
- AES-256 encryption for data at rest
- Secrets stored in environment variables, never in source code
- Stripe handles all payment data — we never touch card numbers
Authentication & access
- Session tokens are cryptographically signed (HMAC-SHA256)
- Role-based access control (RBAC) at every API endpoint
- Per-branch and per-workspace permission scopes
- Admin tools are restricted to admin and HR roles
Infrastructure
- Self-hosting option: your data stays on your own servers
- Managed cloud runs on hardened Linux instances
- Automated daily backups with point-in-time recovery
- Database and API servers are network-isolated
Monitoring & audit
- Structured server logs with retention for 90 days
- Failed login attempts are rate-limited and logged
- Activity feed tracks who changed what and when
- Diagnostics dashboard surfaces anomalies in real time
Updates & patching
- Dependencies are reviewed and updated on every release
- Security advisories are triaged within 24 hours
- Zero-downtime deployments via rolling updates
- Changelogs published for every production release
Responsible disclosure
If you discover a security vulnerability in Orgero, please report it responsibly to security@orgero.com. We commit to acknowledging your report within 48 hours, keeping you informed as we investigate, and publicly crediting you once the issue is resolved (if you wish). Please do not publicly disclose the vulnerability before we have had a chance to address it.