DealQ — Privacy Policy

1. Introduction

This Privacy Policy explains how DealQ Ltd. (“DealQ,” “we,” “us,” or “our”) collects, uses, stores, shares, and protects information when you (“you,” “User”) access or use DealQ and its related websites, applications, and services (collectively, the “Service”).

This Privacy Policy should be read together with our Terms and Conditions. Capitalized terms not defined here have the meaning given in the Terms and Conditions.

By using the Service, you acknowledge that you have read and understood this Privacy Policy. If you do not agree with it, please do not use the Service.

Our role. For personal data contained in User Content, including voice and meeting data and Imported Data (Section 2.1), the organization whose workspace holds it (or you, if you use the Service on your own) decides what is brought into the Service and why, and is the data controller. DealQ processes that data on its behalf, as a data processor, under the Data Processing Terms in our Terms and Conditions. For all other personal data described in this Privacy Policy, including account information, Connected Account Data, usage, device, and log data, and support communications, and for the processing DealQ carries out for its own purposes (keeping the Service secure, preventing abuse, meeting its legal obligations, and the de-identification and product-improvement use described in Section 6), DealQ Ltd. is the data controller.

If you are not a DealQ user. User Content may include information about people who do not use DealQ, such as the other party to a negotiation, a contact in a CRM, or a participant in a meeting. The organization that brought that information into the Service is responsible for it. Section 11.4 explains what you can do.

2. Information We Collect

2.1 Information You Provide to Us

• Account information. When you create an account, we collect information such as your name, email address, password (stored in hashed form), organization name, and role.
• User Content. We collect the content you submit to the Service, including typed or pasted text, uploaded documents, files, attachments, spreadsheets, presentations, and contracts, together with associated file names, folder structures, and tags.
• Voice and meeting data. Where you use voice or meeting features, we collect the audio of the session and the written transcript generated from it (“Transcription Data”). We currently retain the audio recording. If you ask us to delete the audio recording of a session, we will delete it within 72 hours of your request.
• Imported data. We collect structured data — such as CRM records, deal records, and account records — that you or your organization choose to bring into the Service through an API or an integration (“Imported Data”). Where you connect a CRM (Section 3), Imported Data means the records you choose to import into, or link to, a negotiation, and the updated copies DealQ takes of those records when you ask for a refresh or when a linked negotiation is opened. Imported Data is User Content. It is stored in your organization’s workspace, is available to the members of that workspace, and is used, shared, and retained as this Privacy Policy describes for User Content (Sections 4 to 8). Once a record is in the workspace, DealQ does not apply the sharing rules, record-level permissions, or field-level restrictions that the source system applied to it.
• Support communications. When you contact us, we collect the information you provide, such as your messages and contact details.

2.2 Information We Collect Automatically

• Usage data. Information about how you interact with the Service, such as features used, pages viewed, and actions taken.
• Device and log data. Information such as IP address, browser type, operating system, device identifiers, and timestamps.
• Cookies and similar technologies. See Section 12 (Cookies and Tracking).

2.3 Information From Third Parties

• Connected Account Data. If you choose to sign in with, or connect, a third-party identity or integration provider (the providers we currently support are listed in Section 3.1), we receive information from that provider. We call this “Connected Account Data”. Imported Data (Section 2.1) is not Connected Account Data, even where it reached DealQ through a connected account; the difference is explained at the start of Section 3. Connected Account Data is governed exclusively by Section 3 of this Privacy Policy. Where any other Section of this Privacy Policy could be read to permit a use, sharing, or retention of Connected Account Data that Section 3 does not, Section 3 prevails.
• Other sources. If you or your organization import data through an API or another integration that is not a connected account, we receive that data as authorized by you and as needed to provide the integration.

3. Connected Accounts and Integrations

This Section describes everything DealQ does with Connected Account Data: information received from a third-party identity or integration provider’s APIs when you choose to sign in with that provider or connect it to DealQ. The rules in Sections 3.2 to 3.7 apply to every provider in the same way. Section 3.1 lists, per provider, exactly what is accessed and why, and Section 3.8 records the provider-specific policy commitments we have made.

