---
title: Security - Workflow Documents
description: >-
  What Workflow Documents is built on, where it runs, how your documents and
  store data are encrypted and isolated, and how we keep the app up to date.
  No PHP anywhere.
source_url:
  html: >-
    https://docs.workflow-documents.app/security
  md: >-
    https://docs.workflow-documents.app/security.md
---

# Security

Workflow Documents is built and operated by Code Creation Labs. This page explains what the app is made of, where it runs, how your store's data is protected and how we keep everything up to date. It is written for store owners and for anyone filling in a security questionnaire. The privacy policy and the data processing agreement are linked at the end.

## What the app is built on

| Layer | What we use |
| --- | --- |
| Application code | TypeScript on Node.js, a current long-term-support release. The admin pages, the template editor, the Flow action and the API are one code base. |
| PDF rendering | A dedicated rendering service (Gotenberg with headless Chromium) inside our private network. It has no public address, accepts requests only from the app and with authentication, runs with JavaScript disabled in a fresh context per document, and cannot reach private network addresses. |
| Database, cache and files | PostgreSQL (Google Cloud SQL), Redis (Google Cloud Memorystore) and Google Cloud Storage for the PDFs |
| Hosting | Containers on Google Kubernetes Engine in Google Cloud region europe-west1 (Belgium, European Union). Databases, caches and file storage are region-local. |
| Shopify integration | Shopify's official app libraries, Shopify Flow actions, the Admin GraphQL API and Shopify's webhooks |
| Your storefront | Nothing runs in your theme or your checkout. |

There is no PHP, WordPress, Java or other runtime anywhere in the service.

> [!NOTE]
> **When a vulnerability is in the news**
> If an advisory concerns PHP, WordPress, Java, .NET or another technology the app does not use, it cannot affect Workflow Documents and there is nothing you need to do. If it concerns Node.js, Chromium, PostgreSQL, Redis or one of the libraries we use, the process under "How we keep the app up to date" applies: the fix ships with the next release, and a critical issue gets a release of its own. You are always welcome to send the advisory to support@codecreationlabs.com and we will confirm in writing whether it applies.

## Security advisories and whether our apps are affected

When a vulnerability or an attack involving Shopify apps is in the news, we check it against every app we make and record the result here, so you can file the answer instead of asking.

