Security

Security by structure,
not by promise.

Our engineers work inside your companies’ systems, so security is built into how the work is done. Each company’s data is kept apart, access is enforced in code, every action is recorded and deletion is certified.

Principles

Six rules hold for every company we work with, and our software enforces them.

  • Kept apart by company.

    Each company’s data lives in its own encrypted volume with its own key. Our tools refuse any command that would reach another company’s data.

  • Read-only by default.

    Our connectors to your finance systems are built to read only, over HTTPS connections that verify the server they reach. Nothing in them writes to your records.

  • Software drafts, people send.

    What we build prepares the work, such as collection emails. Your team reviews it and decides what goes out. Our software cannot send email.

  • Every action on the record.

    A tamper-evident log records who did what, when and for which company, with signed checkpoints. It records actions, never your data values.

  • Credentials never in the clear.

    Passwords and keys for your systems stay in the operating system’s secure keychain, never in files, logs or error messages.

  • Deletion you can verify.

    When we leave, we erase your data by destroying its keys, as NIST SP 800-88 describes, and give you a signed deletion certificate confirmed by a second person.

Siloed by company.
Aggregated for the fund.

Portfolio companies can compete, and each has its own customers, contracts and regulators. Antitrust, securities and privacy law all limit what may move between them, so our fund model is built to those limits.

One silo per company.
Each company’s records stay in its own encrypted store, and figures for the fund are computed inside it. We never combine personal data from different companies.
Only company-level figures go up.
The fund model receives financials, KPIs and covenant figures. Personal data, customer names, contract terms, and health, card and export-controlled data never leave the company.
No pooling across competitors.
A view across companies needs at least five contributors, none above a quarter of the total, and never names or ranks them. Competitively sensitive figures appear only after a time lag, and companies never see one another’s data.
Each company agrees first.
A data-sharing agreement with each company, checked against its customer contracts and approved by its board, sets what reaches the fund and why.
Walls around inside information.
Companies with public debt, or held alongside credit strategies, are tagged. Their figures sit behind your information barriers, and every read is logged.
Projections labeled as projections.
Projected IRR and MOIC carry their assumptions with them, ready for the SEC’s rules on hypothetical performance.
Clean at exit.
When a company is sold, its data and its history in the fund model can be exported, then deleted with a signed certificate.

Security for each industry

Every industry we work in has its own rules. We sign the terms they require before regulated data reaches us, keep what we don’t need out of reach, and never connect agents to control systems.

Technology, Media & Telecom Customer DPAs · CPNI · COPPA
Your customers’ contracts travel with us. We sign your data processing terms, give 30 days’ notice before adding a subprocessor, and keep telecom customer records and children’s data out of scope unless the agreement covers them.
Healthcare & Life Sciences HIPAA · 42 CFR Part 2 · 21 CFR Part 11
We sign a business associate agreement, with Part 2 terms where needed, before touching health information, and hold our providers to the same terms. Data is de-identified to HIPAA’s standard before any analysis that doesn’t need identities.
Industrials & Manufacturing ITAR · EAR · DFARS 7012 · CMMC
Export-controlled and defense information stays out of our systems unless an engagement is set up for it: US persons only, in US government cloud regions. Agents never connect to plant-floor control networks; they read data pushed out to them.
Financial & Business Services GLBA · SEC Reg S-P · NYDFS 500 · FINRA
We sign the service-provider terms your regulators expect and notify you within 72 hours of a breach. Prompts, outputs and model versions are logged so AI-generated records can go to your archive, and agents stay out of suspicious-activity files.
Consumer, Retail & E-Commerce PCI DSS · CCPA · State privacy laws
We never touch card numbers and give you a PCI responsibility matrix. Our terms carry the CCPA and state processor clauses, and outreach is only drafted: your team sends it from your systems, with your suppression lists.
Energy, Infrastructure & Real Estate NERC CIP · TSA SD-02G · CIRCIA · FCRA
We connect only through your own jump host with multi-factor sign-in, which you can revoke at any time, and never to grid, pipeline or building control networks. We tell you of an incident within 24 hours, leaving room for your own reporting clocks.

Engagement lifecycle

How your data is handled from the first agreement to the day we leave.

Before we start.
A written agreement sets what we may access and why, with a data processing agreement where the law requires one, standard contractual clauses for EU and UK data, and DORA terms for EU fund managers and insurers. We name the people who can reach your data.
While we work.
Only the named people can open your company’s data, our connectors only read, and every action is logged. Anything that changes your records or reaches your customers goes through your team, and we tell you within 72 hours of any incident affecting your data.
When we leave.
We revoke our access, erase your data and hand you a signed certificate. It lists anything we could not reach, such as copies already in your own email.

AI and agents

Where models are used, and who stays in control.

One private, open-source model.
Every agent runs on the same open-source model, which we host privately. Prompts, data and outputs never go to an outside AI company, and your agreement names the model and where it runs.
No training across companies.
We never use one company’s data to train a model for another company.
People approve what matters.
Agents work within the permissions your agreement sets. Anything that changes your records or reaches your customers waits for a person on your team.
Tested on every release.
Automated tests check that credentials never reach logs, that no command crosses between companies and that our software cannot send email. A release that fails them does not ship.

Assurance

What we test today, and what comes next.

Independent audits.
We don’t yet hold a SOC 2 report or an ISO 27001 certificate, and we’ll say so plainly until we do. SOC 2 is on our roadmap. Until then we answer your security questionnaire and walk your team through our controls.
Security questions.
Email info@doranlabs.com for our security overview or to send your due diligence questionnaire.

Ask us how
we protect it.

Send your security questionnaire or ask for a walkthrough of how an engagement is protected, from the first agreement to deletion.