Security
This page exists so your firm can satisfy its own vendor oversight obligation under 17 C.F.R. § 248.30(a)(2)(ii) or 16 C.F.R. § 314.4(f) without having to email us first. It is written as substantiation for the Data Processing Addendum, not as marketing, which is why the last section is the one about what we do not have.
Your own deployment
Each firm runs on its own deployment with its own database. No query can return another firm's row.
United States only
Hosted in Virginia, documents in Ohio. No subprocessor outside the United States.
Encrypted
TLS 1.2 or higher in transit. Encrypted at rest, with sensitive fields encrypted one by one.
Two-factor for everyone
Required for every user, with short-lived sessions and passwords hashed with bcrypt.
Documents locked for five years
Stored under S3 Object Lock with versioning: none can be deleted or overwritten in that time without a privileged override.
What is still in progress
SOC 2 and ISO 27001 work began on 6 October 2026. No report or certificate exists yet; the list is below.
Architecture
- Hosting
- Railway, in the United States (Virginia). Application and managed PostgreSQL with the pgvector extension. Uploaded documents are held in Amazon S3 in the United States (Ohio), with versioning and Object Lock in governance mode with a five-year retention period: a stored document cannot be deleted or overwritten during that period without a privileged override.
- In transit
- TLS 1.2 or higher for every connection, including between the application and the database.
- At rest
- Encrypted by the platform: the database at the volume level, and documents by Amazon S3. Stored credentials, meaning brokerage connection tokens, Slack and email secrets and each user’s two-factor seed, are also encrypted field by field, as are anonymous Speak up reports, their messages and anything that could identify the reporter, the MNPI register (the issuer, what was learned, from whom, and its log), reviewers’ notes on brokerage statements, and the narrative notes on code of ethics records (breaches, conflicts, gifts, outside activities, contributions), and the narrative of registration filings (Form U4, U5 and ADV items). Luna keeps only the last four digits of a brokerage account number. Other records are not; see the last section.
- Data residency
- United States only. No offshore processing, and no subprocessor outside the United States. The full list is at subprocessors.
Isolation between customers
We will describe this precisely rather than using the word “isolated” and leaving you to assume what it means.
Today, each customer runs on its own deployment with its own database. There is no shared database and therefore no query that could return another firm’s row. Uploaded documents are the one shared resource: every firm’s documents sit in the same Amazon S3 bucket, each firm in its own folder, and each firm’s deployment uses its own AWS credentials, which can reach only that folder.
We are building shared multi-tenant hosting, because a deployment per customer does not scale to self-serve signup. It will use a separate database schema per firm, with the search path bound per connection, and it will not ship without an isolation test suite that attempts cross-tenant reads and fails the build if any succeeds. When it ships, this page changes and your firm’s administrators are told directly. Your firm can also elect to remain on a dedicated deployment.
Access and accountability
- Authentication
- Multi-factor authentication is required for every user. Signed tokens with short-lived access tokens and rotating refresh tokens. Passwords are hashed with bcrypt.
- Authorization
- Role-based: employee, compliance and chief compliance officer, with per-module overrides your CCO controls. An employee sees their own code of ethics filings, trades and attestations, not anyone else’s. Outside counsel can be invited as a guest to a single SEC exam and can reach only that exam.
- Audit trail
- Every mutation is recorded with actor, action and timestamp. The log carries periodic integrity checkpoints so tampering is detectable rather than merely discouraged, and it exports for an examiner.
- Luna personnel
- Access is limited to people who need it to operate or support the Services, and is logged. We do not browse customer data.
How AI processing works
- Model provider
- Anthropic, under its commercial terms, which state that Anthropic may not train models on customer content submitted through the API. We submit under those terms, not consumer terms.
- Training
- Our model provider may not train on your data at all. Any model we train ourselves is trained only on de-identified data: data with everything that identifies your firm, your people, your clients or anyone else removed. We do not create it from archived email content or personal trading data, we do not try to re-identify it, and your firm can opt out by emailing support@lunacompliance.io. We also measure how accurate Luna’s own checks are from de-identified reviewer decisions, and the Peer Network pools de-identified, firm-level settings and exam records into benchmarks your firm can leave at any time. These are contractual commitments in Terms §4.3 and §4.6, and §11.2 means a change to §4.3 reaches an existing firm only at its renewal.
- What is sent
- The text of the document under review, and the rules and policies it is reviewed against. Questions asked in Luna’s chat, with the conversation so far and the rule and policy passages retrieved to answer them. Chat messages, to tell a trade request from a question. Counts of pending items and recent regulatory headlines, for the dashboard briefing. Where your firm uses the email archive: each message’s subject and body, with quoted history and signatures removed and Social Security, card, account and other long numbers replaced by placeholders; attachments and email addresses are not sent. An SEC exam request letter, to break it into its items. Brokerage account numbers and credentials are not sent to a model.
- Human decision
- Model output is advisory. Marketing findings go to a person at your firm with the rule cited, and no approval or denial is made on a model output. The automatic decisions are rule-based: a preclearance request for a restricted security is denied, as is one from someone on that issuer’s MNPI insider list, and one for a clearly exempt security is approved, each recorded as the system’s. One action does follow a model: if Luna’s chat reads a message as disclosing inside information, it stops helping with the trade and alerts compliance.
Incidents
We maintain a written incident response program covering detection, assessment, containment, notification and post-incident review.
We notify your firm within 72 hours of becoming aware of unauthorized access to a system holding your data. That trigger is unauthorized access to a system, not confirmed exfiltration of data, because that is where § 248.30(a)(5)(i)(B) sets it. It is in the DPA rather than only on this page.
What we do not have yet
A security page that lists only strengths is not useful to someone doing diligence. Here is the honest gap list, and we will move items off it rather than quietly rewording them.
SOC 2 report
In progress. Work toward a SOC 2 Type 2 report began on October 6, 2026. No report exists yet: a Type 2 report covers a period of operation, so it is months away. We will publish the audit firm and the period once they are set.
ISO 27001 certificate
In progress. Work toward ISO 27001 certification began on October 6, 2026. No certificate exists yet. We will publish the certification body and the dates once they are set.
Penetration test
No third-party test has been performed yet. One is part of the program that began on October 6, 2026, and should happen before shared multi-tenant hosting, not after. We will say when it is done and what it covered.
Field-level encryption of records
Stored credentials, Speak up reports, the MNPI register, statement review notes, the narrative notes on code of ethics records and the narrative of registration filings are encrypted field by field. Other records, including holdings and archived email, are encrypted at the volume level only. Because Cal. Civ. Code § 1798.150 reaches only nonencrypted data, extending field-level encryption to them is the next step.
Formal vendor questionnaire
We answer them individually today. A standard completed questionnaire is coming.
Reporting and requests
- Vulnerabilities
- security@lunacompliance.io. We will not pursue a good-faith researcher who reports privately, does not access another customer’s data, and gives us a reasonable period to fix the issue before publishing.
- Diligence requests
- legal@lunacompliance.io. We respond to a security questionnaire once per twelve-month period under a confidentiality undertaking, per DPA §8.
Luna Compliance, Inc.. This page is kept current; where it and the Data Processing Addendum disagree, the Addendum controls.