DealflowHQ
Before you buy · Security

Where your deal data lives

Two deployment shapes, one honest difference between them, and a short list of what ever leaves an instance. A firm evaluating this should be able to check every sentence on this page.

Your own private instance

Every firm gets its own instance. On your own server, we cannot read your pipeline: you own the database and the deployment, and the vendor is structurally unable to reach the data rather than restricted from it by policy.

On ours, a confidentiality agreement says we will not. That is a weaker promise than the first one and it is stated as a weaker promise, because a firm making this choice deserves to know which of the two it is buying.

Every firm gets its own instance.

Your own private instance

What leaves the machine

A room checks what it is licensed to run. What goes out with that check is an instance id, a version string, and the firm name and brand colour. No deal, no company, no document, no counts and no timing.

That is not a promise in a marketing page. It is written in the file that performs the check, on your own server, where you can read it.

Sent with the licence check

  • An instance id
  • A version string
  • The firm name
  • The brand colour

Never leaves

  • Deals
  • Companies
  • Documents
  • Counts
  • Timing

What the AI providers see

The seats reason using commercial models, so the material a seat reads is sent to a model provider to be read. On a hosted room that runs through our provider account; on a dedicated room a firm can hold its own key, and the work is on its own account.

Nothing is sent to a founder, an investor or anyone else without a partner pressing send. Every seat that produces a message drafts it and stops.

Nothing is sent to a founder, an investor or anyone else without a partner pressing send.

What the AI providers see

Two shapes, and we will tell you which is weaker

Most vendors describe one deployment and call it secure. There are two here and they are not equally strong, so this page names the difference rather than averaging it into a sentence that is true of neither.

Dedicated is the stronger promise and it is stronger for a structural reason, not a contractual one: the keys are yours, so there is nothing for us to decide about. Hosted is the convenient one, and what protects your data there is an agreement and the people who signed it.

A firm that needs the first should buy the first. We would rather say that than sell the second to somebody who assumed it was the same thing.

Dedicated

The stronger promise
Runs in
Your cloud, on your own server
Who holds the keys
You do
Can we read your pipeline?
No: we are structurally unable to reach it
What protects your data
The structure, not a contract
AI provider
Your own key, on your own account

Hosted

The convenient one
Runs in
Our cloud
Who holds the keys
We do
Can we read your pipeline?
A confidentiality agreement says we will not
What protects your data
An agreement, and the people who signed it
AI provider
Our provider account

What you can check yourself

On a dedicated instance the code is on your server. The file that performs the licence check is readable, and it names exactly what goes out: an instance id, a version, the firm name and a brand colour.

That is the standard this page is written to. Every claim above is either something you can read in the code you are running or something stated as a contractual promise rather than a technical one.

On a dedicated instance the code is on your server.

What you can check yourself
How it works

Choose the shape. Check it yourself.

  1. 1

    Need us unable to read it?

    Choose dedicated: your server, your database, your keys.

  2. 2

    Prefer convenience?

    Choose hosted, under a confidentiality agreement.

  3. 3

    Same product either way

    The same code and setup; only the cloud account differs.

  4. 4

    Check it yourself

    On a dedicated instance, read the file that names what leaves.

Questions about this part of DealflowHQ

Can DealflowHQ read our deals?

On a dedicated instance, no: you own the database and the deployment, so we are structurally unable to reach the data. On a hosted instance, a confidentiality agreement says we will not, which is the weaker promise and is stated as one.

What leaves our server?

With the licence check: an instance id, a version string, the firm name and the brand colour. No deal, company, document, count or timing.

Do AI model providers see our documents?

The material a seat reads is sent to a model provider to be read. On a hosted room that runs through our provider account; on a dedicated room you can hold your own key, so the work is on your own account.

Tenancy, what leaves an instance, and what the AI providers see. A firm of 21: you and twenty AI employees. See the whole firm and join the waitlist.