Data Processing Addendum
Last updated: November 4, 2026
This Data Processing Agreement ("DPA") forms part of the Terms of Service (the "Terms") between: - DigiFist BV (BE 0769.399.149), Ellermanstraat 14, 2000 Antwerpen, Belgium ("DigiFist", processor); and - the customer that has accepted the Terms ("Customer", controller).
It applies to personal data that DigiFist processes on Customer's behalf when it provides Galantis, including Galantis Marketing and Galantis WhatsApp (the "Services").
1. Definitions
1.1 "GDPR" means Regulation (EU) 2016/679. "Personal data", "processing", "controller", "processor", "data subject", "personal data breach" and "supervisory authority" have their GDPR meanings.
1.2 "Data Protection Law" means the GDPR and the national law that applies to the processing, including Belgian law.
1.3 "Customer Personal Data" means the personal data within Customer Data (as defined in the Terms §1) that DigiFist processes on Customer's behalf.
1.4 "Subprocessor" means a third party that DigiFist engages to process Customer Personal Data.
1.5 "SCCs" means the standard contractual clauses of Commission Implementing Decision (EU) 2021/914.
1.6 "Security Incident" means a personal data breach affecting Customer Personal Data.
1.7 "Breach Procedure" means DigiFist's documented internal procedure for Security Incidents described in clause 8.3.
2. Roles and scope
2.1 For Customer Personal Data, Customer is the controller and DigiFist is the processor. Where Customer is itself a processor for someone else, Customer warrants that its instructions are authorised, and DigiFist acts as its subprocessor.
2.2 DigiFist is a controller, outside this DPA, for data it processes for its own purposes: - accounts of Authorized Users; - contracts and billing; - support, including the in-app support chat; - security and access logs; - service records of onboarding steps; - service e-mails to Authorized Users and their delivery records, except the e-mail that hands over a store customer's data (Annex III, Mailtrap); - the records it keeps after a deletion under clause 9.4, from the day the deletion is finished.
The DigiFist Privacy Policy (https://whatsapp.galantis.com/privacy-policy) describes that processing.
2.3 Annex I sets out the details of the processing.
3. Documented instructions
3.1 DigiFist processes Customer Personal Data only on Customer's documented instructions, including for transfers to third countries, unless Union or Member State law requires otherwise. In that case DigiFist informs Customer first, unless that law forbids it.
3.2 The instructions are: - the Terms and this DPA; - Customer's configuration and use of the Services (channels, integrations, automations, campaigns, forms and the AI features it enables); - any further written instruction the parties agree.
3.3 DigiFist tells Customer immediately if, in its opinion, an instruction infringes Data Protection Law.
3.4 Customer is responsible for the lawfulness of the processing it instructs: - a lawful basis for each message; - obtaining, recording and honouring consent and opt-outs; - notices to the people it messages; - the accuracy of data it imports.
Consent that Customer imports counts on Customer's own attestation. DigiFist does not verify it.
4. Confidentiality
People DigiFist authorises to process Customer Personal Data are bound to confidentiality by contract or by law.
5. Security
5.1 DigiFist implements the measures in Annex II.
5.2 DigiFist may update them, provided the overall level of protection does not go down.
6. Subprocessors
6.1 Customer gives a general written authorisation to engage Subprocessors. Annex III lists those engaged at the date of this DPA. Section 6.2 of the Privacy Policy is the public listing.
6.2 DigiFist gives at least 30 days' notice of an intended addition or replacement. It does so by e-mail to the Owner of Customer's workspace and by updating Annex III.
6.3 Customer may object on reasonable data-protection grounds within 14 days of the notice. If good-faith discussion does not resolve the objection, Customer may end the Services before the change takes effect, without penalty. No refund is promised.
6.4 DigiFist imposes on each Subprocessor, by contract, data-protection obligations no less protective than this DPA. DigiFist stays liable to Customer for each Subprocessor.
6.5 Integrations that Customer enables and directs are carried out on Customer's instruction and are not Subprocessors engaged by DigiFist. They are Customer's own Shopify store, a Meta Conversions API destination that Customer configures, Judge.me, and AI apps a member connects.
6.6 Meta. Meta Platforms Ireland Limited is a Subprocessor for the processing of Customer's WhatsApp messages through the WhatsApp Business Platform (Cloud API), under Meta's WhatsApp Business Data Processing Terms. For the WhatsApp service it provides to its own users, WhatsApp is an independent controller under its own terms. That processing is outside this DPA.
7. Data subject requests
7.1 DigiFist assists Customer, as far as possible, by appropriate technical and organisational measures, in answering requests under Chapter III GDPR.
7.2 The Services give Customer these tools:
(a) Contact erasure. An Owner or Admin previews and requests the erasure of a contact. The erasure runs in the background, is audited and is retried on failure. It covers the records the Services hold about that person: - profile and custom fields; - conversations and media; - delivery records; - WhatsApp Flow responses; - AI request content; - measurement events and conversions; - commerce records and form submissions; - the inbound-callback archive; - review and back-in-stock records.
The contact stays erased. The emptied contact record stays as the reference for the records in (b).
(b) Consent and opt-out records are an append-only history per topic. An erasure does not remove them. An erased person's opt-outs keep binding a returning number by value, through a one-way digest.
(c) Shopify customer redaction requests for Customer's store are executed automatically.
(d) Opt-outs are recorded per topic. A marketing opt-out does not stop required order updates. A channel-wide STOP stops every message except required order updates and the one confirmation that the STOP took effect.
7.3 If a data subject contacts DigiFist directly, DigiFist refers them to Customer and forwards the request without undue delay, unless the law requires otherwise.
8. Security incidents and DPIAs
8.1 DigiFist assists Customer with Articles 32 to 36 GDPR, taking into account the nature of the processing and the information available to it.
8.2 Breach notification. DigiFist notifies Customer without undue delay after becoming aware of a Security Incident, and in any event within 72 hours. It notifies by e-mail to the Owner of each affected workspace. The notice gives, as far as known: - the nature of the incident, with the categories and approximate numbers of data subjects and records concerned; - its likely consequences; - the measures taken or proposed; - a contact point.
Information that is not yet known follows in phases, without undue further delay.
8.3 Breach Procedure. DigiFist follows a documented Breach Procedure. It covers: - detection, including incidents its Subprocessors report to it; - assessment of whether Customer Personal Data is affected, and of whose data and how much; - the notice to Customer under clause 8.2; - a record of each Security Incident: the facts, its effects and the remedial action taken.
On request, DigiFist gives Customer the record of a Security Incident that concerns it, so that Customer can document the breach under Article 33(5) GDPR.
8.4 A notification is not an admission of fault.
8.5 DPIAs. On request, DigiFist gives the information about the Services that Customer needs for a DPIA or a prior consultation. Information DigiFist already holds is free. Other help is at a reasonable cost agreed in advance.
9. Deletion or return at the end
9.1 At the end of the Services, DigiFist deletes or returns Customer Personal Data at Customer's choice, and deletes existing copies, unless Union or Member State law requires storage. Clause 9.4 sets out what DigiFist keeps after the deletion, for what purpose and on what basis.
9.2 Return. Customer may export Customer Data where technically feasible (Terms §11.5(d)), before the end of the Services or together with its choice.
9.3 Deletion. The Owner of a workspace deletes it in the Services: - the workspace stops working when the Owner asks; - the Owner can still keep the workspace until the deletion starts, 30 days after the request; - the deletion is finished within 90 days of the request.
The deletion removes the workspace's data from the Services, including its Customer Personal Data, or overwrites it so that no personal data remains, except for the records in clause 9.4. If it was the Owner's last workspace, the Owner's own Galantis account is deleted with it.
Copies in database backups are overwritten when the 7-day recovery window passes.
AI request content follows its own rule (Annex I J), which a deletion does not change: it is erased 90 days after each request. The workspace makes no AI request after the deletion request, so none remains 90 days after it.
9.4 What is kept after deletion, and why. From the day the deletion is finished, DigiFist keeps the records below as a controller, for the purpose and on the legal basis stated with each. It no longer processes them on Customer's instructions. It deletes them when the period ends. Each period counts from the day the deletion is finished, unless the item states its own count.
(a) Consent and opt-out records (consent records, suppression records and preference receipts): 5 years. - Purpose: to answer a dispute or a regulator's question about a message sent through the Services, and to keep an opt-out binding. - Form: an End Recipient's phone number and other contact identifiers are replaced with keyed one-way digests. A record can be found when a person gives their number, but the numbers cannot be read back from the records. - Legal basis: compliance with a legal obligation to prove consent and opt-outs (Article 6(1)(c) GDPR), and DigiFist's legitimate interest in establishing, exercising or defending legal claims (Article 6(1)(f) GDPR).
(b) The workspace activity log: 5 years. It shows which actions were taken in the workspace, by which Authorized User, and when. It includes records of DigiFist staff's access to the workspace, their support notes, and the records of the deletion itself. - Purpose: the security of the Services, and resolving disputes. - Legal basis: DigiFist's legitimate interest in the security of the Services and in accountability for every access to Customer's data (Article 6(1)(f) GDPR).
(c) Billing history and the record that the organisation used its free trial: 10 years, counted to the end of the tenth calendar year after the year in which the deletion is finished. - Purpose: billing history because Belgian accounting law requires it; the trial record so that a free trial is given only once. - Legal basis: for billing history, compliance with a legal obligation (Article 6(1)(c) GDPR); for the trial record, DigiFist's legitimate interest in giving a free trial only once (Article 6(1)(f) GDPR).
(d) Items a kept record refers to. Some items cannot be deleted while a record kept unaltered under (a) to (c) still refers to them: campaigns (with their versions and send batches), message templates, connected messaging accounts, forms (with their versions), WhatsApp Flows (with their related records) and the delivery log of service e-mails. - What is kept: these items whole, with the media files they use and the personal data they contain (for example, the e-mail address a service e-mail was sent to). - How long: for as long as such a record refers to them. - Legal basis: the basis of the record that refers to them.
9.5 Store data:
(a) Customer can erase a disconnected Shopify store's data at once with "Delete all Shopify data now" in the Services. Only the Owner or an Admin can do this. It needs a typed confirmation of the store's domain, is audited, and cannot be undone.
(b) Uninstalling the Galantis app disconnects the store. It does not by itself delete data. The data stays until Customer erases it, deletes the workspace, or an approved post-uninstall window passes.
(c) A Shopify shop redaction request is recorded and acknowledged, not executed automatically.
(d) After a store-level deletion, the Services keep a one-way digest that links a customer's number to the store customer. It stops a later message from re-creating the erased person.
(e) Payment failure never causes deletion.
10. Information and audits
10.1 DigiFist makes available the information needed to demonstrate compliance with Article 28 GDPR and this DPA.
10.2 DigiFist allows for and contributes to audits by Customer, or by an independent auditor Customer mandates, on these terms: - at least 30 days' written notice; - at most once per 12 months, unless a Security Incident or a supervisory authority requires more; - under confidentiality; - with minimal disruption; - each party bears its own costs.
10.3 DigiFist may first answer with written information or documentation. No security certification of DigiFist or of any Subprocessor is claimed.
11. International transfers
11.1 DigiFist's hosting platform stores Customer Personal Data in the EU: Laravel Cloud, region eu-central-1. Some Subprocessors in Annex III may process data outside the EEA.
11.2 A transfer to a third country without an adequacy decision happens only under a Chapter V safeguard. For Subprocessors that is the SCCs (Module 3) or another valid mechanism, such as the EU-US Data Privacy Framework. Laravel Cloud and Cloudflare process under their data processing agreements, with the SCCs for any transfer outside the EEA. Annex III states each Subprocessor's safeguard. On request, DigiFist gives further detail of the safeguard for any Subprocessor.
11.3 Where Customer is outside the EEA and DigiFist returns data to it, the SCCs (Module 4) apply where required.
11.4 If a mechanism becomes invalid, DigiFist takes reasonable steps to put an alternative in place or to suspend the transfer.
12. Liability
Liability under this DPA follows the limitations in Terms §15, except where Data Protection Law does not allow a limitation.
13. Duration, precedence and changes
13.1 This DPA applies while DigiFist processes Customer Personal Data. Clauses 9 and 10 survive until deletion or return is complete.
13.2 In case of conflict, the order is: the SCCs, where they apply; then this DPA; then the Terms.
13.3 DigiFist may update this DPA for changes in law or in the Services, with notice under Terms §20, provided protection does not go down.
14. Governing law
Belgian law applies. The courts competent for Antwerp have exclusive jurisdiction, unless mandatory law says otherwise. The SCCs keep their own law and forum clauses.
Annex I: Details of the processing
A. Parties. - Controller: Customer, as identified in its account. - Processor: DigiFist BV, address as above. Contact: support@digifist.com, subject "Galantis Privacy Request".
B. Subject matter. Providing the Services: communication with Customer's own customers and contacts, and the management and automation of those interactions, including through Meta's WhatsApp Business Platform. It also covers the store synchronisation, forms, measurement, reviews and AI features Customer enables.
C. Duration. The term of the Terms, plus the time needed under clause 9.
D. Nature of the processing. Collection, recording, storage, organisation, retrieval, use, transmission and erasure, in particular: - hosting in the EU; - sending and receiving WhatsApp messages, templates, media and Flows; - recording consent and opt-outs per topic and checking them before every send; - synchronising a Shopify store Customer connects, and answering its customer data requests; - running automations, campaigns and opt-in forms; - storefront and Web SDK measurement, with conversion delivery only for events that have marketing consent; - collecting reviews into Customer's Judge.me account; - AI-assisted building of automations and Flows, and AI evaluation, where enabled; - erasure on Customer's instruction.
E. Purpose. Only to provide the Services under the Terms and Customer's instructions.
F. Data subjects. - Customer's customers, prospects and contacts. This includes people who message Customer on WhatsApp, store customers, form submitters, reviewers and back-in-stock subscribers. - Storefront visitors whose events Customer collects. - Customer's Authorized Users, where their data appears in Customer Data.
G. Personal data. - Contact data: WhatsApp number, name, profile name, language, country and custom fields. - Consent and opt-out records, with Customer's attestation for imports and the submission proof for forms. - Message data: content, template variables, media, statuses and Flow responses. - Store data: customer name, e-mail, phone, orders, fulfilments, checkouts and opt-in state. - Import files. - Measurement data: anonymous events and person-linked conversions. Clicks on tracked links in messages are recorded per contact by redirect only, without a pixel or a cookie. - Review data. - AI request content, where AI is enabled. - Automation run records and public API request logs. - Approval requests from API keys and AI apps: the key or app that asked and its name at that moment, the Authorized User behind it, the action it asked for and its settings, the campaign, automation or Flow version it concerns, the deadline, and who answered and when.
H. Special categories. The Services are not designed for special-category or criminal-offence data, and Customer should not use them for it. Free text written by the people Customer messages may contain such data by chance.
I. Frequency. Continuous.
J. Retention while the Services run. Customer can erase earlier. Clause 9 applies at the end.
Anonymous measurement events: 90 days, then identifiers removed
AI request content: 90 days
Automation step detail / run summaries: 90 days / 365 days
Public API request logs: 30 days
Approval requests from API keys and AI apps: 90 days after the request ends
Inbound provider callback bodies: 30 days; the body is emptied and the metadata row stays
Rejected inbound deliveries: 30 days
Uploaded contact-import files: 30 days after the import's last change
Failed background jobs: 30 days
WhatsApp Flow tokens: Valid for 72 hours
Preference-centre links: Valid for 30 days
Message media: As long as the message exists
Consent records and form submission proof: Append-only; a contact erasure does not remove them
Conversion-destination identifiers: Held in memory for delivery, not stored
Hosting platform logs (application, access and system logs): 7 days, then deleted by Laravel Cloud. The Services write logs to no other store, and secrets are removed from every log line
Everything else: Until Customer erases it or clause 9 applies
K. Subprocessors. See Annex III.
Annex II: Technical and organisational measures
Only measures built into the Services are listed.
Tenant isolation. One shared database. Every record, index, foreign key and repository is scoped to the customer's workspace.
Two secret classes. Platform secrets sit in approved secret stores. Customers' provider credentials sit in an encrypted credential store. Neither reaches source code, clients, fixtures or telemetry.
Encryption in transit. Only declared HTTPS endpoints are public.
Storage.
The production file bucket is private and in the EU jurisdiction.
The cache is not public.
Encryption at rest is not claimed.
Verified ingress. Provider callbacks are verified before parsing. The credentials bound to the receiving route decide the workspace.
Network boundaries. Clients use the versioned API only and hold no database, cache, storage or provider credential. Non-production environments use sandbox providers only.
Access control. Server-side roles for every feature. Every staff support session records the actor, reason, time and scope, and is audited.
Logging and redaction. Secrets are redacted on every log channel. No Meta media URL is stored.
WhatsApp Flows. Private keys stay in the secret store. Replays are rejected, and decrypted material never reaches logs, traces or archives.
Consent enforcement. Topic-scoped suppression applies to every proactive send, and a merge of contacts never weakens it.
Recovery.
The database has point-in-time recovery with a 7-day window.
Restores are carried out by DigiFist's owner after a preview of their impact.
Recovery targets: data loss of at most 300 seconds (RPO) and a restore within 3,600 seconds (RTO).
Audited destructive actions. Erasure runs in the background, is recoverable where possible, is preceded by an impact preview, and is audited.
Payment failure never deletes data.
AI controls, where enabled.
AI requests are immutable, and production AI stays off without legal approval and limits.
Safety limits: 200 invocations a day, 2,048 output tokens.
Security incidents. A documented Breach Procedure (clause 8.3).
Certifications: none claimed.
Annex III: Subprocessors
Laravel Cloud
Purpose: Hosting of the Galantis API, background workers, scheduler, PostgreSQL database, cache and file storage. Laravel Cloud's own edge network, in front of the API and Web SDK hosts, is part of this service
Personal data: All Customer Personal Data
Location: European Union: region
eu-central-1(on AWS), as configured; file storage in the EU jurisdictionSafeguard: Hosted in the EU. The SCCs for any onward transfer outside the EEA
Contract: Laravel Cloud's data processing agreement
Cloudflare
Purpose: Hosting of the Galantis web front ends (the merchant app, the admin app and the developer pages), with their TLS certificates. The front ends hold no Customer Personal Data: the browser fetches it from the API, which Laravel Cloud serves. Cloudflare also runs the Galantis MCP server, through which the AI apps a member connects (clause 6.5) reach Galantis. The requests and answers of those apps pass through it, including Customer Personal Data where the app's level of access allows it. The MCP server does not store them. For each call it writes one technical log line: the tool, the result, how long it took and the names of the fields sent, never their values. In this release, apart from the MCP server, Cloudflare does not carry the API or Web SDK traffic
Personal data: Request data (such as IP address and browser details) of people who load the front ends, including Customer's Authorized Users. The Customer Personal Data in the requests and answers that AI apps send and receive through the MCP server, where the app's level of access allows it (for example contacts and their fields, each contact's consent, conversations and messages, and events linked to a contact, such as orders)
Location: Cloudflare's global network; no processing region is configured
Safeguard: The SCCs
Contract: Cloudflare's data processing agreement
Meta Platforms Ireland Limited (WhatsApp Business Platform, Cloud API)
Purpose: Sending and receiving Customer's WhatsApp messages, templates, media and Flows; connecting Customer's existing Meta catalog. For WhatsApp's own service, see clause 6.6
Personal data: WhatsApp numbers, profile names, message content, media, Flow responses, statuses, account identifiers
Location: As Meta's WhatsApp Business Data Processing Terms provide
Safeguard: As Meta's WhatsApp Business Data Processing Terms provide
Contract: Meta's WhatsApp Business Data Processing Terms
OpenAI (Responses API)
Purpose: The AI features in Annex I D, only where Customer enables them
Personal data: Prompts, outputs, usage metadata
Location: EEA data is processed by OpenAI Ireland Limited
Safeguard: OpenAI DPA §4.1: the SCCs or an adequacy decision for onward transfers
Contract: DPA signed 2026-09-14
Intercom
Purpose: Support chat in the Galantis app, only for Customer Personal Data that Customer chooses to share in the chat
Personal data: What Customer types into the chat about its own customers
Location: United States
Safeguard: EU-US Data Privacy Framework, its UK Extension and the Swiss-US Data Privacy Framework; the SCCs if the Data Privacy Framework no longer applies
Contract: Intercom's data processing agreement, part of its agreement
Mailtrap
Purpose: Delivery of the one service e-mail that carries Customer Personal Data: the answer to a Shopify customer data request, sent as an attached export to the users of Customer's workspace who manage its members
Personal data: The store customer's data in the attached export; the recipients' e-mail addresses
Location: United States (Railsware Products Studio LLC, Pasadena, California; hosted on AWS and Google Cloud)
Safeguard: EU-U.S. Data Privacy Framework (Mailtrap DPA clause 7.2, signed 2026-09-24); if the DPF ceases to apply, the EU Standard Contractual Clauses Module 2 and the UK Addendum of that DPA (clause 7.3)
Contract: DPA signed
Not listed: - Laravel Nightwatch (application monitoring). It does not run in production. It is added under clause 6.2 before it is switched on.
Not Subprocessors (for completeness; not part of Annex III): - DigiFist's own processors, for its controller processing (clause 2.2): - Mailtrap, for every other service e-mail: sign-in links, invitations, account and service notifications, staff alerts and payment notices. These go to Authorized Users and DigiFist staff and carry no data of the people Customer messages. - Stripe: direct subscriptions. - Shopify: App Store billing. - Intercom, for the Authorized User's own identity in the chat (member id, e-mail, name, language). - Integrations Customer enables (clause 6.5).