Galantis processes customer data synced from Shopify, including personal information such as name, phone number, email, and purchase history. When a customer or merchant submits a data deletion request under GDPR or other applicable privacy regulations, Galantis handles the erasure through Shopify’s built-in compliance webhook system.Documentation Index
Fetch the complete documentation index at: https://docs.digifist.com/llms.txt
Use this file to discover all available pages before exploring further.
What this covers
- How data deletion requests reach Galantis
- What the
REDACTEDconsent state means and how it is applied - What data is affected by a deletion request
- How
REDACTEDcustomers are handled across the platform
How deletion requests work
Shopify acts as the intermediary for GDPR compliance requests. When a deletion request is submitted — either by a customer requesting erasure of their personal data or by a merchant requesting shop-level data removal — Shopify sends a webhook to all installed apps, including Galantis. Galantis handles two webhook topics:| Webhook | Trigger | Handler |
|---|---|---|
customers/redact | A specific customer requests personal data deletion | ProcessShopifyCustomersRedactJob |
shop/redact | A merchant uninstalls the app and requests full shop data removal | ProcessShopifyShopRedactJob |
The REDACTED state
When acustomers/redact webhook is received, Galantis sets the affected customer’s marketing_state to REDACTED. This state signals that the customer’s data has been subject to a deletion request and the record must no longer be used for any messaging purpose.
REDACTED customers are treated as fully excluded across the platform:
- They are removed from all campaign audience calculations
- They are skipped in all automation message actions
- They do not receive Back-in-Stock notifications, even if they have an
ACTIVEsubscription - They cannot be manually re-added to lists or segments for messaging
The
REDACTED state is permanent within the platform. Unlike UNSUBSCRIBED, which can be reversed by a new explicit opt-in, REDACTED cannot be reversed through normal platform actions. Re-engaging a redacted customer would require a new data collection event with full compliance.Shop-level data removal
When a merchant uninstalls Galantis and requests full data removal via theshop/redact webhook, the ProcessShopifyShopRedactJob handles the erasure of shop-level data associated with that tenant workspace. This covers all customer records, message history, and configuration data held by Galantis for that store.
Reviewing a customer’s compliance state
A customer’smarketing_state is visible in Audience → Contacts → [Customer Name]. If a customer shows REDACTED, their data has been subject to a deletion request and they should not be included in any outbound messaging.
Related guides
- Opt-in & Consent — Full reference for all consent states and how they are enforced
- Audience — Consent & Opt-outs — Managing consent at the audience level