Reguly

Legal

Data processingunder Art. 28 GDPR.

What we commit to as a processor, including the technical and organisational measures and the sub-processors.

Last updated: 7 November 2026

Contents
  1. Data Processing Agreement (DPA)
  2. 1. Parties and contacts
  3. 2. Subject matter, duration and purpose
  4. 3. Types of data and data subjects
  5. 4. Instructions
  6. 5. Obligations of the processor
  7. 6. AI-assisted processing
  8. 7. Sub-processors and third countries
  9. 8. Notification of personal data breaches
  10. 9. Export, return and deletion
  11. 10. Evidence and audits
  12. 11. Obligations of the controller
  13. 12. Liability and final provisions
  14. Annex A — Technical and organisational measures (Art. 32 GDPR)
  15. Annex B — Sub-processors

Data Processing Agreement (DPA)

This data processing agreement (DPA) governs the processing of personal data by Reguly GmbH (the “processor”) on behalf of the customer (the “controller”) when the customer uses the platform. It is part of the main contract (terms and conditions) and is deemed agreed when the main contract is concluded.

This DPA implements the requirements of Art. 28 GDPR. On data protection matters, it prevails over any conflicting provisions of the main contract.

1. Parties and contacts

The processor is Reguly GmbH, Böhlerstraße 1, 40667 Meerbusch, Germany, registered in the commercial register of the local court (Amtsgericht) Neuss under HRB 25709, represented by its managing directors Ben Koenigs, Jan Crienen and Oskar Cornelissen. The controller is the customer who concluded the main contract.

The processor answers data protection questions and receives reports of security incidents at info@reguly.eu. No data protection officer has been appointed, as there is no legal obligation to do so. On the controller’s side, users with the Owner or Admin role in its company account and any persons it names in text form may issue instructions.

2. Subject matter, duration and purpose

The subject matter is the operation of the platform under the main contract. This includes in particular accounts and teams, product, packaging and supplier data, requests to suppliers and their evaluation, signed declarations, public product passports and conformity pages, connections to shop systems, the import of forwarded e-mails, and support. The processor processes personal data only to provide these services. This DPA applies for the term of the main contract and thereafter until the data has been returned or deleted under section 9.

3. Types of data and data subjects

Depending on use, the following data is processed:

  • User account data: name, business e-mail address, team role, sign-in and session data;
  • Contact details of persons at suppliers, manufacturers and other business partners: name, company, position, e-mail address, phone number;
  • Communication content: requests, replies, forwarded e-mails and their attachments;
  • Declaration and signature data: name, position, place, date and signature of the signatory;
  • Product, packaging and evidence data and uploaded documents, where they name persons, such as authorised representatives or contacts in data sheets;
  • Data from connected shop systems and order exports, where the agreed functions need it, such as products, variants and order quantities per destination country;
  • Usage data: visits to public pages without plain-text IP addresses, usage analytics only with consent, sound only during a voice conversation with the assistant.

Data subjects are the controller’s employees and agents, contacts at its suppliers and business partners, signatories, visitors to its public pages and other persons whose data it enters or forwards.

Special categories of personal data (Art. 9 GDPR) are not part of the engagement.

4. Instructions

The processor processes the data only on documented instructions from the controller. Instructions are the main contract, this DPA and the use of the platform within its functions, for example switching on a connection or sending a request. The controller issues supplementary instructions in text form. If the processor is required by law to process data, it informs the controller in advance, unless the law prohibits this. If it considers an instruction unlawful, it informs the controller without delay and may suspend the instruction until it is confirmed.

5. Obligations of the processor

The processor commits all persons with access to the data to confidentiality. It implements the technical and organisational measures under Art. 32 GDPR set out in Annex A and develops them in line with the state of the art without lowering the level of protection. It maintains a record of processing activities under Art. 30(2) GDPR. It assists the controller with data subject requests (Art. 12–23 GDPR) and with the obligations under Art. 32–36 GDPR; requests it receives directly are forwarded without delay. Processor staff with an administration role may access the controller’s data for support, troubleshooting and maintenance, to the extent the occasion requires. Every sign-in on behalf of a user is logged; on request, the controller receives a list of these accesses.

6. AI-assisted processing

Some functions use language models: reading data sheets, documents and shop data, evaluating supplier replies and forwarded e-mails, the assistant with voice input and speech output, and text suggestions. For this, the platform sends the content needed in each case to Google’s Gemini: via the Gemini API (paid tier, currently without a fixed processing region) and, for forwarded documents, also via Vertex AI in Frankfurt. For accounts with curation of incoming documents switched on, the platform also uses Anthropic’s Claude API (USA). Under their contract terms, the providers do not use the data to train their models. The processor does not train its own models with the controller’s data. Results remain assigned to the controller’s account and are not used for other customers. Where the platform applies extracted values automatically, this is recorded in the change history.

