Last updated 15 November 2026
This data processing agreement is part of the terms of service between Digital Sphinx Creations AB (company number 559458-1398), Arlavägen 3, SE-511 72 Fritsla, Sweden ("Reytd", the processor) and the business that uses Reytd (the controller). It covers the personal data Reytd handles for the controller, as article 28 of the GDPR requires. It applies from when the controller accepts the terms, and lasts as long as Reytd handles personal data for it.
What Reytd processes
- Purpose: to run Reytd for the controller: sending review requests to the store's customers, collecting and moderating their reviews, showing them in the widgets and the API, translating them, sorting them by topic (such as delivery or size) for the controller's insights, importing the reviews the controller sends from its previous review app, and keeping the logs that come with this.
- Data subjects: the store's customers, and people who write reviews of its products.
- Personal data: email address, first and last name, language; order details (number, dates, products, shipping, tracking and returns); reviews (rating, title, text, the name shown) and the store's replies; email events (delivered, bounced, clicked, unsubscribed, and opened if the controller turns that on); and requests to the Reytd API, which may contain all of these.
- No sensitive data: Reytd isn't meant for special categories of personal data (article 9), and the controller must not send any.
Reytd's obligations
Reytd:
- Follows the controller's instructions: processes personal data only as these terms and the controller's settings in Reytd describe, unless EU or Swedish law requires otherwise, in which case Reytd tells the controller first unless that law forbids it.
- Keeps it confidential: everyone at Reytd who can access the data is bound to confidentiality.
- Keeps it secure (article 32): data is stored in the EU, all traffic is encrypted (HTTPS), access is limited to the people who run Reytd, backups are made every night, logs and email copies are deleted after fixed periods, and email addresses on the do-not-email list are kept only as a keyed hash.
- Helps with requests from data subjects: the controller can export or erase a customer's data itself, on the store's Customer data page. Reytd passes on any request it receives directly, and helps where the tools aren't enough.
- Reports breaches: tells the controller without undue delay, and no later than 48 hours after becoming aware of a personal data breach, with what is known about it.
- Helps with compliance: gives the information the controller reasonably needs for data protection impact assessments and consultations with authorities.
- Deletes the data at the end: within 90 days after the agreement ends, unless the law requires keeping it. Copies in backups are gone within a further 35 days. The controller can export its data before then.
- Allows audits: makes available the information needed to show it meets this agreement, and allows audits by the controller or an auditor it chooses, at the controller's cost, with 30 days' notice and at most once a year, unless a breach gives reason for more.
The controller's obligations
The controller is responsible for having a legal basis for the data it sends to Reytd and for the review requests it has sent, for informing its customers, and for giving instructions that comply with the law.
Sub-processors
The controller authorizes Reytd to use these sub-processors:
| Sub-processor | What for | Where |
|---|---|---|
| DigitalOcean, LLC | Hosting: the servers and database | Frankfurt, Germany |
| Cloudflare, Inc. | Network and security; storage of widget files (with reviews and the names shown) and product images; delivery of the widget files | Storage in the EU; delivered through its global network |
| Mailgun Technologies, Inc. | Sending review requests and other emails | EU region |
| Anthropic, PBC | Translating reviews: only the review's title and text, the store's reply and a hint of the review's language. Sorting reviews by topic: only the review's rating, title and text. In both, email addresses, phone numbers, links and the customer's full name are taken out first, and the customer's email address from the order is never sent; not used for training, deleted within 30 days | US |
| Laravel Holdings, Inc. (Laravel Forge) | Managing and deploying the servers | US |
| Laravel Holdings, Inc. (Laravel Nightwatch) | Monitoring errors and performance: request addresses without query strings or the secrets in links, timings of requests, queries and jobs, error messages and log lines, with email addresses, IP addresses, the secrets in links and the values of failed queries taken out; no names or email subjects | EU (data region) |
Reytd has an agreement with each sub-processor that protects the data at least as well as this one. Transfers outside the EU/EEA are covered by the EU–US Data Privacy Framework or the European Commission's standard contractual clauses.
Reytd tells the controller by email at least 30 days before adding or replacing a sub-processor. If the controller objects on reasonable data protection grounds and we can't find a solution, it can end the agreement and get back what it paid for the time after.
Conflicts
If this agreement and the terms of service disagree about personal data, this agreement applies.