SECURITY
Security at AlignLane
What protects a shared board today — and what is not available yet. We only list controls that are implemented.
Row-level security
Every workspace, relationship, board and task table is protected by Postgres row-level security. Authorization is enforced in the database, not only in the interface.
Privacy by projection
Public boards, private links and the partner view read a snapshot built from shared tasks and an allow-list of shared fields. Internal notes and estimates are stored in a separate host-only table and never enter the snapshot.
Hashed share tokens
Private links use 128 bits of random token material. Only a SHA-256 digest is stored, so a database row cannot reconstruct a link. Links can be rotated, revoked or given an expiry.
Single-use sign-in links
Email sign-in links expire after 15 minutes, work once, and are stored hashed. Sessions are revocable server-side.
Indexing controls
Boards start private. Publishing is an explicit owner action; a published board is indexable by default on a stable tokenless URL, and owners can switch search visibility off (noindex,nofollow, removed from sitemaps) or unpublish (URL returns 404, caches purged). Every change is audit-logged. Private token links are never indexed or placed in canonical tags, and are served with Referrer-Policy: no-referrer.
Rate limits
Sign-in, share-token, import and AI endpoints are rate-limited.
Transport security
HTTPS everywhere with HSTS; strict security headers and a content security policy.
Minimal import storage
Uploaded export files are parsed and discarded. Only the mapped fields you choose are stored; excluded columns are dropped.
Not yet available
AlignLane does not currently hold SOC 2, ISO 27001 or similar certifications. For security questionnaires or a DPA, contact us. Technical details: security docs.