7. Sub-processors and third countries

The controller grants general authorisation to engage further processors. The sub-processors engaged are listed in Annex B. The processor concludes a contract under Art. 28(4) GDPR with each of them that imposes the same data protection obligations. Where a sub-processor fails to fulfil its obligations, the processor remains liable to the controller for the performance of that sub-processor’s obligations. It announces changes to Annex B at least 14 days in advance by e-mail to the users with the Owner or Admin role and records them in the change log at www.reguly.de/avv#sub. The controller may object on important data protection grounds within 14 days of receipt. If the parties cannot find a solution, the controller may terminate the affected service or the main contract as of the date the change takes effect. Data is processed outside the EU and the EEA only if the requirements of Art. 44 et seq. GDPR are met, in particular on the basis of the EU-US Data Privacy Framework or the EU Standard Contractual Clauses. Annex B states the basis for each service.

8. Notification of personal data breaches

The processor notifies the controller of a personal data breach without undue delay after becoming aware of it, as a rule within 24 hours. The notice is sent by e-mail to the users with the Owner or Admin role and contains, as far as known, the information under Art. 33(3) GDPR: nature of the breach, data and persons concerned, likely consequences and measures taken. Missing information follows as soon as it is available. The processor takes measures without delay to secure the data and mitigate consequences, and assists the controller with notifying the supervisory authority and informing data subjects (Art. 33, 34 GDPR). The controller can reach the processor for this at info@reguly.eu.

9. Export, return and deletion

On request to info@reguly.eu, the processor provides the controller with its data within 14 days as CSV, JSON or PDF, during the term and up to 30 days after the contract ends. The controller can also download signed declarations and uploaded evidence itself in the platform. 30 days after the contract ends, the processor deletes the controller’s data unless it is legally required to retain it. Copies in backups expire within 90 days thereafter. On request, the processor confirms deletion in text form. The controller’s own retention duties, for example for the technical documentation and declaration of conformity under the PPWR (five years for single-use, ten years for reusable packaging), remain its responsibility; it secures these records by export before the contract ends.

10. Evidence and audits

The processor provides the controller with all information necessary to demonstrate compliance with the obligations under Art. 28 GDPR. This includes Annex A, Annex B and, on request, a summary of the latest review of the measures. It allows for audits, including inspections, by the controller or an auditor mandated by it and bound to confidentiality. On-site audits are announced with reasonable notice, as a rule 14 days, and take place during normal business hours without disrupting operations. Inspections take place at most once per calendar year and additionally for a specific reason, such as after a security incident or at the order of a supervisory authority. Each party bears its own costs; the costs of a mandated auditor are borne by the controller unless the audit reveals a material breach by the processor. Data of other customers is excluded from inspection; audit results are confidential but may be submitted to supervisory authorities. Evidence may also be provided through suitable certificates, attestations or audit reports, including those of sub-processors.

11. Obligations of the controller

