Your raise runs on trust. So does ours.
Lunra holds the most sensitive artifact of a fundraise: the deck, the investor list, and the conversation record. This page states what we do to protect it, who touches it, where it lives, and exactly where our certifications stand. Every claim here is current, not aspirational.
Last updated 29 August 2026.
Our SOC 2 Type II observation window opens January 2027 with the report expected Q2 2027, scoped to Security and Confidentiality. We do not have a SOC 2 report today and will not claim otherwise. What we have today is the control substrate the audit will test: tenant isolation and service-role boundaries enforced in continuous integration on every change, audit logging of administrative access, and recorded authentication events. The security whitepaper below describes each control as built.
Tenant isolation
Every table holding customer data carries row-level security, so isolation is enforced by the database itself, not by application code remembering to filter. An automated isolation suite of more than 80 assertions runs against the live security policies on every code change, and a second control verifies that privileged database access appears only in server code that is on a reviewed allowlist.
Access and authentication
Sign-in is by emailed magic link, so there is no stored credential to steal. Workspace membership and roles are granted server-side only. Authentication events are recorded, and administrative actions are audit-logged, including any cross-tenant read by our own staff.
Encryption
All traffic is encrypted in transit with TLS. Data at rest is encrypted with AES-256 on our database and storage infrastructure (Supabase on AWS). Application secrets live in the hosting platform’s environment configuration, never in code.
Deck and document handling
Exactly one AI vendor ever sees customer deck content: Anthropic, whose commercial terms state that content submitted through the API is not used to train models. Adding a second deck-touching vendor is treated as a security boundary change requiring documented review, not a feature decision.
Shared document controls
Documents shared with investors are served through a single controlled route: watermarked, verified as genuine PDFs at the byte level, behind links that expire after 30 days and can be revoked at any time, with optional NDA acceptance gating and a per-view access log your team can see.
Storage region
Customer data is stored and processed in the United States. The primary database and file storage run on AWS in us-east-2 (Ohio) via Supabase; application hosting is on Vercel in the United States.
Subprocessors
These providers process customer data on our instructions only. We do not sell customer data and we do not share it for advertising.
| Provider | Purpose | Data involved | Location |
|---|---|---|---|
| Supabase | Database, authentication, file storage | All customer and workspace data, uploaded documents | United States (AWS us-east-2) |
| Vercel | Application hosting and delivery | Data in transit through the application | United States |
| Anthropic | AI analysis and drafting | Deck content and text submitted to AI features | United States |
| Resend | Email delivery | Recipient addresses, message content | United States |
| Stripe | Billing and payments | Billing contact and subscription status | United States |
| Google Workspace | Company mailboxes for support and operations | Email you send us | United States |
Separately, our investor directory is built from public and licensed sources (SEC EDGAR, Hunter, People Data Labs, Instantly, TwitterAPI.io). Those vendors supply directory data; they do not receive customer deck content or workspace data. How the directory is built and governed, including how an investor can be removed from it, is documented in how Lunra handles investor information.
Data handling and retention
What you upload stays yours, and you do not need to ask us for it: workspace owners can export the entire workspace (every table, plus a signed-link manifest of all stored documents) from Settings at any time, and can permanently delete the workspace the same way. Deletion is a hard delete of every workspace table and stored file, driven by a registry that is checked against the live schema in continuous integration, so a new table cannot silently escape it. We keep only a minimal deletion receipt and what financial record-keeping law requires.
Shared documents keep their history on purpose. When you replace a document with a new version, the superseded file is retained rather than deleted, because it is the record of what an investor actually saw at the time, and the access log points at it. A share link never silently changes what it resolves to.
To exercise a data request, export, correction, or deletion, write to privacy@lunra.io. Investors in our directory can use the no-account request form, applied immediately and without a review step.
Report a security issue
If you believe you have found a vulnerability in Lunra, email hello@lunra.io with “Security” in the subject line and enough detail to reproduce it. Reports go straight to the founding team and we will respond as quickly as we are able. We ask that you give us a reasonable opportunity to fix an issue before disclosing it publicly, and we will not pursue good-faith research conducted within these terms. A machine-readable contact is published at /.well-known/security.txt.
Architecture, tenant isolation, encryption, deck handling and retention, and SOC 2 status in full.