Legal
Data processing addendum
How DataBroker handles personal information that data owners supply and that brokers store in their workspaces.
Updated
1. What this addendum covers
This addendum forms part of each agreement between DataBroker LLC (“DataBroker”) and a customer under which DataBroker handles Personal Information for that customer: the Data supply agreement with a Data Owner, and the Terms of service with a Broker or a Broker's organization (each a “Customer”). If this addendum conflicts with that agreement on Personal Information, this addendum wins.
2. Words with a set meaning
- Data Protection Law: every privacy and data protection law that applies to the processing, including the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection, and U.S. state laws such as the California Consumer Privacy Act.
- Personal Information, controller, processor, data subject and processing have the meanings given in Data Protection Law (for U.S. law, “business” and “service provider” correspond to controller and processor).
- Customer Personal Information: Personal Information that DataBroker processes for the Customer under the agreement, as described in Annex 1.
- Subprocessor: a third party DataBroker engages to process Customer Personal Information.
- Security Incident: a breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Information.
3. Who is responsible for what
3.1 Preparing supplied data. When DataBroker stores, checks, cleans and de-identifies data a Data Owner supplies, to bring it to the Release Standard and prepare Samples, the Data Owner is the controller (or a processor acting for its own customer) and DataBroker is its processor.
3.2 Licensing to Buyers. Supplied data released to Buyers should meet the Release Standard and, where that standard is “no Personal Information”, contain none. If released data still contains Personal Information because the Dataset Schedule allows it, DataBroker and each Buyer act as independent controllers for their own use of it, and each is responsible for its own compliance.
3.3 Broker workspaces. For Personal Information a Broker or its organization puts into its workspace (such as lead and contact details, notes and contracts), the Broker's organization is the controller and DataBroker is its processor. DataBroker is a controller for account, billing and usage information about Brokers themselves, which the Privacy policy covers.
3.4 Customer duties. The Customer is responsible for having a lawful basis for the processing, for giving notices and obtaining consents, for the accuracy of Customer Personal Information, and, where it acts for another controller, for that controller's authorization and for passing on DataBroker's notices. The Customer will not give DataBroker the restricted categories listed in section 8 of the data supply agreement unless the Dataset Schedule expressly permits them.
4. Processing only on instructions
As a processor, DataBroker processes Customer Personal Information only on the Customer's documented instructions. The agreement, the Dataset Schedule (including its Release Standard), this addendum and the Customer's use of the app's features are those instructions. DataBroker will tell the Customer if it believes an instruction breaks Data Protection Law, and may then suspend that processing. DataBroker may also process Customer Personal Information where the law requires it, after telling the Customer unless the law forbids that.
As a service provider under U.S. state law, DataBroker will not sell or share Customer Personal Information, retain, use or disclose it outside the direct business relationship with the Customer or for any purpose other than the agreement, or combine it with Personal Information from other sources except as Data Protection Law permits. DataBroker will tell the Customer if it can no longer meet these duties.
5. People and confidentiality
DataBroker gives access to Customer Personal Information only to staff and contractors who need it for the agreement and who are bound to keep it confidential, and trains them on handling it.
6. Security
DataBroker keeps technical and organizational measures appropriate to the risk, taking into account the nature of the data and the state of the art, including at least those in Annex 2. DataBroker may change them, as long as the overall level of protection does not decrease.
7. Subprocessors
The Customer gives DataBroker general authorization to use the Subprocessors in Annex 3, and the Marketplaces through which DataBroker sells supplied data, for the purposes listed there. DataBroker binds each Subprocessor by written terms that protect Customer Personal Information at least as well as this addendum, and stays responsible for it.
DataBroker posts every change to the list in the Subprocessors section of the privacy policy, and gives Customers whose Personal Information the Service processes at least 15 days' notice by email before a new Subprocessor starts processing it. The Customer may object on reasonable data protection grounds within that time. The two sides will then discuss a solution in good faith; if there is none, the Customer may end the affected part of the agreement, with a refund of any prepaid fees for the unused period.
8. Security Incidents
DataBroker will notify the Customer without undue delay, and in any case within 48 hours, after becoming aware of a Security Incident. The notice will describe, as far as then known, what happened, the categories and approximate numbers of people and records involved, the likely consequences, and what DataBroker is doing about it, and DataBroker will add details as it learns them. DataBroker will take reasonable steps to contain the incident and limit the harm, and help the Customer meet its own duties to notify regulators and people affected. A notice is not an admission of fault.
9. International transfers
DataBroker is based in the United States, and Customer Personal Information may be processed there and wherever its Subprocessors operate. Where Data Protection Law restricts a transfer, the transfer is made under the European Commission's Standard Contractual Clauses (Module 2 where the Customer is a controller, Module 3 where it is a processor), with the UK International Data Transfer Addendum and the Swiss amendments where those laws apply, which are incorporated by reference, with the Customer as data exporter and DataBroker as data importer. For the Standard Contractual Clauses: the optional docking clause (clause 7) applies; under clause 9, option 2 (general authorization) applies, with notice of changes as in section 7 of this addendum; the optional wording in clause 11 does not apply; the competent supervisory authority under clause 13 is the one for the EU member state where the Customer is established or, if it is not established in the EU, where its EU representative is, and otherwise Ireland's; and the clauses are governed by Irish law and disputes about them go to the courts of Ireland (clauses 17 and 18). Annex 1 of this addendum gives the description of the transfer, Annex 2 the security measures and Annex 3 the Subprocessors. For the UK, the UK Addendum's tables are completed with the same information, and either side may end it as its section 19 allows. For Switzerland, the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority, references to the GDPR include the Swiss Federal Act on Data Protection, and the term “member state” does not prevent people in Switzerland from bringing claims where they usually live. If an adequacy decision or certification framework covers a transfer, DataBroker may rely on it instead.
10. Helping the Customer
Taking into account the nature of the processing, DataBroker will help the Customer, by appropriate technical and organizational means, to answer requests from people exercising their rights, and with security, incident notification, data protection impact assessments and prior consultations with regulators. If DataBroker receives a request directly from a person about Customer Personal Information, it will pass it to the Customer and not answer it itself unless the Customer asks or the law requires.
11. Return and deletion
When the agreement ends, or earlier if the Customer asks, DataBroker will delete Customer Personal Information without undue delay, within the periods set in the agreement (for Broker workspaces, as the Terms of service and the Privacy policy describe), or return it first if the Customer asks within 30 days of the end. DataBroker may keep copies the law requires it to keep, copies in backups until they expire, and, for supplied data, copies needed to support Buyer Licenses that continue under the data supply agreement, all of which stay protected by this addendum.
12. Records and audits
DataBroker will make available the information reasonably needed to show that it meets this addendum, such as answers to a security questionnaire and any third-party audit reports it holds. If that is not enough, or a regulator requires it, the Customer may audit DataBroker once a year, on at least 30 days' notice, during business hours, through an auditor bound by confidentiality who is not a competitor of DataBroker, at the Customer's cost, and in a way that does not disrupt DataBroker or expose other customers' information.
13. De-identified data
Where DataBroker de-identifies data, it will keep it in de-identified form, take reasonable measures against re-identification, not attempt to re-identify it, and require Buyers to promise the same. No method can guarantee that re-identification is impossible, and DataBroker does not promise that it is.
14. Liability and term
Each side's liability under this addendum is governed by the limits and exclusions in the agreement it forms part of. The Data Owner's responsibility for processing done on its instructions, including releases at the Release Standard it chose, is covered by its indemnity in the data supply agreement. Disputes under this addendum are governed by the law, and resolved under the dispute resolution terms (including arbitration), of the agreement it forms part of, except where the Standard Contractual Clauses require otherwise. This addendum lasts as long as DataBroker processes Customer Personal Information. Notices go as that agreement provides; notices to DataBroker go to team@data.broker.
Annex 1: Description of the processing
Supplied data (section 3.1). Data subjects: as described in the Dataset Schedule, typically the Data Owner's customers, users, employees or the people its data concerns. Personal Information: as described in the Dataset Schedule. Purposes: storing, checking, cleaning, de-identifying and preparing Samples, to license the data under the data supply agreement. Duration: the term of the Dataset Schedule and section 11.
Broker workspaces (section 3.3). Data subjects: business contacts and prospects of the Broker, and people named in its notes, files and contracts. Personal Information: names, job titles, employers, business email addresses and phone numbers, public profile links, correspondence and notes. Purposes: providing the app's research, CRM, contract and listing features to the Broker. Duration: while the Broker's account is open, and section 11.
Frequency: continuous. Special categories: none, unless a Dataset Schedule expressly permits them with added safeguards.
Annex 2: Security measures
- Encryption of data in transit (TLS) and at rest through our hosting providers.
- Separation of each organization's workspace by access rules enforced in the database.
- Access for staff on a need-to-know basis, with single sign-on and multi-factor authentication where available.
- Secrets kept in managed environment settings, never in code; keys rotated when staff leave or exposure is suspected.
- Logging of access to production systems, and review of unusual activity.
- Checks of supplied files for credentials, malware and Personal Information before release, using automated tools where they are available.
- Regular backups held by our database provider, with restore tested.
- Prompt patching of dependencies with known vulnerabilities.
- Due diligence on Subprocessors' security before use.
- A written incident response process.
Annex 3: Subprocessors
The Subprocessors are those listed, with what each does and where, in the Subprocessors section of the privacy policy, as updated under section 7, together with the data marketplaces DataBroker chooses for a dataset, which list it and deliver it to Buyers.