Data Processing Addendum
Last updated 3 November 2026
This addendum applies automatically when you accept our Terms of Service. It covers personal data inside the files you upload. You don't need to sign anything. If your company needs a countersigned copy, email hello@pipeyield.com.
1. Parties and roles
This addendum is between the customer that accepted the Terms ("you", the controller) and the individual business owner operating Pipeyield ("we", the processor).
"Data protection law" means every law that applies to the processing, including the EU GDPR, the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, the Saudi Personal Data Protection Law, and US state privacy laws such as the CCPA. Terms like "personal data", "processing" and "data subject" have the meanings given in those laws.
"Customer personal data" means personal data in files you upload to Pipeyield. Annex 1 describes it.
2. Processing only on your instructions
- We process customer personal data only to provide the service, as described in the Terms and this addendum. These are your documented instructions. Further instructions must be in writing and consistent with the service.
- We tell you if we think an instruction breaks data protection law.
- If the law requires us to process data in another way, we tell you first, unless the law forbids it.
- You confirm that you have a lawful basis for the data you upload and that you have given any notices it requires.
3. Confidentiality
Only people who need access to provide the service can access customer personal data, and they are bound by confidentiality.
4. Security
We use appropriate technical and organisational measures to protect customer personal data, set out in Annex 2. We may update them as long as protection does not decrease.
5. Subprocessors
- You authorise us to use the subprocessors listed in our Privacy Policy.
- We'll email you at least 30 days before we add or replace a subprocessor. If you object on reasonable data-protection grounds and we can't address your concern, you may cancel and receive a refund of any prepaid, unused period.
- Each subprocessor is bound by a written contract with data protection obligations no less protective than this addendum. We remain responsible for our subprocessors.
6. Assistance
- If a data subject contacts us directly, we forward the request to you and don't answer it ourselves unless you ask.
- We help you, as far as reasonably possible, to answer data subject requests and to carry out data protection impact assessments and consultations with authorities.
7. Breach notification
We notify you without undue delay, and in any case within 48 hours, after we become aware of a personal data breach affecting customer personal data. We share what we know, what we are doing about it, and updates as we learn more.
8. Deletion
We delete raw uploaded files within 7 days of the report they were used for. When your subscription ends, we delete remaining customer personal data within 30 days, unless the law requires us to keep it. For free partner accounts, we delete it within 30 days after the last upload. Deleted data leaves our encrypted backups within a further 7 days. You can download your reports before your subscription ends.
9. Information and audits
On request, we give you the information you reasonably need to show compliance with this addendum, including answers to security questionnaires once a year. If that isn't enough, or an authority requires it, you may audit our compliance once a year, at your cost, with 30 days' notice, during business hours and under confidentiality.
10. International transfers
Customer personal data is stored in Germany (AWS, Frankfurt). We operate from Saudi Arabia, and some subprocessors (email, payments, AI) are in the United States.
- EEA: where customer personal data is transferred from the EEA to us, the Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914, Module Two (controller to processor), are incorporated into this addendum by reference. You are the data exporter and we are the data importer.
- Choices under the clauses: Clause 7 (docking) does not apply. For Clause 9, option 2 (general written authorisation) applies, with the notice period in section 5. The optional wording in Clause 11 does not apply. For Clauses 17 and 18, the law and courts of Ireland apply. For Clause 13, the supervisory authority is the one competent for you under the GDPR. Annexes I and II of the clauses are filled in by Annexes 1 and 2 below, and Annex III by our subprocessor list.
- UK: for transfers from the UK, the International Data Transfer Addendum issued by the UK Information Commissioner applies on top of those clauses, using the details in this addendum. Either party may end it as allowed by its Section 19.
- Switzerland: the same clauses apply, with the Swiss Federal Data Protection and Information Commissioner as competent authority and references to the GDPR read as references to Swiss law.
- Onward transfers: our transfers to subprocessors are covered by their own Standard Contractual Clauses or EU-US Data Privacy Framework certification.
If these clauses conflict with the rest of this addendum or the Terms, the clauses win.
11. US state privacy laws
Where the CCPA or similar US laws apply, we act as your service provider or processor. We don't sell or share customer personal data, and we don't keep, use or disclose it for any purpose other than providing the service, or outside our direct business relationship with you. We don't combine it with personal data from other sources except as those laws allow. We tell you if we can no longer meet these obligations.
12. General
This addendum lasts as long as we process customer personal data for you. The liability limits in the Terms apply to it, as far as the law allows. If this addendum conflicts with the Terms, this addendum wins on data protection matters.
Annex 1: Details of processing
| Subject matter and purpose | Matching ad clicks to CRM lead outcomes to report which keywords and search terms produce qualified leads, grouping lead rejection reasons, and labelling search terms by likely intent |
|---|---|
| Nature of processing | Storage, matching, aggregation, analysis and deletion |
| Duration | The subscription term, plus the deletion periods in section 8 |
| Frequency | Each time you upload files |
| Data subjects | Your leads and prospects; your staff named as lead owners, if included |
| Personal data | Click identifiers (GCLID), lead or deal status, lifecycle stage, dates, campaign and keyword fields, free-text rejection reasons. Names, emails and phone numbers should be removed before upload; if they are present, they are processed only as part of the file and deleted on the same schedule. |
| Sensitive data | None. You must not upload special-category or sensitive data. |
| Exporter | You, the customer, as identified at checkout. Role: controller. |
| Importer | The operator of Pipeyield, Saudi Arabia, hello@pipeyield.com. Full details on request. Role: processor. |
Annex 2: Security measures
- Encryption: HTTPS (TLS 1.2 or higher) for all traffic; encrypted database and disks at rest.
- Backups: encrypted daily database backups kept for 7 days, so deleted data also leaves backups within a further 7 days.
- Access control: access limited to the operator; unique accounts; two-factor authentication on every admin and provider account.
- Data minimisation: an export guide that tells you which columns to remove; only the rejection-reason text and the search terms are sent to the AI provider, without names, contact details or spend, and the provider may not train on them.
- Separation: each customer's files are stored under their own account and never mixed.
- Retention: automatic deletion of raw files within 7 days.
- No account access: we never ask for logins to your Google Ads or CRM accounts.
- Devices: full-disk encryption and automatic screen lock on the devices used to run the service.
- Incidents: a documented breach process with notice within 48 hours (section 7).