Security & trust
What Termlane actually does.
Not what we aspire to.
This page describes the security properties of the product as shipped today. No aspirational compliance claims, no checkbox theater.
Authentication and sessions
Passwords are hashed with bcrypt. Sessions use signed tokens (Auth.js) with secrets configured for your deployment. Protected routes are enforced at the edge where applicable and again on the server for every mutation.
Organizations and data scope
Each workspace is a tenant boundary. Contracts, renewals, audit events, and billing state belong to exactly one organization. Queries for workspace data are scoped by the active organization resolved from the authenticated session.
Roles and authorization
Owner, admin, and member roles are enforced server-side on server actions and APIs. Owners manage billing and workspace identity; admins and owners operate renewals and team invites; members follow along with read-oriented access to shared data. There is no client-only enforcement for data changes.
Auditability
Structural changes and key billing events append to an audit log. The goal is straightforward operational history: who did what, on which renewal, and when.
Billing integrity (Stripe)
Checkout and the customer portal are hosted by Stripe. Webhook payloads are signature-verified before subscription state is trusted. Card numbers and payment method details stay with Stripe.
Email behavior
Operational summaries use an optional outbound provider (for example Resend) when configured by your deployment. If email is not configured, the product surfaces that clearly — nothing implies a message was delivered when it was not.
Abuse and availability posture
Public endpoints such as registration and the contact form apply lightweight rate limiting per IP to reduce automated abuse. Scheduled digests rely on an authenticated cron route with a shared secret — so delivery timing is under your operational control.
Production deployment
Run Termlane on managed infrastructure you trust, with TLS terminated correctly, database backups, and secrets stored in a vault — not in source control. We do not claim SOC 2 or ISO certification for the hosted product by default; your security review should start from this document plus your deployment architecture.
What we do not claim
Termlane does not hold SOC 2 or ISO 27001 certification for the hosted product by default. We support Google and Microsoft sign-in. We do not claim enterprise SSO (SAML federation) or SCIM provisioning unless live in your deployment. If your procurement requires certification paperwork, contact us — we will scope what is actually deliverable honestly.
Security questions?
If you are running a security review or vendor assessment, start here and send us what is missing. We will respond with what is true in the current deployment — not a marketing deck.
Ready to put renewals on the record?
Start free. No credit card required. See the queue and ledger with your own data in minutes.