Skip to content

Security at Plotlane

Last updated October 21, 2026

How we protect the projects, files and conversations you keep in Plotlane.

Overview

Plotlane holds your project plans, tasks, files and conversations, so we build every feature with access control first. This page describes the safeguards that are in place today. It is not a promise of certifications we don't have: Plotlane is not currently SOC 2 or ISO 27001 certified.

Encryption

  • In transit: all traffic to plotlane.rinmac.com is served over HTTPS (TLS). Live updates use the same encrypted connection.
  • At rest: data lives in a managed PostgreSQL database and private object storage on our hosting provider's infrastructure; neither stores files or rows in a publicly readable location.
  • Passwords are never stored in plain text. They are hashed with bcrypt (cost factor 12) and cannot be read back, even by us.

Access control

Every request is checked on the server against your role before any data is returned or changed.

  • Workspace roles — Owner, Admin, Editor, Commenter and Viewer — decide who can change structure, edit rows, comment or only read.
  • Sheet sharing lets you give a person access to a single sheet without opening the rest of the workspace. Organization admins can turn sharing outside the workspace off entirely.
  • Files attached to rows are kept in private storage and are never publicly addressable. Downloads pass through Plotlane, which checks that you can view the sheet first.
  • Dashboards and reports are computed per viewer, so a chart never reveals rows from a sheet you can't open.
  • Forms only add rows; people filling one in can't see the sheet behind it.

Authentication

  • Two-step verification: anyone can require a 6-digit code from an authenticator app (Google Authenticator, Microsoft Authenticator, 1Password, Authy and others) at sign-in, with one-time recovery codes as a backup. Authenticator keys are encrypted at rest, recovery codes are stored only as hashes, each code works once, and repeated wrong codes are locked out.
  • Password reset links are single-use, expire after an hour, and never reveal whether an account exists.
  • Sign-in sessions are held in signed, HTTP-only cookies that page scripts cannot read.
  • Single sign-on with Microsoft Entra ID or Google can be turned on for your organization, so people sign in with their company account.
  • Administrators can disable an account immediately; a disabled person is signed out of Plotlane on their next request.
  • Sign-up, form submissions, uploads, imports and comments are rate-limited to slow down automated abuse.

Application security

  • All input is validated on the server against strict schemas before it reaches the database.
  • Database queries are parameterized, which prevents SQL injection.
  • Browsers are told not to frame Plotlane (clickjacking protection), not to guess file types, and to send minimal referrer information. Camera, microphone and location access are switched off.
  • Uploaded files are limited to 25 MB each. Only safe types such as images and PDFs can preview in the browser; everything else is served as a download, never run in the page.
  • AI suggestions can't change data on their own: every proposed edit is validated against the column and applied only when a person with edit rights clicks Apply. Sheet content is treated as data, not instructions.
  • Google Sheets imports only ever contact Google's servers, so a pasted link can't be used to reach internal systems.
  • Concurrent edits are version-checked, so one person can't silently overwrite another's change.

Audit trail

Changes to rows, columns, sharing and settings are written to an audit log with who made the change, when, and the value before and after. Each row's activity is visible to people with access to the sheet, and system administrators can search the full audit log from the admin console.

Infrastructure

Plotlane runs on Railway, a managed cloud platform, in the United States. The application, its PostgreSQL database and file storage are hosted there; email notifications are delivered through Resend; the optional AI assistant is powered by Anthropic's Claude API, which receives only the sheet a person asks it to review. Production credentials are kept as encrypted environment variables and are never stored in source code.

The database is managed by our hosting provider. We are working toward documented backup and restore testing; until then, we recommend exporting critical sheets to Excel or CSV, which every editor can do at any time.

What you can do

  • Use a long, unique password, or ask your administrator to turn on single sign-on.
  • Give people the lowest role they need — Viewer or Commenter is often enough.
  • Review sheet shares and workspace members when someone leaves a project.
  • Don't put passwords, payment card numbers or health records in sheets.

Reporting a vulnerability

If you believe you've found a security issue, email security@plotlane.rinmac.com with the steps to reproduce it. We'll acknowledge your report within three business days and keep you updated while we fix it.

Please give us reasonable time to fix the issue before you share it publicly, and don't access other people's data, degrade the service or run automated scans against it. We won't pursue legal action against good-faith research that follows these guidelines.