Tenant isolation in the database
Every query runs inside a session-pinned transaction enforced by PostgreSQL Row-Level Security, so the workspace boundary lives in the database — an application bug cannot read across tenants because the database itself refuses. The policy SQL is shared on request.
Source: SecurityImmutable audit log
Every privileged action is captured in an immutable, hash-chained audit log recording actor, IP, target, and a before/after diff. It is streamable to your SIEM so you keep an independent record of what happened in your workspace.
Source: SecurityEncryption everywhere
Traffic is encrypted in transit with TLS (HSTS preload), and data is encrypted at rest by our database and storage providers. On top of that, the application encrypts OAuth tokens, integration secrets and stored API keys before they are written to the database; other columns are not field-level encrypted.
Source: SecuritySigned webhooks
Outbound webhooks for issue, project, and cycle events are signed so receivers can verify each request is authentic, with automatic retries and at-least-once delivery. Build integrations that trust the payload they receive.
Source: Developer webhooksSSO, SAML & SCIM
SAML 2.0 single sign-on plus SCIM 2.0 provisioning map your identity-provider directory groups straight to workspace roles, with automated deprovision on termination. Available on Enterprise.
Source: SecurityWhere your data is hosted
Planoda runs as a single shared deployment hosted in the United States (application on Vercel, file storage on Backblaze B2, both US East). We do not currently offer a choice of data region. Dedicated infrastructure or a specific hosting region can be scoped as part of an Enterprise agreement; talk to us.
Source: SecurityGDPR & DPA
A Data Processing Agreement is offered to every paid customer, with Standard Contractual Clauses for transfers outside the EEA and UK. Workspaces are deleted by our team on a verified owner request, not automatically: we then delete the workspace's data from our database and file storage within 30 days. Copies in the database provider's point-in-time recovery history and in our nightly encrypted off-site backups can remain for up to 30 days after that deletion (see the Privacy Policy).
Source: Data Processing AgreementSOC 2: not certified yet
Not SOC 2 certified yet. We follow the SOC 2 security criteria as our internal baseline and will publish the report when an audit is complete.
Source: SecurityIncident response & disclosure
Report vulnerabilities to security@planoda.com (also published in our security.txt). We do not publish a PGP key or a fixed disclosure deadline yet; a coordinated disclosure program with recognition for verified findings, and third-party penetration testing, are planned.
Source: SecuritySub-processors & legal terms
Our infrastructure sub-processors (database, object storage, AI gateway, email, payments) are disclosed in the legal center alongside the Terms of Service, Privacy Policy, and security overview, so you know exactly who processes your data.
Source: Legal center