Data Processing Agreement

Data Processing
Agreement.

This Data Processing Agreement ("DPA") is incorporated by reference into the Terms of Service and the API Terms for every customer that sends PLLAY personal data about its end users. A signed DPA is available on request at privacy@pllay.io.

Version 1.4 · Effective date: November 3, 2026.

1. Roles

For personal data in data a customer submits ("Customer Data"), the customer is the controller (or a processor acting for its own controller) and PLLAY is its processor and, under US state privacy laws, its service provider. For account data, PLLAY is an independent controller.

PLLAY will not sell or share Customer Data; will not retain, use or disclose it outside the direct business relationship or for any purpose other than those in this DPA; and will not combine it with other personal data except as the law permits.

2. What we process and why

  • Data. Clips and frames, event data and outcomes, evidence frames and records, receipts, and API logs (including the caller IP address).
  • People. The customer’s end users who appear in or are named in that data.
  • Purpose. Verifying outcomes, issuing receipts, handling holds, reviews and disputes, and securing the Service.
  • Instructions. We process Customer Data only on the customer’s documented instructions, including this DPA and the customer’s API calls, and will tell the customer if we believe an instruction breaks the law.
  • Confidentiality. Everyone at PLLAY who can access Customer Data is bound by confidentiality obligations.

3. Sub-processors

The customer authorises the sub-processors on PLLAY's current sub-processor list, available on request at privacy@pllay.io. PLLAY has a written agreement with each that imposes data-protection obligations no less protective than this DPA, and remains responsible for their performance.

We will give at least 30 days’ notice of a new or replacement sub-processor by email to the contact email on the customer’s account. A customer may object on reasonable data-protection grounds within that period; if we cannot address the objection, the customer may end the affected service and receive a refund of prepaid fees for it.

4. International transfers

Data is processed in the United States. Transfers from the EEA, UK and Switzerland are governed by the Standard Contractual Clauses (Module 2 or 3 as applicable), the UK International Data Transfer Addendum and the Swiss amendments, which are incorporated by reference.

5. Security

PLLAY maintains technical and organisational measures appropriate to the risk to Customer Data. Measures in place today include:

  • Storage. Evidence frames are kept in a private storage bucket. Working frames are deleted when each job finishes.
  • Integrity. Evidence records are signed with HMAC-SHA256 and record the ID of the signing key, so keys can be rotated and older records still checked. Signing keys can be read only by the database owner, not by any API role. Receipts carry SHA-256 hashes, and only hashes leave the database if a receipt is anchored.
  • API keys. API keys are scoped to the routes they may call, stored only as SHA-256 hashes, and can be rotated or revoked at any time. Sandbox keys work only against the sandbox.
  • Abuse controls. API calls are rate-limited and support idempotency keys, so a retried request cannot create or settle a result twice.
  • Production access. Production keys are issued only after a person at PLLAY approves a production-access request following a manual business review.
  • People and access. Access to Customer Data is limited to personnel who need it to provide the Service, each bound by confidentiality obligations (Section 2).

PLLAY may update these measures over time, provided the overall level of protection is not reduced. Customers may report suspected security issues to security@pllay.io.

6. Retention

Raw clips and video are deleted within 90 days of the job unless the customer asks otherwise. Evidence frames and records are kept while the customer’s agreement is active and up to 6 years after for dispute and audit purposes. API request logs are kept up to 12 months.

7. Deletion and return

When the agreement ends, we delete or return Customer Data within 90 days, at the customer’s choice, unless the law requires us to keep it, in which case it stays protected under this DPA.

8. Breach notice

PLLAY will notify the customer without undue delay, and in any case within 72 hours, after becoming aware of a personal data breach affecting Customer Data, and will provide the information reasonably available to help the customer meet its own obligations. Notification is not an acknowledgement of fault or liability.

9. Assistance and audits

We will help customers answer data subject requests and complete impact assessments, and make available the information needed to show compliance. Once a year, on 30 days’ notice, a customer may audit our compliance by questionnaire or, where the law requires, by an independent auditor under confidentiality, at the customer’s cost.

10. Order of precedence

If this DPA conflicts with the Terms of Service or the API Terms, this DPA controls for Customer Data. If it conflicts with the Standard Contractual Clauses, the Clauses control.