Privacy

DealLaunch AI is provided by DealLaunch AI Ltd, a private limited company registered in England and Wales under company number 17423669. DealLaunch AI Ltd is the controller of your account and billing data. For the project data your firm puts into its workspace, your firm is the controller and we process that data on its behalf, under our Data Processing Agreement. You can reach us at hello@deallaunch.ai.

Until DealLaunch AI Ltd takes payments in its own name, a first-month payment from the pricing page is taken through the Stripe account of Verana Ventures Ltd, which issues the receipt and keeps the payment record.

Account details you provide when you request access or sign in: your name, email, company and role.

The project data you enter: deals, firms, contacts, notes, documents (or links to them), outreach drafts and activity.

Email from your project contacts, read from your connected mailbox when replies are checked: the subject and opening text of each (up to 1,200 characters) and, on a project where automatic reply status is switched on, Jev's reading of every one, whether or not it changed a status. On those projects the same is saved, with the sender's name and address, for a reply to your outreach from someone at one of the project's firms who is not a contact but writes from that firm's own company domain, on the record of a contact at that firm. Where a reading applies to the firm, the same subject and text are also saved on each colleague's record. On those projects the names of an email's attachments are saved with it, and two more things are read to record a signed NDA or a CIM: e-signature notices saying an NDA was signed, and the mail you sent to the project's contacts. From those we save only the subject, the document names, the notice's title and the person or firm it names, on the contact's record and, where it applies to their firm, on each colleague's record at that firm on the project.

About the counterparties you send tracked documents to: when they open a tracked link, the time, their browser's user-agent string and the request-type headers we use to tell an email security scanner from a person, and, if a document asks them to accept your confidentiality wording, the name, firm and email they enter, the time, the version and the exact text they accepted. We never record their IP address.

About opens of your outreach emails: each outreach email carries a 1x1 image. When the recipient's mail app loads it, we record the time against that contact and that email. From that image we never record their IP address or browser.

Basic technical data needed to run the service (authentication sessions and error diagnostics).

To provide your private workspace - storing and displaying the deals, contacts and documents you create.

To draft and research on your request. When you use an AI feature, the relevant project context is sent to our AI provider (Anthropic) to produce a draft or research suggestion. Drafts and research suggestions are unverified and are never sent or acted on without your review. Two AI outputs take effect without a review step: a contact spreadsheet you import is added as Anthropic tidied it, and on a project where automatic reply status is switched on, TypeSafe AI's reading of an email sets the status of the contact and of their colleagues at the same firm on the project (see Outreach and email). On those projects, fixed rules with no AI also set NDA Signed or CIM Shared from an e-signature notice or a document you sent.

To email you when a counterparty opens a tracked document or accepts your confidentiality wording, at the cadence you choose in Settings (instant, hourly, a daily digest, or off). These alerts are sent through Resend and name the counterparty, their firm and the document type - never the mandate, the client or the file name.

To email you when an investor replies, at the cadence you choose in Settings, and once a day about investors from NDA Signed on who have gone quiet, unless you switch it off. These alerts are sent through Resend and name the investor and their firm - never the mandate, the client or the text of the email.

To show you and your team on the project when an outreach email was opened. Opens never appear in a client report or a share link.

We do not sell, rent or share your contact lists, and we do not use your private deal data to build a shared investor marketplace.

One thing is shared between accounts, and only this: the email FORMAT a company uses - its domain and the shape of its addresses, such as "first.last" - learned when a paid lookup on Anymail Finder or RocketReach returns an address at that company. It contains no names, no email addresses, no contacts and nothing from your workspace, and your own contact list is never a source for it. It exists so that a company's format, once learned, does not cost another lookup.

Data is stored in Supabase (PostgreSQL) with row-level security so each account only sees its own records. Outreach mailbox credentials are encrypted at rest and decrypted only on the server, to send on your instruction, to check for replies and bounces from your project contacts (and, on a project where automatic reply status is switched on, replies to your outreach from their colleagues at the same firm, e-signature notices about them and the mail you sent them) or, for Microsoft 365, to read your upcoming meetings.