Providers today. Google, through two separate and independently optional authorizations: Sign in with Google, and Google Calendar connect; and the CRM providers listed in Section 3.1, each through its own optional connection. You may use any of them, all, or none. If we add another provider (for example, a Microsoft or GitHub sign-in or calendar), its scopes and purposes will be added to Section 3.1 before it is offered, and the same rules will apply to its data.

What you import from a CRM is User Content, not Connected Account Data. Connecting a CRM gives DealQ two different kinds of information, and this Privacy Policy treats them differently:

• The connection. The credentials the CRM provider issues for your connection; the identity of the CRM user and CRM account you connect; and CRM records that DealQ reads only to show you a list, a search result, or a preview, without saving them. This is Connected Account Data, and this Section 3 applies to it.
• What you import. The records you choose to import into, or link to, a negotiation, and each refreshed copy of them (Section 2.1). These are copied into your organization’s workspace at your direction. From that point they are Imported Data and User Content: this Section 3 no longer applies to them, and Sections 4 to 8 apply instead.

Your organization decides which CRM to connect, which records to import, and who is a member of the workspace that will be able to see them, and is responsible for having the right to bring those records, including any personal data they contain, into the Service.

3.1 Providers, and what we access

Google — Sign in with Google (authentication)

If you choose to sign in or create an account with your Google Account, DealQ requests the following non-sensitive scopes:

Google — Google Calendar connect (the meetings integration)

If you choose to connect Google Calendar (Settings → Integrations), DealQ additionally requests the following scopes. calendar.readonly is classified by Google as a sensitive scope.

Read-only, and narrower than it looks. calendar.readonly grants no ability to create, modify, move, or delete events, and DealQ never attempts to. DealQ needs to list the calendars your account can see and then read upcoming events on your primary calendar and the calendars you own; the events-only scope does not allow listing your calendars, which is why calendar.readonly is requested. DealQ uses only the calendar-list, event-list and event-get methods. It does not read calendar sharing settings, access-control lists, colors, or free/busy information.

CRM providers — the CRM integration

If you choose to connect a CRM (Settings → Integrations), you sign in to the CRM provider and authorize DealQ on that provider’s own consent screen. A workspace is linked to one CRM account at a time: the first member to connect links the workspace to that CRM account, and other members connect their own CRM user in the same account. With that authorization, DealQ:

• reads the deals available to the connection, so that you can find one;
• reads a deal you choose to import, link, or refresh, together with the records related to it — such as its company or account, its contacts and their roles, its products or line items, its quotes, and its notes and recent activities — and the definitions of the fields your CRM uses, in order to copy them into the negotiation as Imported Data;
• reads the identity of the CRM user and CRM account you connected (such as identifiers, name, email address, and time zone), to keep the workspace linked to a single CRM account, to label your connection, and to attribute and date what you log; and
• writes to the CRM only when a member asks it to. When you choose to log a meeting to the CRM, DealQ creates a record of that meeting on the linked deal (a completed call, or the provider’s equivalent activity) containing the notes you reviewed, and, if you choose, updates that deal’s next step.

DealQ does not otherwise create, change, or delete records in your CRM.

What a connection can reach depends on the provider. DealQ can read and write only what the CRM provider makes available to the authorization you grant. For some providers that is what your own CRM user is permitted to access; for others it is wider. The table states which applies, and lists the permissions DealQ requests. Write permissions are used only for the logging described above.

3.2 How we use Connected Account Data

We use Connected Account Data only to provide the user-facing features listed below, each of which is prominent in the DealQ interface. We do not use Connected Account Data for any other purpose.

