Data Processing Addendum
Last updated November 17, 2026. A simple DPA for builders using Saidloop (saidloop.com) with end-user personal data. Not legal advice.
This Data Processing Addendum ("DPA") forms part of the Terms of Service between you ("Customer", controller) and Saidloop ("Processor") when Saidloop processes personal data on your behalf in providing the service. For a countersigned PDF or custom terms, email business@xerv-project.id.
1. Roles
Customer determines the purposes and means of processing personal data in feedback reports and related content. Saidloop processes that data only to provide the Saidloop service as described in the Terms and this DPA, and on documented instructions from Customer (including configuration in the product).
2. Details of processing
- Subject matter — hosting and processing feedback reports, screenshots / UI context, optional reporter identifiers, and project metadata
- Duration — for the term of the agreement and retention periods in the Privacy Policy (including ~30 days after project deletion from active systems)
- Nature and purpose — store, display, notify, and expose data to agents Customer connects (e.g. MCP) so Customer can triage and close feedback
- Types of data — may include names, emails, user ids, device/app metadata, message content, and images of product UI
- Data subjects — Customer's end users and other individuals whose data appears in reports
3. Processor obligations
Saidloop will:
- Process personal data only on Customer's documented instructions
- Ensure persons authorized to process data are bound by confidentiality
- Implement appropriate technical and organizational security measures
- Assist Customer, taking into account the nature of processing, with data subject requests and DPIA-related information reasonably available to us
- Notify Customer without undue delay after becoming aware of a personal data breach affecting Customer data
- Delete or return Customer personal data after the end of the service relationship, subject to legal retention and backup cycles
- Make available information reasonably necessary to demonstrate compliance with this DPA and allow audits as mutually agreed in writing (remote questionnaires preferred)
4. Customer obligations
Customer is responsible for lawful collection of end-user data, notices and consents, configuring client-side masking, and not instructing Saidloop to process data unlawfully. Customer must not submit special-category data unless the parties agree in writing.
5. Subprocessors
Customer authorizes Saidloop to use subprocessors for infrastructure, email, storage, and similar functions. Saidloop remains responsible for subprocessors and will impose data protection terms no less protective than this DPA. A current list is available on request at business@xerv-project.id. Material changes will be communicated with a reasonable objection window where required by law.
6. International transfers
Where Saidloop transfers personal data from the EEA/UK/Switzerland to a country without an adequacy decision, Saidloop will use appropriate safeguards (such as Standard Contractual Clauses) or another lawful transfer mechanism.
7. Liability
Liability under this DPA is subject to the limitations in the Terms, except where prohibited by applicable data protection law.
8. Order of precedence
If this DPA conflicts with the Terms regarding data protection, this DPA controls. By using Saidloop to process personal data of end users, Customer agrees to this DPA.
Contact
Saidloop · business@xerv-project.id · Contact.