1. Scope and precedence
This Data Processing Addendum (“DPA”) forms part of the Terms of Service between you (“Customer”) and Program Alpha, Inc. (“PrimaryAPI”). It applies whenever PrimaryAPI processes Customer Personal Data in providing the Service. It takes effect automatically when you accept the Terms; no signature is needed.
If this DPA conflicts with the Terms on a data protection matter, this DPA wins. If it conflicts with the Standard Contractual Clauses, the Clauses win.
2. Definitions
- Data Protection Laws means the laws that apply to the processing, including the EU GDPR, the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection and US state privacy laws such as the California Consumer Privacy Act (CCPA).
- Customer Personal Data means personal data contained in the inputs Customer sends to the Service and the results returned to Customer.
- Controller, processor, data subject, personal data breach and processing have the meanings given in the GDPR. Sub-processor means a third party we engage to process Customer Personal Data.
- Standard Contractual Clauses or SCCs means the clauses approved by the European Commission in Decision (EU) 2021/914.
3. Roles of the parties
For Customer Personal Data, Customer is the controller (or a processor acting for its own customer) and PrimaryAPI is the processor (or sub-processor). Customer decides what to look up, for what purpose, and what happens to the results.
PrimaryAPI is a controller for account, billing, usage and security data about Customer and its users. That processing is described in the Privacy Policy and is not covered by this DPA.
Customer is responsible for having a lawful basis for its processing, for giving data subjects the notices the law requires and for following the Acceptable Use Policy.
4. Processing on documented instructions
We process Customer Personal Data only on Customer’s documented instructions. Customer’s instructions are the Terms, this DPA, the API calls Customer or its agents make, and the settings Customer chooses in the dashboard (for example, key limits). We will tell Customer if we believe an instruction breaks Data Protection Laws.
We will not:
- use Customer Personal Data for our own purposes, other than as needed to provide, secure and bill for the Service;
- combine it with personal data from other customers, or use it to build a database of people; or
- sell it, or share it for cross-context behavioural advertising.
5. Details of the processing
| Subject matter | Running API lookups, searches, validation and enrichment calls that Customer sends to the Service. |
|---|---|
| Duration | For the term of the Terms of Service, and afterwards until deletion as described in this DPA. |
| Nature and purpose | Receiving inputs, passing the parameters each call needs to the provider that serves it, returning results to Customer, keeping results for the retention window so Customer can read them again, and keeping request records for billing and support. |
| Data subjects | People whose identifiers or public information Customer chooses to look up or validate, such as owners of public social media profiles, authors of public posts and reviews, business contacts and people whose email addresses or phone numbers Customer validates. |
| Categories of personal data | Identifiers in inputs (usernames, profile URLs, email addresses, phone numbers, names, domains) and public information in results (public profile details, public posts and comments, business contact details, validation outcomes). |
| Special categories | Not intended. The Acceptable Use Policy forbids using the Service to infer special-category data. Public content may incidentally reveal such data; Customer must not process it for that purpose. |
6. Confidentiality
We ensure that anyone we authorise to process Customer Personal Data is bound by an obligation of confidentiality and has access only to what their role needs.
7. Security measures
We implement appropriate technical and organisational measures to protect Customer Personal Data, taking into account the risks of the processing. The measures in place today are listed in Annex A. We may update them as long as the overall level of protection does not decrease.
8. Sub-processors
Customer gives general authorisation for us to engage sub-processors in the categories listed in Annex B. We impose data protection obligations on each sub-processor that are no less protective than this DPA, and we remain responsible for their performance.
- The current list of named sub-processors, with their purpose and location, is available on request from [email protected].
- We will give at least 30 days’ notice before a new sub-processor starts processing Customer Personal Data. Customer may object on reasonable data protection grounds; if we cannot address the objection, Customer may stop using the affected APIs or close its account and receive a refund of unused bought credits.
9. Requests from data subjects
If we receive a request from a data subject about Customer Personal Data, we will not answer it ourselves except to confirm receipt; we will forward it to Customer where our records identify Customer. Taking into account the nature of the processing, we will help Customer respond to requests to exercise data subject rights, including by deleting stored results on request.
10. Personal data breaches
We will notify Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data. The notice will describe, as far as we know at the time, the nature of the breach, the data and data subjects concerned, the likely consequences and the steps taken or proposed. We will update Customer as we learn more.
Notifying Customer of a breach is not an admission of fault or liability.
11. Impact assessments and consultations
Taking into account the nature of the processing and the information available to us, we will give Customer reasonable help with data protection impact assessments and prior consultations with supervisory authorities that relate to Customer’s use of the Service.
12. Deletion and return
- Full results are deleted automatically when the retention window ends (24 hours by default).
- Inputs to restricted APIs are never stored in readable form; only a hash is kept.
- When the Terms end, we delete remaining Customer Personal Data within 30 days, unless the law requires us to keep it. Before closing its account, Customer can read its request history in the dashboard or through the requests endpoint of the API.
13. Audits and information
We will make available the information reasonably needed to demonstrate compliance with this DPA, including written answers to security questionnaires. Where that is not enough to meet a requirement of Data Protection Laws, Customer may audit our compliance on at least 30 days’ written notice, at its own cost, no more than once a year, in a way that does not disrupt the Service or expose other customers’ data.
14. International transfers
We may process Customer Personal Data outside the country where it was collected, including in the United States. Where Data Protection Laws require a transfer mechanism:
- for transfers from the EU/EEA, the SCCs apply, Module 2 (controller to processor) or Module 3 (processor to processor) as appropriate, with the optional docking clause, Clause 9 option 2 (general authorisation) and Clause 11’s optional language omitted;
- for transfers from the UK, the SCCs apply as amended by the UK International Data Transfer Addendum;
- for transfers from Switzerland, the SCCs apply with the adjustments the Swiss Federal Act on Data Protection requires.
The details of the processing above complete Annex I of the SCCs, Annex A completes Annex II, and the SCCs are governed by the law of Ireland, with disputes resolved by the courts of Ireland.
15. US state privacy laws
Where the CCPA or a similar US state law applies, we act as Customer’s service provider or processor. We will not sell or share Customer Personal Data; retain, use or disclose it for any purpose other than providing the Service; use it outside our direct business relationship with Customer; or combine it with personal data we receive from others, except as those laws allow.
We will comply with the obligations those laws place on us, provide the same level of privacy protection they require, and tell Customer if we can no longer meet them. Customer may take reasonable steps to stop unauthorised use.
16. Liability
Each party’s liability under this DPA is subject to the limitations in the Terms of Service, except where Data Protection Laws or the SCCs do not allow liability to be limited.
17. Annex A: Security measures
Credentials and access
- API keys, session tokens and email verification and reset tokens are stored only as SHA-256 hashes; keys are shown once.
- Passwords are hashed with argon2id; sign-in checks take the same work whether or not the account exists.
- Keys carry an access level (full, run or view), and can have a spend limit, an expiry date, and be rotated or revoked at any time.
- Session cookies are HTTP-only and SameSite=Lax; cookie-authenticated changes must come from our own origin.
- Key creation, rotation, revocation and agent approvals are written to an audit log.
Data minimisation and retention
- Providers receive only the parameters a call needs and our credentials, never Customer’s identity.
- Full results are purged at the end of the retention window; restricted-API inputs are kept only as a hash.
- No shared response cache across customers.
- Card details are entered on the payment processor’s hosted page and never reach our servers.
Network and application
- The website and API are served over HTTPS.
- Requests to customer-supplied URLs pass a server-side request forgery guard that blocks private, loopback, link-local and cloud metadata addresses, re-checks every redirect and caps response size and time.
- Inputs are validated against strict schemas; unknown fields are rejected and request bodies are limited to 2 MB.
- Rate limits apply per key and per account.
- Secrets are never written to logs; keys are identified in logs by their prefix only.
18. Annex B: Sub-processor categories
| Category | Purpose | Data involved |
|---|---|---|
| Cloud hosting and database | Running the Service and storing its data | All Service data, including inputs, results and request records |
| Network and security | Delivering the website and API and protecting them from attacks | Requests and responses in transit, including IP addresses |
| Payment processing | Credit purchases, plan payments, refunds and disputes | Customer billing data only; no Customer Personal Data from lookups |
| Email delivery | Sign-in, verification and account emails | Customer contact details only |
| Upstream data providers | Serving the API calls routed to them | The parameters of each call they serve and the results they return |
- Cloud hosting and database
- Purpose: Running the Service and storing its data
- Data involved: All Service data, including inputs, results and request records
- Network and security
- Purpose: Delivering the website and API and protecting them from attacks
- Data involved: Requests and responses in transit, including IP addresses
- Payment processing
- Purpose: Credit purchases, plan payments, refunds and disputes
- Data involved: Customer billing data only; no Customer Personal Data from lookups
- Email delivery
- Purpose: Sign-in, verification and account emails
- Data involved: Customer contact details only
- Upstream data providers
- Purpose: Serving the API calls routed to them
- Data involved: The parameters of each call they serve and the results they return