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 Documents ("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 Documents app installed in a merchant's Shopify admin, its "Generate document" action 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 generate PDF documents from the data in their store. For the personal data contained in the orders, customers and products the app reads for a document, and in the documents it generates, the merchant is the data controller and we act as a processor on the merchant's behalf under Article 28 GDPR. 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 settings and templates 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: generating PDF documents (for example invoices, packing slips, product sheets and customer summaries) from templates the merchant designs in HTML, CSS and Liquid or with the visual builder. A document is generated when a Shopify Flow workflow runs the "Generate document" action, when the merchant generates it in the admin, or when the merchant's own tools call the Developer API or MCP server. To render one document the app reads the one order, product or customer the document is for from the merchant's Shopify store, fills the template with it and stores the resulting PDF.

Data read from Shopify for an order document: order number, dates, status and notes; line items with product names, SKUs, quantities and prices; discounts, taxes, shipping method and the names of the payment gateways; the customer's name, email address and telephone number; billing and shipping addresses; and the customer's locale. For a customer document: name, email address, telephone number, address, note, tags, locale, order count, amount spent and the customer's 20 most recent orders. For a product document: title, description, vendor, type, tags, images, options and variants with SKU, barcode, price and stock; product data as a rule contains no personal data.

What we store: the generated PDF, which contains whatever the merchant's template placed in it; one history entry per document with the template name, the ID and display name of the order, product or customer, the file name, status, error text and timings; the merchant's templates and branding (logo and fonts); and the merchant's account data listed in section 2. We do not keep a copy of the order, product or customer data outside the PDF and the history entry.

Categories of data subjects: the merchant's customers (purchasers and recipients of shipments and invoices) and any other individuals whose data appears in the merchant's orders, customers or templates; 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 the app processes on the merchant's behalf, the merchant determines the legal basis towards its own customers.

4. Access to the merchant's store, Developer API and MCP server

The app requests the Shopify permissions read_orders, read_customers and read_products. Shopify classifies the name, email address, telephone number and address of a customer as protected customer data; we have requested access to these fields from Shopify for the sole purpose of placing them in the merchant's documents, and we comply with Shopify's protected customer data requirements. The app does not list or synchronise the merchant's orders or customers; it reads the one record a document is generated for, at the moment of generation.

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) read and write the merchant's templates and documents and generate new documents, 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.

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), generated documents in Cloud Storage, 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 Shopify access token is additionally encrypted at field level with a separate KMS key and decrypted only in memory when the app reads from the merchant's store.

PDFs are rendered by a Chromium-based renderer (Gotenberg) that runs inside our own cluster; no third-party rendering service receives the document contents. Shopify Flow and the Developer API receive a signed download link that is valid for 7 days; in the admin the merchant downloads documents with their authenticated session. No document is publicly accessible.

The merchant's branding assets, that is the logo and the fonts the merchant uploads, are stored in a public Cloud Storage bucket behind a content delivery network, because they appear in every PDF and are public by design. Merchants must not upload files containing personal data there. If the merchant selects a Google Font for their documents, our renderer fetches the font files from Google Fonts (Google Ireland Limited) at render time; the request carries no document contents and no personal data, and no customer's browser is involved, so Google is not a sub-processor for this.

Technical logs contain request IDs, status codes, timings, the shop domain and error messages. They contain no document contents, 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 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 Documents 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), 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 merchant (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

7. Data retention and deletion

We keep personal data only as long as needed to provide the service. A generated PDF is stored for the retention period of the merchant's plan: 7 days on the Free plan, 30 days on the Starter plan and 90 days on the Unlimited plan. An hourly job deletes documents whose retention period has ended; the merchant can delete a document earlier in the app. Download links expire after 7 days.

The history entry of a document (template name, resource ID and display name, file name, status, error text and timings) remains until the shop's data is deleted, so that the merchant can see what was generated. On a customers/redact request from Shopify we delete the PDFs of the orders named in the request and remove the customer-related fields from the corresponding history entries. 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 what the app holds about that customer, that is the history entries and any stored PDFs of the orders named in the request, and hands it 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: templates, branding, documents, history, settings, the access token and API keys. Merchants can also request deletion at any time at [email protected].

8. 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.

9. 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 in documents, requests about a merchant's customer data are best directed to that merchant; we will assist the merchant in responding.

10. No tracking, no cookies

The app uses no analytics, advertising or tracking services and sets no tracking cookies. This website sets no third-party advertising or analytics cookies and embeds no third-party trackers.

11. 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.

12. 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.