This addendum forms part of the Terms of Service between Media Yard LLC ("Processor") and the customer ("Controller") whenever FastDAR processes personal data on the customer's behalf that is subject to the GDPR, UK GDPR or similar law. Customers accept it by using the service; if you need a signed copy, email [email protected].
1. What is processed
| Subject matter | Checking, labelling and sorting the texts the customer sends, and running any invitation-only public-post searches it sets up |
| Duration | The term of the agreement, then deletion as in section 8 |
| Nature and purpose | Reading and scoring texts and returning answers; for searches, also collecting, storing, delivering and deleting posts |
| Data subjects | People who write or are named in the texts the customer sends (for example its customers in support tickets); authors of public posts found by the customer's searches; the customer's staff |
| Personal data | Whatever the customer's texts contain; public usernames, post text and links; staff names and emails |
| Special categories | Only if the customer's texts or a public post contain them; customers must not send them without a lawful basis or use the service to target them |
For posts, Media Yard LLC also acts as an independent controller for running and securing the service and the retention schedule in our Privacy notice.
2. Processor's duties
- Process personal data only on the Controller's documented instructions (these terms and the Controller's settings), unless the law requires otherwise, and say so if an instruction seems to break the law.
- Make sure everyone with access is bound by confidentiality.
- Apply the security measures in section 9.
- Help the Controller answer data subject requests, carry out impact assessments and consult authorities, as far as the nature of the processing allows.
- Make available the information needed to show compliance with this addendum, and allow audits by the Controller or its auditor on 30 days' notice, no more than once a year, unless a breach or an authority requires more.
3. Subprocessors
The Controller authorises the service providers listed in section 5 of our Privacy notice. We'll announce new ones there and by email at least 30 days before they start. The Controller may object on reasonable data protection grounds; if we can't resolve it, the Controller may end the affected service and get a pro-rata refund. We bind each subprocessor to data protection terms at least as protective as these, and remain responsible for them.
4. Personal data breaches
We'll notify the Controller without undue delay, and within 48 hours of becoming aware of a breach affecting its data, with what we know and what we're doing, and keep it updated.
5. International transfers
Where personal data leaves the EEA, UK or Switzerland for a country without an adequacy decision, the parties agree to the EU Standard Contractual Clauses (Commission Decision 2021/914), Module 2 (controller to processor) and, where relevant, Module 3, incorporated by reference: clause 7 applies; in clause 9 option 2 with the notice period in section 3; clause 11's optional wording does not apply; clauses 17 and 18 choose Ireland. For UK data the UK International Data Transfer Addendum applies, with the parties' details as above; for Swiss data, the Swiss FDPIC is the competent authority and references to the GDPR include the Swiss FADP.
6. Controller's duties
The Controller is responsible for having a lawful basis for the texts it sends and any searches it runs, for how it uses the answers, and for its settings.
7. Liability
Each party's liability under this addendum is subject to the limits in the Terms, except where the law or the Standard Contractual Clauses don't allow it.
8. Deletion
Texts sent for checking are not stored, except examples and corrections the Controller saves in a label set. When the Controller deletes a search or erases its account, we delete the related personal data within 30 days (including backups within their normal cycle), except billing records the law requires us to keep.
9. Security measures (Annex II)
- Encryption in transit (TLS) for all connections to the service and to providers.
- API keys stored only as one-way SHA-256 fingerprints; CRM tokens never returned in full; sign-in links are long random tokens.
- Access to production limited to named staff with strong authentication; least privilege.
- Automatic deletion on the retention schedule; deletion on request.
- Rate limits, abuse limits and blocking of requests to private networks from customer-supplied URLs.
- Encrypted backups.
- Changes reviewed and tested before release.
10. Order of precedence
If this addendum conflicts with the Terms, this addendum wins; if either conflicts with the Standard Contractual Clauses, the Clauses win.