| Advisory | When | Our apps | Details |
| --- | --- | --- | --- |
| Node.js security release (CVE-2026-123864 and ten further CVEs in the Node.js runtime) | 11 November 2026 | **Applied.** Our apps run on Node.js, so this one concerned us: every app was rebuilt on the patched release (22.23.5) and has been running it in production since 14 November 2026. Nothing to do on your side. | [How we keep the apps up to date](https://docs.codecreationlabs.app/security) |
| PHP2Shell (CVE-2026-109618, CVE-2026-109619): remote code execution in the PHP engine | 21 October 2026 | **Not affected.** None of our apps contain PHP. | [Statement](https://docs.codecreationlabs.app/blog/php2shell-cve-2026-109618-not-affected) |
| Shopify checkout hijack campaign: scripts injected through the storefront code of third-party apps (Hulk Product Options, Selleasy, Swym Wishlist Plus; Qikify in July) redirected shoppers to fake checkout pages | 10 to 20 October 2026 | **Not affected.** None of our apps was involved, and none of them can place a script of this kind in your storefront. | [Statement](https://docs.codecreationlabs.app/blog/shopify-checkout-hijack-not-affected) |
| Node.js security release (CVE-2026-111497 and nine further CVEs in the Node.js runtime) | 21 October 2026 | **Applied.** Our apps run on Node.js, so this one concerned us: every app was rebuilt on the patched release (22.23.4) and has been running it in production since that week. Nothing to do on your side. | [How we keep the apps up to date](https://docs.codecreationlabs.app/security) |
| nginx security release (CVE-2026-15176, CVE-2026-93479, CVE-2026-97205, CVE-2026-95101, CVE-2026-97629) | 14 October 2026 | **Not affected.** nginx is not part of our apps, and every app now runs behind Google Cloud's managed load balancer with Google Cloud Armor. The nginx ingress used before could not be exploited either: none of the five issues can be reached with its configuration (no alias or rewrite, no server-side includes, no HTTP/3, TLS session tickets off). | [Statement](https://docs.codecreationlabs.app/blog/nginx-nodejs-emudhra-october-2026-status) |
| eMudhra (emSign) certificate authority compromise: the keys of eight intermediate CAs are recoverable, emSign ECC Root CA - G3 distrusted | 20 October 2026 | **Not affected.** No system of ours trusts the distrusted root, none of our certificates comes from eMudhra, and the public Certificate Transparency logs show no eMudhra certificate for any of our domains. | [Statement](https://docs.codecreationlabs.app/blog/nginx-nodejs-emudhra-october-2026-status) |

The same table for all our apps, together with the practices they share, is on [Security at Code Creation Labs](https://docs.codecreationlabs.app/security).

## How your data is protected

**In transit.** Every connection between your browser, Shopify and the app uses TLS. The database, the cache, the file storage and the rendering service have no public address: they are reachable only from inside our private network.

**At rest.** All databases and the PDF storage are encrypted at rest with keys we manage in Google Cloud KMS.

**Field-level encryption on top.** Your store's Shopify access token is encrypted individually with AES-256-GCM under a separate key in Cloud KMS, with automatic key rotation, and decrypted in memory only at the moment a document is generated. It is never written to logs.

**Documents.** A generated PDF contains what your template prints, usually an order with its customer. It is stored only for your plan's retention and is reachable only from your admin, through the Developer API with your key, or through the link handed to Shopify Flow, which expires after 7 days.

**Secrets.** API credentials and keys of the service itself live in Google Secret Manager and are loaded when a service starts. They are not in the code, not in the container images and not in the build pipeline.

**Data minimisation.** The app asks for read access to orders, customers and products, because that is what a template renders. It reads only the one order, product or customer a document is about, at the moment the document is generated, and keeps nothing of it beyond the document itself. Nothing is synced, and nothing is written to your store.

## Who can access what

- **Access tokens locked to our servers.** We switched on Shopify's IP allowlist for the Admin API: Shopify accepts the app's access tokens only from our own outgoing address and rejects them from anywhere else, so a stolen token is useless outside our infrastructure.
- **Expiring access tokens.** The app uses Shopify's expiring offline access tokens. Each token is valid for one hour and is renewed automatically, so a leaked token stops working on its own.
- **Declared network access.** The app declares in its Shopify configuration the outside hosts its code in your storefront, checkout and admin may contact (Shopify's network access rules), so Shopify can spot a request that does not belong there.
- **A firewall in front.** Requests reach the app through Google Cloud's managed global load balancer with Google Cloud Armor, Google's web application firewall, which blocks known attackers and inspects every request before it reaches our servers.
- **Your store only.** Every template, document and setting carries the store it belongs to, and every query is scoped to the store that was authenticated. One store can never read another store's templates or documents.
- **Verified requests only.** Pages inside the Shopify admin are authenticated with Shopify session tokens. Flow steps and Shopify's own webhooks are verified by Shopify's HMAC signature before any data is touched.
- **Templates.** A template is one HTML file with Liquid: the include, render and layout tags are not available, output is escaped by default, and rendering is capped in time and size. See [Template variables and Liquid](https://docs.workflow-documents.app/template-variables-and-liquid.md).
- **Rendering.** The rendered HTML is turned into a PDF by the isolated Chromium with JavaScript disabled. Images are loaded only from public https addresses; private network addresses are refused. A Google font you choose is downloaded at render time, while fonts you upload stay on our infrastructure.
- **Our team.** Production systems are reached only through Google Cloud IAM with individual accounts. Internal maintenance tools are not exposed to the internet.

## How we keep the app up to date

- **Shopify's app security checks.** We run Shopify's [app security checks](https://shopify.dev/docs/apps/build/security/app-security-checks), the deterministic scan and the agent review, against every app we make and again with every release. The 37 checks cover unauthenticated routes, data not scoped to a store, unverified webhooks and app proxy requests, committed secrets, leaked credentials, unsafe HTML and disabled expiring access tokens, among others.
- **Every change is scanned before it can ship.** The pipeline runs type checks and linting, static application security testing (SAST), secret detection, dependency vulnerability scanning and container image scanning. Our release bar is zero known vulnerabilities in dependencies and in the image.
- **Runtime and operating system.** The container image, Node.js on its Alpine Linux base, is rebuilt with every release, so runtime and operating system patches ship continuously, and the rendering service is updated with Chromium. The managed Kubernetes platform keeps the underlying nodes patched.
- **Shopify platform.** We track Shopify's API versions and the security advisories for Shopify's app libraries, and apply updates promptly. The app runs on a current Admin API version.
- **Security reviews.** We conduct a full internal review of every route, data path and database query at regular intervals, most recently in October 2026.
- **Monitoring.** Availability is monitored around the clock and published on our [status page](https://crm.codecreationlabs.com/status/shopify-public-apps), and errors alert us. Operational logs are kept for at most 30 days and never contain tokens or secrets.

## Retention and deletion

- PDF files are deleted automatically after your plan's retention period (7, 30 or 90 days). The history row stays, without the file. You can delete a PDF earlier at any time. See [Document history and downloads](https://docs.workflow-documents.app/document-history.md).
- When you uninstall the app, its access to your store is deleted immediately. Shopify's shop/redact request, which follows 48 hours after uninstall, erases the store's templates, documents and files.
- Shopify's mandatory privacy requests (customers/data_request, customers/redact and shop/redact) are handled automatically within the timelines Shopify sets.
- Sub-processors and the full retention schedule are in the [privacy policy](https://workflow-documents.app/privacy). A signed data processing agreement can be requested at [workflow-documents.app/dpa](https://workflow-documents.app/dpa).

## Reporting a security issue

If you believe you have found a vulnerability, or you need a security questionnaire completed, email support@codecreationlabs.com. Security reports are read and answered with priority.
