Back to Privacy CenterSalesQL·Legal

On this page

1. What the Contributor Program is2. Who participates in the Program3. Signals processed under the Program3.1 Browser-extension observations3.2 Verification-derived signals3.3 Deliverability and freshness signals4. Legal basis5. Provenance, confidence and what is not exposed6. Safeguards7. Customer obligations under the Program8. Business Contacts — your rights9. Changes to these Terms10. Contact
Back to top
  1. Privacy Center/
  2. Resources/
  3. Contributor Program Terms

SalesQL Contributor Program Terms

v2.0Updated 2 June 2026Effective 2 July 2026

legal.localeNotice.title

legal.localeNotice.body

legal.localeNotice.cta

These Contributor Program Terms (the “Contributor Program Terms”) explain how the SalesQL Contributor Program works, who participates in it, what data SalesQL processes through it, on what legal basis, and what safeguards apply. They are part of the binding agreement between SALESQL LTD (“SalesQL”, “we”, “us” or “our”) and Customers and End Users of the Services, and they supplement the Privacy Policy, the Terms of Service, the Acceptable Use Policy (AUP) and the Browser Extension Notice.

Capitalised terms used here have the meanings given in the Terms of Service and the Privacy Policy.

#1. What the Contributor Program is

SalesQL maintains a B2B database of professional contact information used by Customers for sales, marketing, recruiting and verification. To keep that database accurate, fresh and relevant at scale, SalesQL processes signals generated by the routine use of the SalesQL browser extension, which observes the professional information of profile pages End Users view on professional networking sites (primarily LinkedIn), together with technical signals generated by the SalesQL email and phone verification feature.

This collective set of signals, and the safeguards we apply to them, is the SalesQL Contributor Program (the “Program”). The Program ensures the Profiles Database stays current — for example, when a professional changes employer, that change can be observed and used to update the underlying record for the benefit of all Customers.

#2. Who participates in the Program

Use of the SalesQL browser extension constitutes participation in the Program. This is a structural feature of the browser extension, not an opt-in setting. By installing the browser extension, or by allowing End Users in the Customer’s workspace to do so, the Customer and its End Users participate in the Program.

The rest of the SalesQL Services — the web application, the REST API, the Model Context Protocol (MCP) Server and Campaigns — can be used independently of the browser extension and do not generate Contributor Program signals.

A Customer or End User who does not wish to participate in the Program should:

  • Not install the SalesQL browser extension (and uninstall it if previously installed).

These actions stop further generation of Contributor Program signals from the Customer’s account. Past signals already incorporated into the Profiles Database are not retroactively erased by uninstallation; data subjects whose information has been incorporated retain the right to request removal as described in Section 8.

#3. Signals processed under the Program

#3.1 Browser-extension observations

When an End User uses the SalesQL browser extension on a profile page on a supported professional networking site, the extension reads the professional information rendered on that page through the End User’s own authenticated session. The observed information may include full name, current and past job titles, current and past employers, employment dates, education, skills, certifications, languages, professional summary, the public profile URL and avatar, and other professional fields rendered on the profile.

These observations are used to maintain the freshness, accuracy and quality of the Profiles Database. The Browser Extension Notice describes the extension’s behaviour and the sites on which it operates.

#3.2 Verification-derived signals

The signals processed under the Contributor Program are generated when a Customer or End User invokes the SalesQL email or phone verification feature — bounces, mailbox-not-found, domain-not-found, deferral codes, MX-record health, line-status checks and similar SMTP / provider responses — which confirm whether a contact point is still valid and in use. Signals generated by sending through Campaigns (deliveries, bounces, opens, replies and similar) are used solely to report to the relevant Customer on its own campaigns under the processor relationship described in Privacy Policy Section 3.6, and are not incorporated into the Profiles Database or this Program.

#3.3 Deliverability and freshness signals

The Program incorporates these verification-derived signals to confirm whether contact points remain valid and in use. Deliverability signals generated by sending through Campaigns are used only to report to the relevant Customer on its own campaigns and are not incorporated into the Profiles Database.

#4. Legal basis

For SalesQL’s processing under the Program:

  • Professional contact information about Business Contacts (third-party data subjects) generated through the Program is processed on the basis of legitimate interests under Article 6(1)(f) UK/EU GDPR, supported by a documented Legitimate Interests Assessment (LIA) and a dedicated Data Protection Impact Assessment (DPIA). A summary of the LIA and DPIA is available on request to privacy@salesql.com.
  • Account-level data of the Customer and its End Users (mailbox connection, sending-domain configuration, account-level usage) is processed on the basis of performance of contract under Article 6(1)(b) UK/EU GDPR.
  • The processing of message contents and metadata sent or received through Campaigns is governed separately by the processor relationship in the SalesQL Data Processing Addendum (DPA) and Privacy Policy Section 3.6; that mailbox data is not part of this Program.

#5. Provenance, confidence and what is not exposed

