Data Protection

Last updated: 1 August 2026

This page sets out the technical and organisational measures we apply to merchant data, and serves as our data processing summary for merchants who need one for their own compliance records.

Roles

The merchant is the controller. Ignite Apps is the processor, acting only on the merchant's documented instructions.

Categories of data

Customer records and order history (may include name, email, phone, shipping address).

Purpose of processing

To recreate the merchant's own customers and orders in a new Shopify store the merchant controls, at the merchant's explicit instruction (a store-to-store migration).

Protected customer data

This app requests customer or order scopes, so Shopify's Protected Customer Data requirements apply. Our assessed level: Level 2 — customer PII is processed in order to replicate it.

Security measures

• TLS in transit; AES-256-GCM at rest.
• HMAC-verified OAuth callbacks and webhooks; admin-only operational endpoints.
• Least-privilege scopes — we request only what the app needs.

Retention and deletion

• Transient processing only. No customer PII is retained after a migration completes. The only persisted secret is the store OAuth access token, encrypted at rest with AES-256-GCM under a separate server-side key.
• On completion, on uninstall, and on the shop/redact webhook.

GDPR / CCPA compliance webhooks

We implement all three of Shopify's mandatory compliance webhooks. Each request is verified with an HMAC signature and an unsigned or mis-signed request is rejected with HTTP 401.

• customers/data_request — responds with the customer data we hold.
• customers/redact — erases the named customer's data.
• shop/redact — erases the store's stored connection and all associated records.

Sub-processors

Cloudflare (compute, storage, DNS).

Contact

Data protection enquiries: [email protected].