• Sign you in and keep one account. The provider’s account identifier and your email address are used to create or find your DealQ account and to authenticate you.
• Show who you are. Your name and profile picture are shown in your own DealQ interface.
• Show your upcoming meetings. Events from a connected calendar are displayed to you in the meetings view.
• Attach a meeting to a negotiation. When you choose to, an event is linked to one of your negotiations so that you can open live coaching for it and see the meeting on that negotiation’s report.
• Tell deal meetings from other meetings. Attendee email addresses are compared against your negotiation counterparts, your workspace’s contact book, and company domains to label a meeting as related to a deal or to a known contact, and event type, all-day, declined, and no-video-link entries are hidden. This happens in memory for the request that displays the list, and the result is shown to you only; it is not recorded or measured.
• Send the meeting bot to a call you choose. When you switch the bot on for a specific meeting, the video-conferencing link from that event is used to schedule the bot to join that call.
• Connect your CRM. The identity of the CRM user and CRM account you connect is used to keep your workspace linked to a single CRM account, to label your connection, and to attribute and date what you log.
• Find a deal. Deals available to your connection are read from the CRM and shown to you so that you can choose one. They are not saved unless you import or link one.
• Import, refresh, and log, at your direction. When you import, link, or refresh a deal, DealQ reads it through your connection and copies it into the negotiation, where it becomes Imported Data (Section 3, introduction). When you ask DealQ to log a meeting, DealQ writes it to the CRM through your connection (Section 3.1).

Section 4 (How We Use Your Information) does not apply to Connected Account Data. In particular, we do not use Connected Account Data to monitor or analyze usage of the Service, to generate analytics, to improve our products, or to improve any model.

3.3 What we store, and for how long

• The connected-integration record. For a connected calendar we store: the provider’s access and refresh tokens, encrypted at rest with AES-256-GCM under a key held separately from the database; the connected account’s email address and provider account identifier; the list of scopes you granted; and the timestamp of the last successful sync. This record is deleted immediately when you disconnect the integration or delete your DealQ account.
• Calendar events are not copied. DealQ does not copy, cache, or index your events. Each time you view your meetings, DealQ calls the provider’s calendar API live, uses the response to render that request, and discards it. There is no calendar-event database. Where the interface or our marketing says “sync”, “synced”, or “last checked”, it refers to the last time DealQ read your calendar live to render the meetings view; no copy is kept.
• Two exceptions, each created only by your explicit action:
  • When you attach a meeting to a negotiation, the event identifier, its title, and its start time are saved on that negotiation as part of the negotiation’s workspace content — in the same way as a note you type — so that the negotiation can show which meeting it relates to. A negotiation belongs to your organization’s workspace and is shared with its members, so these fields stay with the negotiation for as long as it exists, including after you leave the workspace or delete your account, and are erased when the negotiation is deleted (they are covered by the negotiation’s deletion cascade). You can have them removed earlier by re-linking the negotiation to a different meeting or by asking us (Section 15).
  • When you switch the meeting bot on for a calendar meeting, a dispatch record stores the event identifier, the identifier of the calendar it is on and of the calendar connection it was read through, the video-conferencing link, and the meeting’s end time, so the bot can join at the right moment and not after the meeting has ended. When you disconnect the calendar or delete your DealQ account, dispatch records for meetings that have not yet started are cancelled and deleted, and those fields are erased from dispatch records for meetings that have finished. A bot that is already in a call at that moment finishes that call (at most four hours), after which the same fields fall within the deletion window in Section 8. Dispatch records are also deleted with the negotiation.
• The CRM connection record. For a CRM connection we store: the access and refresh tokens the provider issues, protected as described for provider tokens in Section 9; the identity details of the CRM user and CRM account you connected (Section 3.1); and the technical details needed to reach that account, such as its API address and region. We delete this record when you disconnect, when the workspace owner unlinks the CRM account from the workspace, or when you delete your DealQ account. The workspace’s own link to the CRM account (its identifier and name, who first connected it, and the workspace’s logging setting) is deleted when the owner unlinks it.
• What a linked negotiation keeps. When you import or link a deal, the negotiation stores the identifiers of the CRM records it corresponds to and a summary of the deal for display (such as its name, stage, amount, close date, and next step). When you log a meeting, DealQ keeps a reference to the record it created in the CRM, so that the same meeting is not logged twice. These are Imported Data, like the imported records themselves, and are retained as described in Section 8.
• Sign-in data. Your name, email address, profile picture URL, and provider account identifier from a third-party sign-in are stored on your DealQ account record, encrypted at rest on cloud infrastructure operated by our hosting provider under a data processing agreement, for as long as your account exists.
• Operational records. Our security audit log records integration events — such as connected, disconnected, token refreshed, re-authorization required, and read failed, and, for a CRM, account linked or unlinked, deal linked or unlinked, and meeting logged — together with the connected account’s email address and provider account identifier, and the identifiers of the records concerned. These entries are kept for security and fraud-prevention purposes only, do not contain the content of calendar events or of CRM records, and are not used for anything else. No analytics or telemetry system receives Connected Account Data, and calendar event content is never written to application logs.

