Pamplemousse
Request an invite →
A stained-glass greenhouse of iron arches and potted grapefruit trees, ripe fruit hanging in the foreground
Principles · Security

Trust requires specifics.

Security is not a mood, a lock icon, or a claim that a product is “safe.” It is a continuing practice. The board to the right is our running list of security measures, kept current as each one ships.

Status boardPrivate beta
Invite-only, operator-reviewed accountsIn place
Server-side session validationIn place
Rate limiting · invite formIn place
Rate limiting · sign-inIn place
Multifactor authenticationIn place
Cross-workspace isolation testingIn place
Independent audit or pen testNot claimed

How we protect your account.

Four practices · Open one

Accounts are reviewed and created through an operator-managed process rather than open registration. Authenticated areas require a session; administrative actions are checked again on the server, and system-administrator access is separate from workspace roles.

Private beta reduces casual exposure. It does not, by itself, make the application secure.

Invitation is an access policy, not a security certification.