Security

Please include:

• what the problem is and where (URL, API route or MCP tool);
• step-by-step instructions to reproduce it, using only accounts and workspaces you own;
• what an attacker could do with it; and
• how we can contact you, and whether you would like to be credited.

We aim to acknowledge reports within 3 business days and to keep you updated until the issue is fixed. Please give us a reasonable time to fix a problem — normally 90 days — before you share details publicly. We do not currently run a paid bug bounty.

In scope: planra.co and the web app, the REST API, the MCP endpoint (/api/mcp), and the public pages Planra hosts (forms, signing links, client portals, share links and published docs).

Out of scope:

• services run by other companies, such as Clerk, Supabase, Vercel, Google or Resend — report those to them;
• denial-of-service, load testing, spam, and social engineering of our staff or users;
• reports from automated scanners with no demonstrated impact;
• problems that need physical access to a device, or a device that is already compromised.

If you act in good faith and follow these rules, we will not pursue or support legal action against you for your research:

• test only against accounts and workspaces you own or have permission to test;
• do not access, change, download or keep other people's data — if you reach it by accident, stop, do not share it, and tell us;
• do not disrupt the service or degrade it for others;
• do not use a vulnerability for longer than needed to show it exists; and
• keep the details confidential until we have fixed the problem or agreed otherwise.

• Sign-in is handled by Clerk; we never see or store your password.
• Workspace isolation: every request is checked against your active membership of the workspace, and viewers have read-only access.
• Encryption: all traffic uses HTTPS, and data is encrypted at rest by our database and storage provider. AI provider keys and some integration tokens are additionally encrypted by Planra; API keys are stored only as hashes.
• Agent controls: agents have trust levels, budgets and approval gates, and every agent action is recorded in a provenance timeline that owners can export.
• Audit log of significant actions, kept for 365 days.
• Abuse protection: rate limits on API routes and public pages, and an allowlist sanitiser for content shown on public pages.
• Reviews: we review the code for security problems and fix what we find.

We do not currently hold SOC 2 or ISO 27001 certification. For details of the providers we use, see Subprocessors; for how we handle personal data, see the Privacy Policy.