Retention is otherwise governed by Section 8. Any Connected Account Data that remains after the deletions described above is deleted within the 90-day window stated there.

3.4 How we share Connected Account Data

We do not transfer Connected Account Data to any third party except:

• Hosting and infrastructure subprocessors (MongoDB Atlas, Railway, and Amazon Web Services), strictly for storing and operating the Service on our behalf, under contractual confidentiality and data-protection obligations. These providers store data; they do not use it.
• DealQ’s own meeting-bot runner. When you switch the bot on for a meeting, the video-conferencing link is passed to the software DealQ operates to join the call. This is part of the Service, not a third party.
• Legal process. Where required to comply with applicable law, legal process, or an enforceable governmental request.
• A merger, acquisition, or sale of assets, and then only after obtaining your explicit prior consent.

Connected Account Data — including calendar event titles, descriptions, attendees, and links, and CRM records read only to show you a list, a search result, or a preview — is never sent to any Third-Party AI Provider, speech-to-text provider, email provider, or operational-logging provider listed in Section 5. Imported Data is not Connected Account Data (Section 3, introduction); it is User Content and is processed as described in Section 5.

3.5 How humans access Connected Account Data

Calendar data, and CRM data read through a connection without being imported. DealQ personnel do not read this data except: (i) with your affirmative consent (for example, to help you with a support request); (ii) to investigate suspected abuse, fraud, or a security incident; (iii) to comply with applicable law; or (iv) in aggregated, anonymized form that cannot identify you, for internal operations.

Sign-in profile data. In addition to (i)–(iv), the name, email address, and profile picture on your account record are visible to the DealQ staff who administer accounts and respond to support requests, in our account-administration console, for those purposes only.

Reads of customer transcripts, recordings, and coaching chats by DealQ staff are recorded in our audit log.

3.6 What we never do with Connected Account Data

We do not:

• transfer, sell, or otherwise make Connected Account Data available to advertising platforms, data brokers, or information resellers;
• use Connected Account Data to serve advertisements of any kind, including retargeted, personalized, or interest-based advertisements;
• use Connected Account Data to determine credit-worthiness or for lending purposes;
• use Connected Account Data for surveillance, or make it available to any entity that conducts surveillance;
• build or maintain any database or dataset of Connected Account Data beyond the per-user records described in Section 3.3;
• use Connected Account Data for analytics, product research, usage measurement, or behavioral profiling;
• sell, rent, license, or broker Connected Account Data.

AI and machine learning. DealQ does not use Google Workspace APIs to develop, improve, or train generalized or non-personalized AI and/or ML models. More generally, DealQ does not use any provider’s APIs, or any data obtained through them (including Google Calendar data), to develop, improve, or train generalized or non-personalized artificial-intelligence or machine-learning models. We also do not use Connected Account Data to train personalized models, to fine-tune, evaluate, or prompt any model, or as training data for any Third-Party AI Provider.

The de-identified meeting transcripts described in Section 6 are produced from the call’s audio, captured by your device or by the DealQ bot as an ordinary call participant (see Section 3.9). They are not obtained through any provider API and are not derived from calendar data. The only role calendar data plays is providing the link used to join a call you have individually chosen. A transcript may naturally contain names or other details spoken during the call; those are removed by the de-identification described in Section 6.1.

3.7 How you revoke access, and what happens then

You can disconnect at any time from Settings → Integrations, or from the provider’s own account settings (for Google: myaccount.google.com/permissions). Disconnecting in DealQ sends a revocation request to the provider for the refresh token and deletes the stored connected-integration record — tokens, connected email, and scope list — immediately, and cancels any meeting-bot dispatches scheduled from that calendar as described in Section 3.3. Deleting your DealQ account runs the same revoke-and-delete steps before the account record is removed.

