Security & Compliance
Access Control
Role-based access control in Babelize: the available roles, a full permission matrix, authentication and session handling, and best practices for team access.
Babelize uses role-based access control (RBAC) to manage who can do what within your projects.
Roles
| Role | Description |
|---|---|
| Owner | Full access, billing, can delete projects |
| Admin | Project management, member invites |
| Editor | Run translations, manage content |
| Viewer | Read-only access |
Permission Matrix
| Permission | Owner | Admin | Editor | Viewer |
|---|---|---|---|---|
| View projects | ✓ | ✓ | ✓ | ✓ |
| Create projects | ✓ | ✓ | ✓ | ✗ |
| Delete projects | ✓ | ✓ | ✗ | ✗ |
| Run translations | ✓ | ✓ | ✓ | ✗ |
| Invite members | ✓ | ✓ | ✗ | ✗ |
| Remove members | ✓ | ✓ | ✗ | ✗ |
| Manage billing | ✓ | ✗ | ✗ | ✗ |
Authentication
| Method | Status |
|---|---|
| Email OTP | Available |
| GitHub OAuth | Available |
| Google OAuth | Available |
Sessions
| Property | Value |
|---|---|
| Duration | 7 days |
| Renewal | On activity |
| Cookie security | HttpOnly, Secure, SameSite |
Best Practices
- Least privilege — assign the minimum role needed
- Review access regularly — remove members who no longer need access
- Use OAuth — reduces password-related risks
Last updated: 2026-10-16
How is this guide?
Data Encryption
Babelize encrypts data in transit with TLS 1.3 and at rest with AES-256-GCM, backups included, using cloud KMS keys with automatic rotation.
Data Retention
How long Babelize keeps your data: source code is deleted after processing, translations stay while the project exists, plus account data, logs and backups.