The controller is responsible for the lawfulness of the processing and for safeguarding the rights of data subjects. It only enters data for whose processing a legal basis exists. Where the platform contacts persons at the controller’s suppliers on its behalf, the controller informs these persons under Art. 13 and 14 GDPR. The processor provides a notice text for this (privacy policy, section “Information for suppliers and contact persons”, www.reguly.de/privacy#suppliers) and links it in every request e-mail. The controller keeps its users’ credentials secret, assigns roles only as needed and reports any errors or irregularities it notices without delay.

12. Liability and final provisions

Liability is governed by Art. 82 GDPR and the provisions of the main contract. Changes to this DPA follow the procedure for changes to the terms and conditions (section 13 of the terms); changes to Annex B follow section 7. The law of the Federal Republic of Germany applies. Should a provision be invalid, the remaining provisions remain valid. The German version is binding; the English version is a translation.

Annex A — Technical and organisational measures (Art. 32 GDPR)

The processor implements in particular the following measures:

  • Encryption: transmission via TLS; database and file storage encrypted at rest (AES-256); credentials for connected shop systems additionally encrypted within the application;
  • Access control: individual user accounts with sign-in via Firebase Authentication; roles in the company account (Viewer, Editor, Authorised signatory, Admin, Owner); access tokens are valid for a limited time only; processor staff access data only with an administration role for support and maintenance, and sign-ins on behalf of a user are logged;
  • Tenant separation: logical separation of different customers’ data at application level, every access is bound to the company account of the signed-in user; content the controller publishes, such as product passports and declarations of conformity, is intentionally accessible without sign-in; database row-level security (RLS) additionally blocks the direct database interfaces;
  • Data minimisation and pseudonymisation: IP addresses are stored only as salted hashes; usage analytics only with consent and with masked form input; no names or addresses of end customers are taken over from order exports;
  • Availability and resilience: daily database backups by the database provider (retained for 7 days), versioning of files in file storage; restoration is tested at least once a year;
  • Logging: security-relevant events and changes to data are recorded in an audit log, including sign-ins on behalf of users; the entries are linked by chained checksums;
  • Sub-processors: engaged only with a data processing agreement and, for transfers to third countries, with EU Standard Contractual Clauses or certification under the EU-US Data Privacy Framework (Annex B);
  • Review: semi-annual review of the measures against a fixed checklist (introduced on 12 October 2026, most recently on 5 November 2026), additionally after major changes and after security incidents; defined procedure for detecting, assessing and reporting security incidents.

Annex B — Sub-processors

The following sub-processors are engaged (as of 7 November 2026):

  • Vercel Inc., 340 S Lemon Ave #4133, Walnut, CA 91789, USA — hosting of the web application and its server-side functions; region Frankfurt (fra1); EU-US Data Privacy Framework, supplemented by EU Standard Contractual Clauses.
  • Render Services, Inc., San Francisco, USA — operation of the backend interface (API) and the database of the Shopify app; region Frankfurt; EU-US Data Privacy Framework, supplemented by EU Standard Contractual Clauses.
  • Supabase Pte. Ltd., 65 Chulia Street #38-02/03, OCBC Centre, Singapore 049513, Singapore — database of the platform and database of internal customer care (both in the Frankfurt region, eu-central-1); EU Standard Contractual Clauses (Modules 2 and 3) for access from third countries.
  • Amazon Web Services EMEA SARL, Luxembourg — file storage (Amazon S3, region Frankfurt, eu-central-1) and file delivery (Amazon CloudFront, global network); EU Standard Contractual Clauses for access from third countries.
  • Google Ireland Limited, Ireland, and Google LLC, USA — sign-in (Firebase Authentication, no selectable region); the processor’s e-mail mailboxes, for example for forwarding to data@reguly.eu (Google Workspace); data storage for incoming documents with AI evaluation (Google Cloud and Vertex AI, region Frankfurt, europe-west3); AI evaluation via the Gemini API (paid tier, currently without a fixed region); EU-US Data Privacy Framework and EU Standard Contractual Clauses.
  • Anthropic, PBC, USA — AI evaluation of incoming documents (Claude API), only for accounts with curation switched on; processing in the USA; EU Standard Contractual Clauses.
  • Plus Five Five, Inc. (Resend), 2261 Market Street #5039, San Francisco, CA 94114, USA — sending the platform’s e-mails (system messages, requests and reminders to suppliers) and receiving replies; sending via the Ireland region (eu-west-1), delivery logs also in the USA; EU-US Data Privacy Framework, supplemented by EU Standard Contractual Clauses.

The following are not sub-processors within the meaning of this DPA: Stripe, which handles payments as an independent controller; shop systems and services that the controller connects itself and with which it has its own contracts (e.g. Shopify, Shopware, Billbee, Stanley/Stella); services the processor uses only for its own purposes (e.g. GitHub, Notion, Groq, Google Ads, Calendly, Microsoft Clarity with the users’ consent). The privacy policy describes these services.

Change log

  • 5 November 2026: Annex B reconciled with the actual setup and rewritten. Newly listed: Supabase, Amazon Web Services, Google, Anthropic and Resend. Corrected for Render: backend interface and database of the Shopify app, not the database of the platform. Scope note added.
  • 5 November 2026, addendum: The video avatar is no longer used; the services intended for it are not part of Annex B. Annex B lists eight sub-processors.
  • 7 November 2026: The platform database at Supabase runs in the Frankfurt region (eu-central-1) instead of Paris (eu-west-3). Annex B and the privacy policy now name Frankfurt only.
  • 7 November 2026: Microsoft Clarity removed from Annex B; usage analytics runs under the processor’s own responsibility and only with the users’ consent (privacy policy, cookies section). Annex B lists seven sub-processors. Addresses and transfer bases updated from the providers’ current agreements: Vercel, Render and Resend under the EU-US Data Privacy Framework; Supabase Pte. Ltd., Singapore, under EU Standard Contractual Clauses. Security incidents are reported to info@reguly.eu.