Privacy Manifesto
The privacy principles behind RebelOps.
This page explains the privacy ideas that shape RebelOps. It is meant to explain our design direction in plain language. For the legal details, use the Privacy Policy and Terms.
True End-to-End Encryption
Organizations can enable end-to-end encryption for supported data. When it is enabled, the encryption key does not live on RebelOps servers unless you deliberately share it. That means we cannot access encrypted data.
What this means in practice: Organization settings show what is encrypted, and organization directors can rotate encryption keys if they suspect compromise.
Isolated Organization Containers
Unlike many tools that keep everyone in a shared environment, each RebelOps organization runs in its own isolated environment with dedicated:
- Database instance
- File storage
- Credentials and authentication
- Processing environment
Why this matters: Isolation helps reduce cross-organization exposure. If one organization has a problem, that design reduces the chance that the same problem also exposes everyone else.
Anonymous-by-Design Architecture
Our main server is designed not to keep normal operating links between users and organizations. When you create or join an organization, you decide whether to save a convenience link back to it for easier device hand-offs.
How it works: Memberships live inside the organization's own environment. The main server can keep an optional bookmark for convenience, but that is separate from the organization's real operating data.
Truly Anonymous Accounts
RebelOps accounts do not require a valid email address. In practice, the email field works more like a username that happens to use email format, so it can be fictional.
What this means: Identifiers such as anonymous@privacy.local or rebel@nowhere.void can work as login names. They are not treated as guaranteed contact information.
Privacy-First AI
Organizations decide what data AI features can access and which AI provider is used. RebelOps is designed to let organizations choose the provider and control the data flow as much as the product allows.
Important: AI privacy depends in part on the provider your organization chooses. If you use self-hosted or private AI infrastructure, RebelOps is designed to support that direction over time. See Trooper.AI for one example of a private AI option.
The RebelOps Difference
Many project tools were designed around convenience first. RebelOps is trying to take privacy more seriously at the architecture level, even when that makes implementation harder.
Traditional PM Tools
- Shared databases
- Server-side encryption keys
- Cross-organization data visibility
- Required email verification
- Centralized user tracking
RebelOps
- Isolated containers
- Client-side encryption keys
- Zero cross-organization access
- Anonymous accounts supported
- Decentralized privacy architecture