CUEBES offers four privacy tiers for your repositories, from fully public to zero-knowledge encryption. Choose the right level for your project's needs.
Privacy Tiers Explained
Public
Best for: Open source projects, portfolios, learning resources
- Anyone can view your code
- Anyone can clone your repository
- Only you (and collaborators) can push changes
- Appears in public searches and your profile
Private
Best for: Personal projects, work in progress, team projects
- Only you and invited collaborators can view
- Does not appear in searches
- Requires authentication to clone or pull
- Standard access control without encryption
Encrypted Private
Best for: Sensitive code, compliance requirements, client work
- All the benefits of Private
- Server-side AES-256-GCM encryption at rest
- Your code is encrypted in our database
- Full Git client compatibility (Xcode, VS Code, etc.)
- Transparent to users - works like any Git repo
How it works: Encrypted Private uses envelope encryption. Each repository has its own encryption key (DEK), which is itself encrypted with a platform key. Your code is automatically encrypted when stored and decrypted when you access it.
End-to-End Encrypted (E2EE)
Best for: Maximum security, zero-trust requirements
- Client-side encryption - we never see your code
- You hold the encryption keys
- Only accessible via CUEBES web interface
- Cannot use external Git clients
Important: E2EE repositories cannot be cloned with Git clients like Xcode or VS Code. Use Encrypted Private if you need IDE integration with encryption.
Comparison Table
| Feature | Public | Private | Encrypted Private | E2EE |
|---|---|---|---|---|
| Access Control | Open | Yes | Yes | Yes |
| Encryption at Rest | No | No | Yes (Server) | Yes (Client) |
| Git Client Support | Yes | Yes | Yes | No |
| IDE Support | Yes | Yes | Yes | No |
| Zero Knowledge | No | No | No | Yes |
Changing Privacy Settings
You can change your repository's privacy level at any time:
- Go to your Codicle
- Click "Settings"
- Under "Privacy", select your new level
- Click "Save Changes"
Note: Changing to E2EE will require re-encrypting all content and will disable Git client access. This action cannot be undone without recreating the repository.