Data Processing Agreement
pursuant to Article 28 GDPR (Auftragsverarbeitungsvertrag) - for the use of Workflow Documents
1. Subject matter and instructions
The Processor processes personal data on behalf of the Controller exclusively to provide the Workflow Documents service: designing document templates and generating PDF documents (such as invoices, packing slips, product sheets and customer summaries) for the Controller's orders, products and customers from Shopify Flow, the Shopify admin or the Developer API, storing the generated documents for the retention period of the Controller's plan and keeping a history of the generated documents.
The Processor processes the data only on documented instructions from the Controller, including with regard to transfers of personal data to a third country, unless required to do so by Union or Member State law. This DPA, together with the Controller's use of the app and its configuration, constitutes such documented instructions.
The Processor informs the Controller immediately if it considers that an instruction infringes the GDPR or other data protection provisions.
2. Duration
This DPA applies for as long as the Processor processes personal data on behalf of the Controller, i.e. for the duration of the Controller's use of the app, and ends with the deletion or return of the data in accordance with Section 9.
3. Nature and purpose of processing; data and data subjects
Nature and purpose of the processing: designing document templates and generating PDF documents (such as invoices, packing slips, product sheets and customer summaries) for the Controller's orders, products and customers from Shopify Flow, the Shopify admin or the Developer API, storing the generated documents for the retention period of the Controller's plan and keeping a history of the generated documents.
Categories of personal data: order data read from the Controller's Shopify store for a document (order number, dates, status and notes, line items with product names, SKUs, quantities and prices, discounts, taxes, shipping method and payment gateway names, the customer's name, email address and telephone number, billing and shipping addresses and the customer's locale); customer data (name, email address, telephone number, address, note, tags, locale, order count, amount spent and the 20 most recent orders); product data (title, description, vendor, type, tags, images, options and variants with SKU, barcode, price and stock), which as a rule contains no personal data; the generated PDF documents, which contain these data as placed by the Controller's template; and per document a history entry with template name, resource ID and display name, file name, status, error text and timings.
Categories of data subjects: the Controller's customers (purchasers and recipients of shipments and invoices) and any other individuals whose data appears in the Controller's orders, customers or templates; the Controller's own staff who use the app or receive its notifications.
Further detail is set out in Annex 1.
4. Confidentiality
The Processor ensures that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality, and that access is limited to what is necessary to provide the service.
5. Security of processing (Art. 32 GDPR)
Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk to the rights and freedoms of natural persons, the Processor implements appropriate technical and organisational measures (TOMs) to ensure a level of security appropriate to the risk. The current measures are described in Annex 2.
6. Sub-processors
The Controller grants the Processor general written authorisation to engage the sub-processors listed in Annex 3 to provide the service. The Processor imposes data protection obligations on each sub-processor by contract that are equivalent to those set out in this DPA.
The Processor informs the Controller of any intended changes concerning the addition or replacement of sub-processors at least 30 days in advance, thereby giving the Controller the opportunity to object to such changes before they take effect.
7. Assistance to the Controller
Taking into account the nature of the processing, the Processor assists the Controller by appropriate technical and organisational measures, insofar as this is possible, in fulfilling the Controller's obligation to respond to requests for exercising the data subject's rights under Chapter III GDPR.
The Processor assists the Controller in ensuring compliance with the obligations pursuant to Articles 32 to 36 GDPR (security, breach notification, data protection impact assessment and prior consultation), taking into account the nature of processing and the information available to the Processor.
8. Personal data breach
The Processor notifies the Controller without undue delay after becoming aware of a personal data breach, and provides the information reasonably required to enable the Controller to meet its notification obligations under Articles 33 and 34 GDPR.
9. Deletion or return of data
At the choice of the Controller, the Processor deletes or returns all personal data processed on behalf of the Controller after the end of the provision of services, and deletes existing copies, within 30 days of termination (for example, uninstallation of the app), unless Union or Member State law requires storage of the personal data.
The Processor additionally honours Shopify's mandatory data-protection webhooks (customers/data_request, customers/redact and shop/redact) within the timelines Shopify specifies. On customers/data_request the Processor acknowledges and logs the request and compiles by hand what the app holds about the customer (the history entries and any stored documents of the orders named in the request), which it hands to the Controller within the 30 days Shopify's requirements allow; there is no automatic export. On shop/redact the Processor deletes all data of the Controller's shop within 48 hours of receiving the webhook; on customers/redact it deletes the documents of the orders named in the request and removes the customer-related fields from the corresponding history entries. Independently of this, generated documents are deleted automatically after the retention period of the Controller's plan, and the Controller can delete any document earlier in the app.
10. Audits and information
The Processor makes available to the Controller all information necessary to demonstrate compliance with the obligations laid down in Article 28 GDPR and allows for and contributes to audits, including inspections, conducted by the Controller or another auditor mandated by the Controller, subject to reasonable notice and confidentiality.
11. International transfers
The Processor's own processing infrastructure (Google Cloud, region europe-west1, Belgium) is located in the European Union. The sub-processors used for this service are listed in Annex 3. Where a sub-processor - in particular Shopify - processes personal data outside the EEA, the transfer is safeguarded by appropriate measures pursuant to Chapter V GDPR, in particular the EU Standard Contractual Clauses and, where applicable, the EU-U.S. Data Privacy Framework.
12. Liability and final provisions
Liability is governed by Article 82 GDPR and the agreement between the parties for the use of the app. This DPA is governed by the law of the Federal Republic of Germany. Should individual provisions be invalid, the validity of the remaining provisions remains unaffected. Amendments must be made in text form.
In the event of any conflict between this DPA and other agreements between the parties, the provisions of this DPA prevail with regard to data protection.
13. Conclusion of this Agreement
This Data Processing Agreement is provided on the Processor's website (and, where applicable, in the Controller's customer account). It is concluded when the Controller, before conclusion, takes note of its content and actively ticks the acceptance checkbox (for example 'I accept the Data Processing Agreement').
A handwritten signature by the Controller is therefore not required; the Controller's acceptance is recorded electronically with the date of acceptance, and the Processor's signature is affixed below.
Annex 1 - Details of the processing
Subject matter and purpose: designing document templates and generating PDF documents (such as invoices, packing slips, product sheets and customer summaries) for the Controller's orders, products and customers from Shopify Flow, the Shopify admin or the Developer API, storing the generated documents for the retention period of the Controller's plan and keeping a history of the generated documents.
Type of personal data: order data read from the Controller's Shopify store for a document (order number, dates, status and notes, line items with product names, SKUs, quantities and prices, discounts, taxes, shipping method and payment gateway names, the customer's name, email address and telephone number, billing and shipping addresses and the customer's locale); customer data (name, email address, telephone number, address, note, tags, locale, order count, amount spent and the 20 most recent orders); product data (title, description, vendor, type, tags, images, options and variants with SKU, barcode, price and stock), which as a rule contains no personal data; the generated PDF documents, which contain these data as placed by the Controller's template; and per document a history entry with template name, resource ID and display name, file name, status, error text and timings.
Categories of data subjects: the Controller's customers (purchasers and recipients of shipments and invoices) and any other individuals whose data appears in the Controller's orders, customers or templates; the Controller's own staff who use the app or receive its notifications.
Duration: for the term of the Controller's use of the app (see Section 2). Generated documents are stored for the retention period of the Controller's plan (currently 7, 30 or 90 days depending on the plan) and then deleted automatically; history entries remain until the shop's data is deleted.
Annex 2 - Technical and organisational measures (Art. 32 GDPR)
The Processor implements the following technical and organisational measures:
- Confidentiality - physical access control: hosting in Google Cloud's certified EU data centres (ISO 27001 / SOC 2); the Processor operates no own server rooms.
- Confidentiality - system access control: authenticated access to all systems, multi-factor authentication (MFA) for administrative access, use of a company password manager, least-privilege administrative accounts, no shared logins, and least-privilege service accounts for the application's own access to cloud resources.
- Confidentiality - data access control: role-based access restrictions, access logging, and encryption of data at rest.
- Confidentiality - separation control: logical separation of each merchant's data (multi-tenant isolation) and separate production and non-production environments.
- Integrity - transfer control: TLS/HTTPS for all data in transit; the application, its databases, file storage and caches run in the Google Cloud region europe-west1 (Belgium).
- Integrity - input control: audit logging of relevant changes (who, what, when).
- Availability and resilience: redundant EU cloud infrastructure, monitoring and alerting, regular fully encrypted backups, and documented recovery procedures.
- Procedures for regular review: data-protection management, an incident-response and breach-notification process, privacy by design and by default, and sub-processor control under Art. 28(2) and (4) GDPR.
- Storage limitation: generated documents are deleted automatically by an hourly job after the retention period of the Controller's plan (7, 30 or 90 days) and can be deleted earlier by the Controller; signed download links expire after 7 days; technical logs contain no document contents and no customer data and are kept for a limited period only.
- PDF rendering by a Chromium-based renderer operated inside the Processor's own cluster; no third-party rendering service receives document contents. If the Controller selects a Google Font for its documents, the renderer fetches the font files from Google Fonts (Google Ireland Limited) at render time; that request carries no personal data. The app reads only the one order, product or customer a document is generated for, at the moment of generation, and does not list or synchronise the Controller's orders or customers.
- All data is encrypted at rest with customer-managed keys in Google Cloud KMS (CMEK); the Controller's Shopify access token is additionally encrypted at field level with a separate KMS key and decrypted only in memory; API keys are stored as hashes only.
Annex 3 - Approved sub-processors
The Controller authorises the following sub-processors:
- Google Cloud EMEA Limited - Hosting (Kubernetes), database (Cloud SQL), file storage (Cloud Storage), cache (Memorystore) and key management (Cloud KMS) - European Union - Google Cloud region europe-west1 (Belgium) - DPA: https://cloud.google.com/terms/data-processing-addendum
- Shopify International Limited - The Shopify platform: OAuth, the Admin API from which the app reads order, product and customer data for each document, webhooks, and Shopify Flow, which receives the download link - Ireland (EU); Shopify operates globally, third-country transfers safeguarded under Chapter V GDPR (SCC / EU-U.S. DPF) - DPA: https://www.shopify.com/legal/dpa
- Amazon Web Services EMEA SARL (Amazon SES) - Delivery of the app's own notification emails to the Controller (for example quota and failure alerts); these emails never contain customer data or document contents - European Union - AWS region eu-central-1 (Frankfurt, Germany) - DPA: https://d1.awsstatic.com/legal/aws-dpa/aws-dpa.pdf