Legal
Privacy Policy
Last updated
This policy explains what data Co-Signal processes, why, who else processes it on our behalf, and how you can exercise your rights over it. It applies to co-signal.com and the Co-Signal application.
What data we process
Co-Signal processes the following categories of data:
- Workspace and user identity. Your name and email address, from the sign-in provider you use to create your account, plus your workspace membership and role.
- CRM-derived account, contact, opportunity and lead records. When you connect Salesforce or import a CSV file, we ingest and store the account, contact, opportunity and lead records you choose to connect, so we can compute overlaps with your partners.
- Encrypted CRM and Slack access tokens. The OAuth access and refresh tokens issued by your connected CRM, and the access token issued when your workspace connects Slack, encrypted at rest (AES-256-GCM), so Co-Signal can keep your data in sync and send your Slack notifications without storing these credentials in plain text.
- Sharing rules and their audit log. The visibility level and field-level choices you set for each partner, and a log of every change made to them, including who made the change and when.
- Website enquiries and demo bookings. What you send through our contact form, our demo request form or our booking page: your name, work email address, company, role, company size, CRM and optional message, the source details (the page, the landing page, the referring site and campaign values) and, for a booking, the time you choose.
- Co-Signal for Chrome (browser extension). The extension shows a Co-Signal button on websites and on Salesforce, HubSpot and LinkedIn pages. Nothing is sent when a page loads. When you click the button or icon, or while the Co-Signal panel is open, it sends the current site's domain to Co-Signal to find the matching account. On a Salesforce, HubSpot or LinkedIn page it sends the record id, company name and website of the record you are viewing instead. It does not read or send page content from other websites, and it does not sell or share browsing data. It keeps your Co-Signal sign-in on your device and saves the position of its button in your Chrome settings.
- Operational logs. Standard server request and error logs generated by running the service.
Lawful basis and roles
For CRM-derived account, contact and opportunity records, your company is the data controller and Co-Signal is the data processor: you decide what to connect and what to share with a partner, and we process it under your instructions to provide the service. For your own workspace and user identity, and for the leads you submit through our contact form, Co-Signal is the data controller. We set analytics cookies only with your consent, which you can withdraw at any time with Cookie settings.
Who processes data for us
We use a small number of subprocessors, each of which is traceable to a real, currently-configured integration in our production environment. We do not use any subprocessor beyond the ones listed here.
| Subprocessor | What it processes | Purpose |
|---|---|---|
| Google Cloud Platform (Firebase) | Workspace and user identity, connected CRM account, contact, opportunity and lead records, encrypted CRM and Slack access tokens, sharing rules and their audit log, contact-form leads, and operational logs. | Identity, application data storage, and application hosting: Firebase Authentication signs users in, Cloud Firestore stores every workspace, account, contact, opportunity, sharing rule, audit log entry and lead, and Cloud Run (via Firebase App Hosting) runs the application server. |
| DeepSeek | For smart matching, candidate account identity evidence (company names, domains and other CRM-derived matching signals). For Ask Agent, the question a member asks plus the account, opportunity, partner, co-sell request and priority evidence that member is already authorized to see. For drafts, the account, partner and opportunity names and the opportunity's stage and close date. No CRM access tokens are ever sent. | AI language model provider behind Co-Signal's AI features: smart matching (fuzzy company-identity classification beyond exact domain matching), Ask Agent answers and recommendation explanations, and drafts of co-sell requests. |
| Slack | A member's email address (used to find that member's Slack account), partner company names, CRM account names, the text of co-sell requests, summaries of sharing changes, overlap, opportunity and request counts, and links back to Co-Signal. | Notifications for workspaces that connect Slack: channel messages about co-sell requests and reminders, new overlaps, sharing changes and match reviews, and personal direct-message digests of a member's overlaps and open requests. |
| Resend | Recipient email addresses, the name of the person who sent an invitation, workspace and partner company names, invitation links, and the content of each email. For website enquiries and bookings, the alert to the Co-Signal team carries the enquirer's name, work email address, company, role, company size, CRM, message and source details, and the booking confirmation carries the booked time, the Google Meet link and the private cancellation link. | Transactional email: teammate and partner invitations, service notices to workspace users (for example, a change to what a connected AI assistant can see), website enquiry alerts and acknowledgements, and demo booking confirmations. |
| Google Analytics | A pseudonymous browser identifier from the _ga cookies, the address of each page visited with only campaign (utm) values kept, the site a visitor came from (its origin when it is another site), the page title, the conversion names generate_lead (with whether it came from the contact form or a demo request) and book_demo, and the technical details every web request carries, such as the IP address and browser type. No name, email address or message is sent. | Measuring which marketing pages are visited and which forms lead to a demo request or a message. It loads only after a visitor accepts analytics cookies, and never on the private page used to cancel a booking. |
| HubSpot | For an enquiry: name, work email address, company, the message and the source details (the page, landing page, referring site and campaign values). For a demo request or booking also role, company size and CRM and, for a booking, the meeting time and Google Meet link. Our server sends the hubspotutk cookie value with a submission only if the visitor accepted analytics cookies, and never sends the visitor's IP address. The tracking code sets the hubspotutk, __hstc, __hssc and __hssrc cookies and receives page views (the page path with only campaign values kept) and the technical details every web request carries, such as the IP address and browser type. | Co-Signal's own sales and marketing CRM for co-signal.com: each contact form message, demo request and booked demo is sent to our HubSpot account as a form submission, and a booked demo is also logged there as a meeting. HubSpot's tracking code runs only after a visitor accepts analytics cookies; it records page views and links a later form or booking to earlier visits. |
| Cloudflare (Turnstile) | The signals Cloudflare's Turnstile script collects in the browser to issue a one-time token, including the visitor's IP address and browser details as with any request to Cloudflare, and the token itself. Our server sends Cloudflare only its secret key and that token to verify it: it does not send your IP address, name, email address or message. Turnstile sets no cookie on co-signal.com. | Checking that the contact form, the demo request form and the demo booking form are being completed by a person. Turnstile runs on the pages that carry one of those forms. |
| Google Calendar (Google Workspace) | To find open times, only the times our calendars are busy. For a booking: the booked time, the guest's name and work email address, the company name, the optional message, the private cancellation link and the Google Meet link, all held in the calendar event, which also invites the calendar of the Co-Signal team member who hosts the demo. | Finding open demo times and creating the Google Calendar invitation, with a Google Meet link, for each booked demo. Google emails the invitation to the guest, and the event is deleted when a booking is cancelled. |
- Subprocessor
- Google Cloud Platform (Firebase)
- What it processes
- Workspace and user identity, connected CRM account, contact, opportunity and lead records, encrypted CRM and Slack access tokens, sharing rules and their audit log, contact-form leads, and operational logs.
- Purpose
- Identity, application data storage, and application hosting: Firebase Authentication signs users in, Cloud Firestore stores every workspace, account, contact, opportunity, sharing rule, audit log entry and lead, and Cloud Run (via Firebase App Hosting) runs the application server.
- Subprocessor
- DeepSeek
- What it processes
- For smart matching, candidate account identity evidence (company names, domains and other CRM-derived matching signals). For Ask Agent, the question a member asks plus the account, opportunity, partner, co-sell request and priority evidence that member is already authorized to see. For drafts, the account, partner and opportunity names and the opportunity's stage and close date. No CRM access tokens are ever sent.
- Purpose
- AI language model provider behind Co-Signal's AI features: smart matching (fuzzy company-identity classification beyond exact domain matching), Ask Agent answers and recommendation explanations, and drafts of co-sell requests.
- Subprocessor
- Slack
- What it processes
- A member's email address (used to find that member's Slack account), partner company names, CRM account names, the text of co-sell requests, summaries of sharing changes, overlap, opportunity and request counts, and links back to Co-Signal.
- Purpose
- Notifications for workspaces that connect Slack: channel messages about co-sell requests and reminders, new overlaps, sharing changes and match reviews, and personal direct-message digests of a member's overlaps and open requests.
- Subprocessor
- Resend
- What it processes
- Recipient email addresses, the name of the person who sent an invitation, workspace and partner company names, invitation links, and the content of each email. For website enquiries and bookings, the alert to the Co-Signal team carries the enquirer's name, work email address, company, role, company size, CRM, message and source details, and the booking confirmation carries the booked time, the Google Meet link and the private cancellation link.
- Purpose
- Transactional email: teammate and partner invitations, service notices to workspace users (for example, a change to what a connected AI assistant can see), website enquiry alerts and acknowledgements, and demo booking confirmations.
- Subprocessor
- Google Analytics
- What it processes
- A pseudonymous browser identifier from the _ga cookies, the address of each page visited with only campaign (utm) values kept, the site a visitor came from (its origin when it is another site), the page title, the conversion names generate_lead (with whether it came from the contact form or a demo request) and book_demo, and the technical details every web request carries, such as the IP address and browser type. No name, email address or message is sent.
- Purpose
- Measuring which marketing pages are visited and which forms lead to a demo request or a message. It loads only after a visitor accepts analytics cookies, and never on the private page used to cancel a booking.
- Subprocessor
- HubSpot
- What it processes
- For an enquiry: name, work email address, company, the message and the source details (the page, landing page, referring site and campaign values). For a demo request or booking also role, company size and CRM and, for a booking, the meeting time and Google Meet link. Our server sends the hubspotutk cookie value with a submission only if the visitor accepted analytics cookies, and never sends the visitor's IP address. The tracking code sets the hubspotutk, __hstc, __hssc and __hssrc cookies and receives page views (the page path with only campaign values kept) and the technical details every web request carries, such as the IP address and browser type.
- Purpose
- Co-Signal's own sales and marketing CRM for co-signal.com: each contact form message, demo request and booked demo is sent to our HubSpot account as a form submission, and a booked demo is also logged there as a meeting. HubSpot's tracking code runs only after a visitor accepts analytics cookies; it records page views and links a later form or booking to earlier visits.
- Subprocessor
- Cloudflare (Turnstile)
- What it processes
- The signals Cloudflare's Turnstile script collects in the browser to issue a one-time token, including the visitor's IP address and browser details as with any request to Cloudflare, and the token itself. Our server sends Cloudflare only its secret key and that token to verify it: it does not send your IP address, name, email address or message. Turnstile sets no cookie on co-signal.com.
- Purpose
- Checking that the contact form, the demo request form and the demo booking form are being completed by a person. Turnstile runs on the pages that carry one of those forms.
- Subprocessor
- Google Calendar (Google Workspace)
- What it processes
- To find open times, only the times our calendars are busy. For a booking: the booked time, the guest's name and work email address, the company name, the optional message, the private cancellation link and the Google Meet link, all held in the calendar event, which also invites the calendar of the Co-Signal team member who hosts the demo.
- Purpose
- Finding open demo times and creating the Google Calendar invitation, with a Google Meet link, for each booked demo. Google emails the invitation to the guest, and the event is deleted when a booking is cancelled.
Cloudflare's Turnstile Privacy Addendum describes how Cloudflare handles the data Turnstile collects.
Google user data. Our demo booking calendar connects to Google Calendar with two permissions only: to see when our calendars are busy, and to create and delete the events it makes for booked demos. We use that access only to offer open demo times and to manage those events. We do not sell this data, use it for advertising, or let anyone read it except to run the booking service, keep it secure or meet a legal obligation. Co-Signal's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Connected CRMs are not subprocessors: they are data sources your workspace authorizes. When your workspace connects Salesforce, Co-Signal reads its account, contact, opportunity and lead records. When your workspace connects HubSpot, Co-Signal reads its company, contact and deal records and its list of owners. Both connections use the OAuth access granted when the connection is made. HubSpot asks for some permissions as optional, and an admin can decline them.
Writing into your CRM (CRM write-back) is optional and is controlled by a workspace admin. If an admin sets up a CRM destination, Co-Signal writes into your own Salesforce or HubSpot account only after the admin has confirmed a preview. For accounts, it writes an overlap summary, an overlap count, a link back to Co-Signal and, if chosen, partner names, partners with open opportunities and the best overlap tier, together with a sync status and a last synced time. It can also write one overlap record per partner and account (partner name and domain, overlap tier and score, relationship and open opportunity status, and a link), and in HubSpot it can keep a contact list current for each saved report you choose. Co-Signal writes partner information only where that partner has allowed it to reach CRMs. If a partner withdraws that permission or the partnership ends, Co-Signal removes that partner's data from your CRM. Your users can also add a contact that a partner has shared (its name, title and partner attribution) to your CRM.
An admin can turn a destination off at any time. Co-Signal then stops writing and marks the records it created as "No longer updated". An admin can then choose "Remove Co-Signal data", which, after a preview and confirmation, deletes or clears only what Co-Signal wrote. If a CRM is disconnected, Co-Signal keeps the encrypted access tokens for at most 30 days, only so that this marking and removal can still be carried out. It then revokes the refresh token where the CRM allows it and deletes the tokens, sooner if a removal completes with nothing left. Co-Signal keeps a record of what it wrote (identifiers and fingerprints only, not partner names or CRM values) for 30 days after a record is removed, and keeps the result of a removal for 400 days. Co-Signal's own use of HubSpot for website enquiries and demo bookings is separate and is listed above.
Cookies and similar technologies
This site sets the cookies below. Strictly necessary cookies are always on. Analytics cookies are set only if you accept them, and you can change your choice at any time with Cookie settings in the footer. We use Google Analytics and HubSpot tracking to understand how the site is used and which pages lead to a demo request or a message. The private page you use to cancel a booking is never measured.
We keep an anonymous record of each cookie choice for 24 months, so we can show that a choice was made. It holds your consent ID, your choices, whether you made them in the banner or in Cookie settings, the banner and notice versions, the site address and the time. It holds no IP address, browser details, email address or page address.
Strictly necessary
| Cookie | What it does | Provider | Lifetime |
|---|---|---|---|
| cs_consentStrictly necessary | Remembers your cookie choice, a random consent ID and the version of the cookie banner you answered, so we do not ask again until the banner changes. | Co-Signal | 6 months |
| Cloudflare TurnstileStrictly necessary | Checks that a form is being completed by a person. Sets no cookie on co-signal.com. | Cloudflare | Not applicable |
- cs_consentStrictly necessary
- What it does
- Remembers your cookie choice, a random consent ID and the version of the cookie banner you answered, so we do not ask again until the banner changes.
- Provider
- Co-Signal
- Lifetime
- 6 months
- Cloudflare TurnstileStrictly necessary
- What it does
- Checks that a form is being completed by a person. Sets no cookie on co-signal.com.
- Provider
- Cloudflare
- Lifetime
- Not applicable
Analytics, only if you accept
| Cookie | What it does | Provider | Lifetime |
|---|---|---|---|
| cs_first_touchAnalytics | Remembers the page, the site it came from and the campaign that first brought you here, so a later demo request or booking can be tied to it. | Co-Signal | 180 days |
| _gaAnalytics | Lets Google Analytics tell one browser from another. | 2 years | |
| _ga_<ID>Analytics | Keeps the state of a visit for Google Analytics. | 2 years | |
| hubspotutkAnalytics | Lets HubSpot recognise your browser, so a form you send is linked to your earlier visits. | HubSpot | 6 months |
| __hstcAnalytics | HubSpot's main tracking cookie: when you first, last and now visited, and how many visits. | HubSpot | 6 months |
| __hsscAnalytics | Tells HubSpot whether this is a new visit. | HubSpot | 30 minutes |
| __hssrcAnalytics | Tells HubSpot whether you have restarted your browser. | HubSpot | End of your visit |
- cs_first_touchAnalytics
- What it does
- Remembers the page, the site it came from and the campaign that first brought you here, so a later demo request or booking can be tied to it.
- Provider
- Co-Signal
- Lifetime
- 180 days
- _gaAnalytics
- What it does
- Lets Google Analytics tell one browser from another.
- Provider
- Lifetime
- 2 years
- _ga_<ID>Analytics
- What it does
- Keeps the state of a visit for Google Analytics.
- Provider
- Lifetime
- 2 years
- hubspotutkAnalytics
- What it does
- Lets HubSpot recognise your browser, so a form you send is linked to your earlier visits.
- Provider
- HubSpot
- Lifetime
- 6 months
- __hstcAnalytics
- What it does
- HubSpot's main tracking cookie: when you first, last and now visited, and how many visits.
- Provider
- HubSpot
- Lifetime
- 6 months
- __hsscAnalytics
- What it does
- Tells HubSpot whether this is a new visit.
- Provider
- HubSpot
- Lifetime
- 30 minutes
- __hssrcAnalytics
- What it does
- Tells HubSpot whether you have restarted your browser.
- Provider
- HubSpot
- Lifetime
- End of your visit
Google Calendar, Cloudflare Turnstile, Google Analytics and HubSpot process data for us as described in Who processes data for us. Lifetimes of the Google and HubSpot cookies are those providers' own figures.
Where data is stored and processed
Our application and database run in Google Cloud's europe-west4 region (the Netherlands), inside Firestore's eur3 multi-region, matching the region recorded in our deployment runbook.
Our AI features (smart matching, Ask Agent and co-sell request drafts) send the data described for DeepSeek above to DeepSeek, through its API at api.deepseek.com. DeepSeek's own privacy policy (last updated 10 February 2026) states that DeepSeek directly collects, processes and stores personal data in the People's Republic of China. We therefore treat data sent to DeepSeek as processed and stored in the People's Republic of China, outside the European Union.
Slack, Resend, Google Analytics, Google Calendar and Cloudflare process data on their own infrastructure, in locations each provider determines. Co-Signal's own HubSpot account, used for website enquiries and bookings, is hosted in HubSpot's EU data centre.
Retention and deletion
We retain your data for as long as your workspace remains active. To request deletion of your workspace or any data within it, contact us through our contact page. We will confirm deletion in writing once it is complete.
Website enquiries and demo bookings, with their source details, are kept in our database for 24 months and then deleted automatically, unless you become a customer, in which case they are kept with your account records. Your workspace data is kept as described above. Copies held in HubSpot and in Google Calendar are not removed by that automatic step; to have them deleted, contact us through our contact page.
Cookie choice records are kept for about 24 months and then deleted automatically.
Your data subject rights
Depending on where you are located, you may have the right to access, correct, delete, or export your personal data, or to object to or restrict how we process it. To exercise any of these rights, contact us and we will respond within a reasonable time.
Security practices
- CRM access tokens are encrypted at rest.
- Every sharing decision is enforced server-side, through one authorization layer every surface of the product calls through.
- Changes to sharing rules are written to an audit log.
- Every new partnership starts at the most conservative sharing default.
This policy was drafted for Co-Signal and reviewed by our team before publication. A review by a qualified legal professional is a planned post-launch item, not something that has happened yet.