Architecture, not attestation
How Pensiro separates one workspace's data from another.
Workspace data sits behind Postgres row-level security keyed to workspace membership, checked in the database rather than in the browser.
Workspace isolation.
A request for a row in a workspace you are not a member of returns nothing, and that check runs in the database rather than in the browser, so it applies to any client holding your credentials.
This describes how the system is built. Pensiro has not had an independent penetration test, and this page is not a promise that no attack will succeed.
Locked administrative paths.
Administrative database functions follow one fixed pattern:
- A pinned search path
- Execution revoked from the public role and granted only to signed-in users
- A membership check as the function's first statement
This covers the functions Pensiro defines in its own schema.
Attachments.
Files live in a private storage bucket, readable only by members of the workspace they belong to. A workspace admin can delete any attachment; a member can delete the ones they uploaded themselves.
Integration credentials.
Pensiro holds no OAuth token for your GitHub or Slack account. The one credential Pensiro does store is the shared secret that verifies an incoming GitHub webhook really came from GitHub. It sits in a separate table no application user can read, and a new one can be generated from Settings, Integrations, which retires the old one.
Account export and deletion.
Account export and account deletion are self-service from Settings, Account. Export contains your own records plus the full contents of any workspace you own; for a workspace you belong to without owning, only your own rows are included.
Pensiro refuses to delete an account while that person is the sole owner of a workspace that still has other members, and asks them to hand ownership over first; a workspace is deleted along with the account only when the account is its only member.
Uploaded files are not removed by account deletion yet; email privacy@pensiro.com if you need attachments erased. The full account is in the privacy policy.
An honest note.
Pensiro does not claim a third-party security certification. No independent security audit or penetration test has been performed. This page is a description of the architecture, not an attestation, a certification, or a service-level commitment.
Report a security problem: security@pensiro.com. We aim to acknowledge within 3 business days.
Common questions.
Can one workspace see another workspace's data?
Workspace data is separated by row-level security in the database, keyed to membership, so a request from an account that is not a member returns no rows. Pensiro has not been independently tested, so we describe how it is built rather than promise an outcome.
Who can delete an attachment?
A workspace admin can delete any attachment; a member can delete the ones they uploaded themselves.
Does Pensiro store my GitHub or Slack credentials?
No OAuth token for your account. Pensiro does store the shared secret that verifies incoming GitHub webhooks, in a table no application user can read.
Can I export my data?
Yes, from Settings, Account. The export covers your own records plus the full contents of any workspace you own; for workspaces you belong to without owning, only your own rows are included.
Is Pensiro SOC 2 or ISO certified?
Not at this time. This page describes real architecture, not a certification claim.
Client words in, dev-ready structure out.
Request early access See pricing
Signups open at launch. Early access reaches the team directly. You can also email support@pensiro.com.