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

Privacy Policy

1. Controller and contact

This Privacy Policy explains how Workflow Forms ("the app") processes personal data. The app is operated by Code Creation Labs GmbH, Friedensstr. 1, 47647 Kerken, Germany, represented by Yann Faulhaber (Amtsgericht Kleve, HRB 20472; VAT ID DE451671933).

For any data-protection question or to exercise your rights, contact us at [email protected].

2. Scope of this policy and our role

This policy covers the app itself: the Workflow Forms app installed in a merchant's Shopify admin, the forms it displays on the merchant's Online Store, its triggers for Shopify Flow, and its Developer API and MCP server. Our public websites (this landing page and the help center) are covered by our company privacy policy, which is linked in the footer; this policy mentions them only where they touch the app.

The app is installed by a Shopify merchant (the "merchant") to show forms (for example contact, newsletter or request forms) on their Online Store and to start Shopify Flow workflows from the submissions. For the personal data a visitor enters into a merchant's form, the merchant is the data controller and we act as a processor on the merchant's behalf under Article 28 GDPR. The merchant decides which fields a form has, what it asks for and what happens with a submission, and informs their visitors in their own privacy policy. Our Data Processing Agreement can be concluded online on this website (DPA link in the footer).

We are the controller only for the limited account and operational data we need to run the service and to communicate with the merchant: the shop domain, the merchant's plan and usage counters, the forms, fields and settings the merchant creates, the API keys the merchant creates, the notification recipients the merchant enters, and support correspondence.

3. What we process and why

Purpose of processing: displaying the merchant's forms on their Online Store (as a block in the theme, as a popup or as a page at a direct link), receiving and storing the submissions, protecting the forms against spam, passing each submission to Shopify Flow so that the merchant's workflows run, and showing the submissions to the merchant in an inbox in the app.

Data a visitor sends us when submitting a form: the values of the fields the merchant defined, which may include name, email address, telephone number, a message and any custom field; the storefront language; the state of consent checkboxes (for example marketing consent); and, if the visitor is logged in to the merchant's store, their Shopify customer ID, which Shopify passes to us in signed form. The app has no Shopify data permissions and never reads customer records from the merchant's store itself; we know about a visitor only what they type into the form.

What we store per submission: the field values as one encrypted envelope (see section 5); a one-way hash of the first email field and of the customer ID, used only to find a person's submissions when they are to be deleted; the form handle, the language, the status in the inbox and timestamps. The visitor's IP address is never stored (see section 4).

Categories of data subjects: visitors of the merchant's Online Store who submit a form, including the merchant's customers; the merchant's own staff who use the app or receive its notifications.

Legal basis: performance of the contract with the merchant and our legitimate interest in providing and securing the service (Art. 6(1)(b) and (f) GDPR). For the personal data visitors enter into a form, the merchant determines the legal basis towards their visitors.

4. What happens in the visitor's browser

A form is served on the merchant's store domain through Shopify's app proxy, and the submission reaches us the same way. The form script sets no cookies and uses no analytics, advertising or tracking services. A popup form remembers in the visitor's browser (local storage) whether it has already been shown or closed, so that it does not reappear on every page; this is strictly functional and requires no consent.

Spam protection: each rendered form carries a time-stamped signed token, a hidden honeypot field catches automated submissions, and submissions are rate-limited per shop and form. For the rate limit we keep a hash of the visitor's IP address for a few minutes in a cache (Redis); the IP address itself is never stored or logged. A refused submission is not stored.

Fonts and styling: fonts the merchant uploads are delivered from our public content delivery network. If the merchant selects a Google Font for a form, the visitor's browser loads the font files directly from Google Fonts (Google Ireland Limited); Google then receives the visitor's IP address and browser details. This is the merchant's choice, and the merchant covers it in their own privacy policy. The merchant's own CSS and Liquid for a form run on the storefront page, which Shopify serves. Visitor-facing messages (such as "required" or "sent") are shown in the storefront language.

5. Hosting and security

All processing takes place on Google Cloud in the region europe-west1 (Belgium): the application runs on Kubernetes, data is stored in Cloud SQL (PostgreSQL), and short-lived data in Memorystore (Redis). Everything is encrypted at rest with customer-managed keys in Cloud KMS and in transit with TLS.

The values of each submission are encrypted as one envelope with a dedicated key in Cloud KMS before they are stored, and are decrypted only when the merchant opens a submission, exports it, or a workflow needs the values. Lists in the app and the API show who submitted when; the values are opened one submission at a time. The Shopify access token is additionally encrypted with a separate KMS key.

