Security updateOur apps are not affected by PHP2Shell or the checkout hijack campaign that hit Shopify stores in October. No action is needed for any of our apps.How we protect your store

Data Processing Agreement

pursuant to Article 28 GDPR (Auftragsverarbeitungsvertrag) - for the use of Workflow Forms

1. Subject matter and instructions

The Processor processes personal data on behalf of the Controller exclusively to provide the Workflow Forms service: displaying forms on the Controller's Online Store (as a theme app block, a popup or a direct link page, delivered through Shopify's app proxy), receiving and storing the submissions of the Controller's storefront visitors, protecting the forms against spam, passing each submission to Shopify Flow as a trigger, showing the submissions to the Controller in an inbox and, where the Controller turns these on, copying submissions into metaobjects in the Controller's Shopify store and exporting them as CSV.

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: displaying forms on the Controller's Online Store (as a theme app block, a popup or a direct link page, delivered through Shopify's app proxy), receiving and storing the submissions of the Controller's storefront visitors, protecting the forms against spam, passing each submission to Shopify Flow as a trigger, showing the submissions to the Controller in an inbox and, where the Controller turns these on, copying submissions into metaobjects in the Controller's Shopify store and exporting them as CSV.

Categories of personal data: the values of the form fields the Controller defines, which may include name, email address, telephone number, message text and any custom field; the state of consent checkboxes (such as marketing consent); the storefront language; the Shopify customer ID of a logged-in visitor as passed by Shopify in signed form; a one-way hash of the first email field and of the customer ID, used only to find a person's submissions for deletion; the form handle, status and timestamps. The app has no Shopify data permissions and reads no customer records from the Controller's store. The visitor's IP address is used only as a short-lived hash for rate limiting and is never stored or logged.

Categories of data subjects: visitors of the Controller's Online Store who submit a form, including the Controller's customers; 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 the submissions found by the customer's ID or email hash, 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 every submission whose email hash or customer ID matches the customer named in the request. Independently of this, the Controller can delete submissions at any time, individually or in bulk, in the app or through the Developer API. Copies the Controller has made as metaobjects in its Shopify store or as CSV exports are outside the Processor's systems and are deleted by the Controller.

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: displaying forms on the Controller's Online Store (as a theme app block, a popup or a direct link page, delivered through Shopify's app proxy), receiving and storing the submissions of the Controller's storefront visitors, protecting the forms against spam, passing each submission to Shopify Flow as a trigger, showing the submissions to the Controller in an inbox and, where the Controller turns these on, copying submissions into metaobjects in the Controller's Shopify store and exporting them as CSV.

Type of personal data: the values of the form fields the Controller defines, which may include name, email address, telephone number, message text and any custom field; the state of consent checkboxes (such as marketing consent); the storefront language; the Shopify customer ID of a logged-in visitor as passed by Shopify in signed form; a one-way hash of the first email field and of the customer ID, used only to find a person's submissions for deletion; the form handle, status and timestamps. The app has no Shopify data permissions and reads no customer records from the Controller's store. The visitor's IP address is used only as a short-lived hash for rate limiting and is never stored or logged.

Categories of data subjects: visitors of the Controller's Online Store who submit a form, including the Controller's customers; 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). Submissions are stored until the Controller deletes them or a customers/redact request covers them; rate-limit hashes expire after a few minutes.

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: submissions are kept only until the Controller deletes them or a redaction request covers them; rate-limit hashes of visitor IP addresses expire after a few minutes; technical logs contain no form values, no customer data and no visitor IP addresses and are kept for a limited period only.
  • Form values are stored as one encrypted envelope per submission with a dedicated key in Google Cloud KMS and are decrypted only when the Controller opens or exports a submission or a workflow needs the values; lists show only who submitted when. Spam protection by a time-stamped signed render token, a honeypot field and per-shop and per-form rate limits; the form script sets no cookies.
  • 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. Not a sub-processor: where the Controller selects a Google Font for a form, the visitor's browser loads the font files directly from Google Fonts (Google Ireland Limited) on the Controller's instruction; the Controller covers this in its own privacy notice.

  • Google Cloud EMEA Limited - Hosting (Kubernetes), database (Cloud SQL), cache (Memorystore), file storage for the Controller's uploaded fonts (Cloud Storage) 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 app proxy and theme app extension through which forms are displayed on the Controller's store and submissions are sent to the Processor, webhooks, Shopify Flow, which receives each submission as the "Form submitted" trigger, and, where the Controller turns it on, metaobjects in the Controller's own store - 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 visitor data or form values - European Union - AWS region eu-central-1 (Frankfurt, Germany) - DPA: https://d1.awsstatic.com/legal/aws-dpa/aws-dpa.pdf

Request your signed DPA

Fill in your company details and we'll email you a personalised Data Processing Agreement (Article 28 GDPR), already signed by Code Creation Labs GmbH.