We maintain source, freshness, verification and confidence metadata internally to support the quality of the Profiles Database and the handling of data-subject rights. Source signals from any of the methods described in Section 3 contribute to the internal confidence and freshness assessment of the relevant data point.

Provenance metadata is used by SalesQL for these internal purposes. We do not disclose, to other Customers, the specific End User, Customer or workspace that contributed a given signal. The Profiles Database is a shared SalesQL resource; contributions are not exposed back to other Customers as attributed contributions.

#6. Safeguards

The Program is operated under the following safeguards:

  • Data minimisation: signals incorporated into the Profiles Database are filtered to professional-context categories only. Special categories (Article 9 UK/EU GDPR), Article 10 data, and the categories listed under Privacy Policy Section 3.4 (“We do not collect or maintain”) are excluded.
  • Suppression list: the Program respects the SalesQL suppression list. Signals that would update or revive a record subject to a suppression entry are discarded. The suppression mechanism is described in Section 11 of the Privacy Policy.
  • Data-subject rights: Business Contacts whose data is updated through Program signals retain all the rights described in Sections 10 and 11 of the Privacy Policy, including the unconditional right to be removed from the Profiles Database, exercised through the SalesQL Privacy Center.
  • Article 19 UK/EU GDPR notification: where a Business Contact’s Profile Data has been disclosed to Customers and is then erased through a suppression request, SalesQL notifies those Customers so they can update their own records, unless this proves impossible or involves disproportionate effort.
  • Withdrawal of contribution: a Customer or End User who no longer wishes to contribute can stop generating signals by uninstalling the browser extension.
  • Respect for third-party site terms: the browser extension is designed to operate alongside the End User’s own authenticated session on supported professional networking sites; it does not bypass any third-party authentication or anti-bot mechanism.
  • Subprocessor controls: the Program operates within the same security and Subprocessor framework that applies to all of the Services. See the Subprocessors page and the DPA Annex 2 (Technical and Organisational Measures).

#7. Customer obligations under the Program

Without limiting the obligations in the Terms of Service and the AUP, when a Customer or its End Users participate in the Program, the Customer:

(a) acknowledges and accepts that the use of the browser extension generates signals that maintain the Profiles Database, and accepts the framing in this document;

(b) does not use technical means to evade, intercept, manipulate or falsify the signals (no fake browsing automation, no synthetic traffic, no spoofed observations), as further specified in AUP Section 7;

(c) does not represent to data subjects that the Customer is not contributing signals to SalesQL when the Customer is in fact using the browser extension;

(d) ensures that End Users authorised to use the browser extension in the Customer’s workspace are aware of, and bound by, terms no less protective than these Contributor Program Terms;

(e) complies with the third-party terms of any platform on which the browser extension is used, and does not misuse the extension to access content the End User is not authorised to access (Browser Extension Notice, Section 8).

Failure to comply with this Section 7 is a material breach of the Terms of Service and may result in suspension or termination of the Account, in addition to SalesQL’s other remedies.

#8. Business Contacts — your rights

If you are a Business Contact whose data may have entered the SalesQL Profiles Database through the Program, you have the unconditional right to:

  • Be removed from the Profiles Database (suppression / opt-out) — public, self-service form on the Privacy Center with email verification.
  • Request a copy of the data SalesQL holds about you (Article 15 UK/EU GDPR; CCPA “right to know”) through the Privacy Center.
  • Request erasure beyond suppression (Article 17 UK/EU GDPR) through the Privacy Center.
  • Object to processing based on legitimate interests, including the processing performed under the Program (Article 21 UK/EU GDPR). This is functionally equivalent to suppression.
  • Lodge a complaint with a supervisory authority (Article 77 UK/EU GDPR), including the UK Information Commissioner’s Office (ICO).

The detailed framework for exercising these rights is in Privacy Policy Sections 10 and 11.

#9. Changes to these Terms

SalesQL may update these Contributor Program Terms from time to time. Material updates will be communicated through the Services or by email. Continued use of the browser extension after the effective date of an update constitutes acceptance of the updated Terms.

Where a change to these Terms reflects a substantive change to how the Program operates (for example, a new category of signals, a change in the scope of the observations, or a new Subprocessor processing Program signals), SalesQL will both update this document and reflect the change in the Privacy Policy and the Subprocessors page. The three documents are designed to be consistent.

#10. Contact

For questions about the Contributor Program:

  • Privacy and data-subject rights — privacy@salesql.com or the SalesQL Privacy Center.
  • Other questions — legal@salesql.com.
  • Postal — SALESQL LTD, 71-75 Shelton Street, London, WC2H 9JQ, United Kingdom.
  • EU/Swiss Representative — GDPR Local (https://gdprlocal.com).
Back to Privacy Center

Questions?legal@salesql.com·privacy@salesql.com

Other legal documents

Privacy PolicyCookie PolicyTerms of ServiceData Processing AddendumAcceptable Use PolicySubprocessors
© 2020–2026 SalesQL Ltd PrivacyTermsCookiesPrivacy Center