For a CRM, disconnecting asks the CRM provider to revoke the credentials issued for your connection and deletes your connection record (Section 3.3). The workspace owner can also unlink the CRM account from the workspace, which does the same for every member’s connection. Depending on how the provider issues credentials, revoking one connection may also end other connections made with the same CRM user, who can then reconnect. You can also remove DealQ’s access from the CRM provider’s own settings. Disconnecting or unlinking does not remove Imported Data already in your workspace (Section 8): a member can delete it there, or you can ask us to (Section 15). DealQ does not delete or change anything in your CRM when you disconnect or unlink.

3.8 Provider policy commitments

• Google. DealQ’s use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

3.9 The meeting bot and Google Meet

The optional DealQ meeting bot joins a video call as a visible, named participant in order to capture the call’s audio. It does this as an ordinary meeting participant, signed in with a Google account owned by DealQ that is not linked to you or your connected accounts. It does not use any provider API scope, the Google Meet API, the Meet Media API, or any other Google Workspace API, and it reads no data from your connected accounts. The only Connected Account Data involved is the video-conferencing link used to schedule it (Section 3.3). Audio and transcripts it captures are “Voice and meeting data” under Section 2.1 and follow the retention and deletion terms stated there, including deletion of a session’s audio within 72 hours of your request.

3.10 New uses require your consent

We will not use Connected Account Data for any purpose not described in this Section 3 without first notifying you and obtaining your consent. Section 14 (Changes to This Privacy Policy) does not allow us to add a new use of Connected Account Data by notice alone.

4. How We Use Your Information

This Section applies to information other than Connected Account Data. Connected Account Data is used only as described in Section 3.

We use the information described in Section 2 to:

• provide, operate, and maintain the Service and generate Outputs for you;
• create and authenticate your account and verify your identity;
• provide customer support and respond to your requests;
• maintain the security and integrity of the Service, and prevent fraud and abuse;
• monitor, analyze, and improve the performance and features of the Service;
• generate aggregated, de-identified analytics that cannot reasonably be re-associated with you or any identifiable individual;
• improve our models as specifically and narrowly described in Section 6;
• communicate with you about the Service, including service-related notices; and
• comply with legal obligations and enforce our agreements.

5. AI Processing and Third-Party AI Providers

The Service operates by sending User-provided inputs (typed text, uploaded documents, attachments, meeting transcripts, Imported Data, metadata, and contextual information, together “User Content”) to third-party large language model and infrastructure providers (“Third-Party AI Providers”) so that we can generate outputs for you. Connected Account Data is not User Content and is never sent to a Third-Party AI Provider (see Section 3.4).

We currently rely on the following categories of service providers and sub-processors:

• AI model providers (OpenAI and Anthropic; we may add Google, Mistral, Cohere, or Microsoft models and will list them here before use): receive User Content to generate preparation guidance and live coaching. None of them receives Connected Account Data.
• Speech-to-text (Deepgram): receives meeting audio to produce real-time transcripts.
• Document processing (Google Cloud Document AI): receives uploaded documents to extract their text.
• Search and embeddings (Voyage AI): receives document and query text to power search inside your workspace.
• Hosting and storage (MongoDB Atlas, Railway, and Amazon Web Services): store your account data, workspace data, and files.
• Transactional email (Postmark): receives your email address and message content to send account and security emails.
• Operational logging (Langfuse): receives model-request metadata, and only where we enable it for debugging, request and response content, to help us monitor reliability.

Web search. Some features search the public web, either when you ask for research on an organization or a person, or where the Service looks something up in order to answer you. The search is carried out by the AI model provider handling that request, using its own search service. The search terms are drawn from your request and from the User Content in the negotiation, and may include the names of organizations and people. The pages the provider retrieves come from third-party websites that DealQ does not control. What comes back is used to generate the output for you, and the output, with the sources it cites, is kept as part of your workspace’s content. It may be inaccurate or out of date, or may concern a different person or organization with a similar name.

Imported Data is processed in the same way as other User Content: it may be sent to the AI model providers, and to the other service providers listed above, for the purposes this Privacy Policy describes for User Content. It is not used to train models (Section 6.2).

We keep an up-to-date list of the providers we use and update this Privacy Policy if the categories of recipients change materially.

Third-Party AI Providers operate independent infrastructure governed by their own terms of service, privacy policies, data processing agreements, and security practices, which are outside of our control.