Technical logs contain request IDs, status codes, timings, the shop domain and error messages. They contain no form values, no customer data and no visitor IP addresses. Logs are kept with Google Cloud Logging for a limited time for operations and security.

Our public websites (this landing page and the help center) are delivered through Cloudflare, Inc. (DNS, TLS termination and edge caching), which processes the visitor's technical connection data. The app itself and all merchant and visitor data stay on Google Cloud in the europe-west1 region.

How we protect your data in practice - encryption in transit and at rest, a second layer of encryption for access tokens and credentials, strict separation between stores, access control, vulnerability scanning before every release and how to report a security issue - is described on the Security page of the Workflow Forms help center and, for all our apps, on Security at Code Creation Labs. Both pages also list current security advisories and state whether our apps are affected.

Security reports and questions go to [email protected].

6. Sub-processors

We engage the following sub-processors to provide the service. Each is bound by a data processing agreement with obligations equivalent to ours:

  • Google Cloud EMEA Limited - Hosting (Kubernetes), database (Cloud SQL), cache (Memorystore), file storage for the merchant'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 merchant's store and submissions are sent to us, webhooks, Shopify Flow, which receives each submission as the "Form submitted" trigger, and, if the merchant turns it on, metaobjects in the merchant'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 merchant (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

7. Where submissions go on the merchant's instruction

Every stored submission is sent to Shopify Flow as the "Form submitted" trigger with all values as JSON, so that the merchant's workflows run (for example to tag a customer, create a draft order or notify the merchant's team). What a workflow does with the values is decided by the merchant in Shopify Flow. A refused submission and a status change in the inbox fire two further triggers that carry no form values.

The merchant can turn on a copy of each submission as a metaobject in their own Shopify store; Shopify then stores that copy under the merchant's account. The merchant can export submissions from the inbox as a CSV file.

The merchant can create API keys for the app's Developer API and MCP server, which let the merchant's own tools (their code or an AI agent) manage forms and fields and read, update and delete submissions within the merchant's own shop. We store only a hash of each key. The merchant is responsible for the tools they connect and for what those tools do with the data they receive.

Google Fonts (section 4) is likewise a service the merchant chooses, not a sub-processor of ours.

8. Data retention and deletion

We keep personal data only as long as needed to provide the service. Submissions are stored until the merchant deletes them, individually or in bulk in the inbox or through the Developer API. The rate-limit hashes described in section 4 expire after a few minutes.

On a customers/redact request from Shopify we delete every submission whose email hash or customer ID matches the customer named in the request. On a customers/data_request from Shopify, the app acknowledges and logs the request; it produces no automatic export. Our support then compiles by hand the submissions found by the customer's ID or email hash and hands them to the merchant within the 30 days Shopify's requirements allow.

Uninstalling the app ends the processing. Shopify then sends us the shop/redact webhook, and within 48 hours of receiving it we delete all of the shop's data: forms, fields, submissions, settings, fonts, the access token and API keys. Copies the merchant made as metaobjects or CSV exports are under the merchant's control. Merchants can also request deletion at any time at [email protected].

9. International transfers

Our own infrastructure is in the EU. Where a sub-processor - in particular Shopify - processes personal data outside the EEA, the transfer is safeguarded under Chapter V GDPR, in particular the EU Standard Contractual Clauses and, where applicable, the EU-U.S. Data Privacy Framework.

10. Your rights

Subject to the applicable conditions, you have the right of access, rectification, erasure, restriction of processing, data portability and objection, and the right to lodge a complaint with a supervisory authority. The authority responsible for us is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW), Kavalleriestr. 2-4, 40213 Düsseldorf, Germany.

Because we act as the merchant's processor for the data visitors enter into a form, requests about a submission are best directed to the merchant whose form you used; we will assist the merchant in responding.

11. No tracking, no cookies

Neither the app in the Shopify admin nor the form script on the storefront uses analytics, advertising or tracking services or sets tracking cookies. This website sets no third-party advertising or analytics cookies and embeds no third-party trackers.

12. Changes to this policy

We may update this Privacy Policy to reflect changes to the service or the law. This version applies from 7 October 2026; the current version is always published on this page. Material changes to sub-processors are notified in accordance with our DPA.

13. Our other apps

Code Creation Labs GmbH also publishes these Shopify apps. Each app has its own privacy policy and data processing agreement on its website.