Documents you upload are held in a private storage bucket and served through short-lived signed links.

A watermarked copy made for a tracked link is kept in the same private bucket, and is deleted when the link is revoked or expires, or its document is deleted - at once, or within minutes where the link was withdrawn by the database or expired unopened.

Subprocessors we rely on include Supabase (database, auth, storage), Anthropic (AI drafting/research, and tidying contact spreadsheets you import), TypeSafe AI (reading email from project contacts and replies to your outreach from their colleagues at the same firm, with the names of their attachments, on projects where automatic reply status is switched on), RocketReach (finding people at a firm and their work address, where you ask for it), Anymail Finder (finding a named person's work address, where you ask for it), Resend (our own transactional email: invites, access decisions, document alerts and reply alerts), Vercel (hosting) and your own connected email provider (Microsoft 365 / Google / SMTP) for sending and for reading replies from your project contacts and, on projects where automatic reply status is switched on, replies to your outreach from their colleagues at the same firm. The full list is at deallaunch.ai/sub-processors.

In transit: everything moves over HTTPS with TLS. The app, the API and the database are reachable no other way.

At rest: the database and the document store are encrypted at rest by our infrastructure provider (Supabase, AES-256), hosted in the EU (Frankfurt).

Credentials get a second layer on top of that. Mailbox passwords and OAuth refresh tokens - including any Google refresh token - are encrypted by the application with AES-256-GCM before they are written, under a key held only in server environment configuration and never in the database. A copy of the database alone does not yield a usable credential.

Access: every table is protected by row-level security, so an account reaches only its own rows and the projects explicitly shared with it. Mailbox credentials are stricter still - they are personal to the user who connected them and are readable by nobody else, including the owner of the workspace and including us. They are decrypted on our server only when they are used - to send, to check your mailbox for replies and bounces from your project contacts (and, on a project where automatic reply status is switched on, replies to your outreach from their colleagues at the same firm, e-signature notices about them and the mail you sent them) or, for Microsoft 365, to read your upcoming meetings - and are never decrypted in a browser.

Least privilege: we request the narrowest scope that does the job. For Gmail that is send-only - we request no Google scope that can read, search, list, download or modify your mail. For Microsoft 365 we also request permission to read mail, used to find replies and bounces from your project contacts and, on a project where automatic reply status is switched on, replies to your outreach from their colleagues at the same firm, e-signature notices about them and the mail you sent them, and to read your calendar, used to show upcoming meetings. A mailbox connected with an app password is read over IMAP for the same, and its folders are opened read-only.

Retention and deletion: disconnecting a mailbox deletes its stored credential immediately. Deleting your account removes your workspace data. We keep no copy of your mailbox. We do keep the outreach you write and send in DealLaunch, and the subject and opening text (up to 1,200 characters) of each email from a project contact found when replies are checked, on that contact's record and, where a reading applies to their firm, on their colleagues' records. On a project where automatic reply status is switched on we keep the same, with the sender's name and address, for a reply to your outreach from someone at one of the project's firms who is not a contact but writes from that firm's own company domain, on the record of a contact at that firm and, where a reading applies to the firm, on their colleagues' records. On those projects we also keep the names of those emails' attachments, and the subject, document names and title of each e-signature notice or email you sent that recorded a signed NDA or a CIM, with the person or firm a notice names, on that contact's record and, where it applies to their firm, on their colleagues' records - never the text of your email or of the notice.

People: no member of our staff reads Google user data. Access to production systems is limited to the accounts that need it and is protected by two-factor authentication.

If we discover a personal data breach, we will tell you without undue delay. Where it affects your account or billing data, we will also tell the UK Information Commission, or another supervisory authority, where the law requires it. Where it affects your firm's workspace data, we will tell your firm, as its controller, within 72 hours, as our Data Processing Agreement sets out, so that it can decide whether to notify its supervisory authority.

If you connect a Gmail account, DealLaunch AI requests one scope: https://www.googleapis.com/auth/gmail.send. It permits sending only. It gives no ability to read, search, list, download or modify any message in your mailbox, and we request no other Google scope.

We use it for one purpose: to send the outreach messages you have reviewed and chosen to send, from your own address, to the counterparties you entered on your own mandate. We never send on our own behalf and we never message anyone you have not added yourself.

We store only a refresh token, held so that sending continues to work between sessions. It is encrypted by the application with AES-256-GCM under a key that lives only in server configuration, decrypted on our server at the moment you send, and never exposed to the browser. Disconnecting the mailbox in the app deletes it immediately. See How we protect your data above for the mechanisms in full.

DealLaunch AI use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not transfer Google user data to third parties except as necessary to provide or improve this feature, to comply with applicable law, or as part of a merger or acquisition. We do not use Google user data for advertising, and we do not allow humans to read it except with your explicit consent, for security purposes, to comply with applicable law, or where the data is aggregated and anonymised.

Google user data obtained through this scope is never sent to any AI provider. Message drafting happens from the project data you entered in DealLaunch AI, before anything reaches your mailbox. A Gmail mailbox connected with an app password instead of this scope is read over IMAP for replies and, on a project where automatic reply status is switched on, for e-signature notices and the mail you sent to project contacts, as described under Outreach and email.

When you connect a mailbox, messages are sent from your own account and only for emails you have approved. If you place approved messages in the scheduled queue, they may continue to go out on a daily schedule - even while the app is closed - until the queue empties or you cancel it.

On a project where automatic reply status is switched on, we check your connected mailbox for email from that project's contacts over the last 14 days - every ten minutes, every five minutes while its Outreach page is open, and when you press Check replies. The subject and text of each such email, whatever it is about, with the project codename, the client's name and the contact's current status, are sent to TypeSafe AI's Jev model, which reads what it means. A clear reading sets the contact's status, and that of their colleagues at the same firm on the project, without a review step; an uncertain one is saved for review, except that a person writing back still moves Contacted to Replied. A status you set by hand stays until a newer reply from that contact, from a colleague at the same firm on the project, or from someone else at that firm writing from its own company domain in reply to your outreach, says otherwise - a clear new reply can reopen a pass or a pause, never a closed contact. The names of an email's attachments are sent with it; the attachments themselves are never opened, downloaded or sent, and mail from anyone who is not a contact on the project is never sent to TypeSafe AI, except a reply to your outreach from someone at one of the project's firms, written from that firm's own company domain, which is read as that firm's reply and shown on the timeline with the sender's name and address.

On the same projects, two more things are read on our server, by fixed rules and without any AI, to record a signed NDA or a CIM: e-signature notices (DocuSign, Adobe Acrobat Sign, Dropbox Sign, Signaturit, Yousign, PandaDoc and Zoho Sign) whose subject or attachment names an NDA - no other notice, request or reminder is read beyond its subject and attachment names, and only a completion counts - and the mail you sent to the project's contacts in the same 14 days - its recipients, subject, attachment names and any DealLaunch tracked link in it. Neither is sent to any AI provider, and the text of your email and of the notice is not kept. A notice that names one of the project's contacts, by their exact address, as a signer (or as the sender of an NDA it says is for this project), or a signed NDA, CIM or financial model you sent, sets NDA Signed or CIM Shared for that contact and their colleagues at the same firm on the project; it never moves anyone backwards and never reopens a pass, a pause or a closed contact. A match it is not sure of - an address the notice only mentions, a name, a firm named in the document's title, or a notice naming people at more than one firm - changes nothing and is only noted on the contact's timeline.

You are responsible for ensuring your outreach complies with applicable anti-spam and data-protection rules.

You can edit or delete records in your workspace at any time. You can export your workspace data from Settings - Security, and permanently delete your account from Settings, without asking us. To have your uploaded files erased too, or for anything else, contact us at hello@deallaunch.ai.

If you are unhappy with how we handle your personal data, you can complain to us at hello@deallaunch.ai. We will acknowledge your complaint within 30 days and tell you the outcome. You can also complain to the UK data-protection regulator, the Information Commission (ico.org.uk), or, if you live or work in the European Economic Area, to the data-protection authority of that country.