Where Third-Party AI Providers offer them, we configure available endpoints to disable provider-side training and to minimize data retention, including the use of “zero-retention” or “no-training” enterprise modes where available.

6. AI Model Training

This Section governs all uses of User Content for the training, fine-tuning, evaluation, or improvement of any AI model, whether operated by DealQ or a Third-Party AI Provider.

6.1 Data We May Use for Product and Model Improvement (Transcripts and Coaching Tips)

We may use Transcription Data, together with the coaching tips and outputs generated during your sessions, to test, evaluate, train, fine-tune, and improve our own models, prompt systems, and product, and to engage Third-Party AI Providers in supervised fine-tuning or evaluation workflows on our behalf.

Transcription Data is produced from audio captured by your device or by the DealQ meeting bot as an ordinary call participant. It is not obtained through any provider API. No Connected Account Data of any kind — including calendar event titles, descriptions, attendee lists, or sign-in profile data — is included in any training, fine-tuning, or evaluation dataset.

Before any Transcription Data is used for these purposes, we apply commercially reasonable de-identification and redaction processes designed to remove direct identifiers such as names, email addresses, phone numbers, and organization names.

For this limited purpose, you grant DealQ a non-exclusive, worldwide, royalty-free license to use the de-identified Transcription Data. This license is limited to the model-training and evaluation purposes described in this Section, and it ends when you opt out as described below.

Opt-out. You may opt out of training use of your Transcription Data at any time by emailing manuel@dealq.io. Once you opt out, we will stop using your Transcription Data for model training and remove it from the training datasets used for future model versions. Because trained models cannot be selectively reversed, opting out does not affect models that completed training before your request.

6.2 Data We Do Not Use for Model Training

We do not use the following categories of information to train, fine-tune, or evaluate any model, whether ours or a Third-Party AI Provider’s:

• documents, files, attachments, spreadsheets, presentations, contracts, and other artifacts you upload;
• text you paste or type into the Service’s input fields, prompt windows, or workspaces;
• structured customer data, CRM records, deal records, and account records imported via API or integration;
• metadata, file names, folder structures, and tags associated with the above;
• all Connected Account Data described in Section 3, including Google Calendar data and Sign in with Google data.

For these categories, we configure available Third-Party AI Provider endpoints to disable training, model improvement, and extended retention to the maximum extent commercially offered. This data is processed solely to generate Outputs for you in real time.

6.3 Caveats

You acknowledge that: (a) de-identification is a probabilistic process and cannot eliminate all theoretical risk of re-identification; (b) Third-Party AI Providers may independently retain inputs and outputs for limited periods for trust-and-safety, abuse-detection, and legal-compliance purposes, even where training is disabled; and (c) we may modify the scope of this Section prospectively upon notice, with no retroactive effect on User Content already processed.

7. How We Share Your Information

We share information only as described below. Connected Account Data is shared only as described in Section 3.4.

• Service providers and subprocessors. With the hosting, infrastructure, and processing providers listed in Section 5, who process data on our behalf to operate the Service under contractual confidentiality and data-protection obligations. We use no analytics provider.
• Third-Party AI Providers. As described in Section 5.
• Legal and safety. Where required to comply with applicable law, legal process, or enforceable governmental request, or to protect the rights, property, or safety of DealQ, our users, or others (for Connected Account Data, only as permitted by Section 3.4).
• Business transfers. In connection with a merger, acquisition, financing, or sale of assets, subject to this Privacy Policy — and, for Connected Account Data, only after obtaining your explicit prior consent.
• A service you connect, at your direction. When you ask DealQ to send information to a service you have connected — for example, to log a meeting to your CRM — we send what you asked us to send to that service, through your connection. Once there, it is held by that service under your organization’s agreement with its provider, and DealQ does not control how it is used, shared, kept, or deleted.
• With your consent. Where you have directed or authorized us to share information (for Connected Account Data, only as permitted by Section 3.4).

No sale of personal data. We do not sell, rent, license, or broker User Content or personal data to advertisers, data brokers, or other third parties for commercial gain, and we do not engage in cross-context behavioral advertising.

8. Data Retention

