Security & privacy
Rodeo is built so people only ever see what they should — from workspace isolation down to a single shared page. Here's how it works.
Every request is scoped to your workspace at the data layer. There's no path for one workspace to read or touch another's data — object IDs are always checked against your membership.
Private spaces are members-only, everywhere. A workspace member who isn't in a private space can't reach its pages through search, references, databases, comments, or the API.
Guests are shared into specific pages only. They can't see the rest of the workspace, and removing a guest instantly revokes their access.
The API is secure-by-default: every endpoint requires a valid signed token unless it's explicitly public (like login). No endpoint ships open by omission.
All traffic runs over HTTPS/TLS. Uploads and API calls are always encrypted between your browser and our servers.
Short-lived access tokens with rotating, single-use refresh tokens keep you signed in safely — and sign-out revokes access everywhere.
You're a member of a workspace, or you're not. Non-members get nothing — not even the existence of a page.
Owners and admins manage the workspace; members collaborate; guests are limited to what's shared with them.
Inside a workspace, private spaces are visible only to their members — enforced on every read and write path, not just the sidebar.
Individual pages can be shared with specific guests at view, comment, or edit level — and revoked at any time.
Private where it needs to be. Shared where it should be. Fast everywhere.