We retain personal data for as long as needed to provide the Service and fulfill the purposes described in this Privacy Policy, unless a longer retention period is required or permitted by law.

Account data is retained for as long as your account remains active. Provider access and refresh tokens are deleted immediately when you disconnect an integration; other Connected Account Data is deleted as described in Section 3.3. When you delete your account, or request deletion, we delete or de-identify the associated personal data within 90 days, except where retention is required for legal, security, or fraud-prevention purposes. Connected Account Data is always deleted rather than de-identified, with two stated exceptions: a meeting title attached to a shared negotiation stays with that negotiation as workspace content (Section 3.3), and security audit-log entries recording that an integration was connected or disconnected are kept for security and fraud-prevention purposes only. Imported Data is kept as part of your workspace’s content. What is held on a negotiation is deleted with that negotiation; the companies and people that an import adds to, or updates in, your workspace’s shared records stay there, for use across negotiations, until a member deletes them or the workspace is deleted. Disconnecting a CRM, or unlinking a CRM account, does not delete Imported Data. Information DealQ sent to a connected service at your request is held by that service, not by DealQ, and is not deleted by anything you do in DealQ.

9. Data Security

We take reasonable and appropriate technical and organizational measures designed to protect personal data against unauthorized access, use, alteration, loss, or disclosure. These include: TLS encryption for all data in transit; encryption at rest on our hosting providers’ infrastructure; provider access and refresh tokens additionally encrypted with AES-256-GCM under a key held outside the database; role-based access to production systems limited to DealQ staff who need it; short-lived, HttpOnly session cookies; and an audit log of security-relevant events and of staff access to customer content. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

10. International Data Transfers

DealQ and its service providers may process personal data in countries other than your own, including outside the United Kingdom and the European Economic Area. Where we transfer personal data internationally, we rely on appropriate safeguards, such as the UK International Data Transfer Agreement, the UK Addendum, or the European Commission’s Standard Contractual Clauses.

11. Your Privacy Rights

11.1 United Kingdom and EEA (UK GDPR / GDPR)

If you are in the UK or the EEA, you have the right to access, correct, delete, restrict, or object to the processing of your personal data, the right to data portability, and the right to withdraw consent where processing is based on consent. Where DealQ is the data controller (Section 1), we process personal data on the lawful bases of performance of a contract, our legitimate interests, your consent, and compliance with legal obligations. Where DealQ is a data processor, the lawful basis is decided by the organization that is the data controller.

You also have the right to lodge a complaint with a supervisory authority, such as the UK Information Commissioner’s Office (ICO).

11.2 California (CCPA / CPRA)

If you are a California resident, you have the right to know what personal information we collect, to access and delete it, to correct inaccurate information, and to opt out of the sale or sharing of personal information. As stated in Section 7, we do not sell or share personal information. We will not discriminate against you for exercising your rights.

11.3 Exercising Your Rights

To exercise any of these rights, contact us at manuel@dealq.io. We will respond within the timeframes required by applicable law. We may need to verify your identity before fulfilling your request.

11.4 Information About You in Someone Else’s Workspace

If you believe an organization has put information about you into DealQ, for example as the other party to a negotiation or as a participant in a recorded meeting, that organization is the data controller for it (Section 1) and is the right place to send your request. If you contact us instead, we will pass your request to that organization where we can identify it, and we will help it respond.

12. Cookies and Tracking

We use first-party cookies and similar technologies only to operate the Service, remember your preferences, and maintain sessions. We use no analytics or advertising cookies. You can control cookies through your browser settings; disabling some cookies may affect the functionality of the Service. For details on the specific cookies and storage we use, see our Cookie Policy.

13. Children’s Privacy

The Service is not directed to children under the age of 16, and we do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us so we can delete it.

14. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Material changes will be communicated through the Service or by other reasonable means. A new use of Connected Account Data additionally requires your consent, as stated in Section 3.10. Any modification operates prospectively only and will not retroactively change the treatment of User Content already processed. The “Last Updated” date above indicates when this Policy was last revised.

15. Contact Us

For questions about this Privacy Policy, to exercise your data rights, or to opt out of training use of Transcription Data, contact us at:

DealQ Ltd. Email: manuel@dealq.io