Mersail Data Processing Agreement
Version: 1.0
Effective date: 16 November 2026
Last updated: 10 November 2026
This Data Processing Agreement ("DPA") forms part of the Mersail Merchant Agreement (the "Agreement") between the Merchant and Mersail. It meets article 28 of Regulation (EU) 2016/679 (the "GDPR"). The Merchant accepts it in electronic form together with the Agreement (GDPR art. 28(9)).
1. Definitions
1.1 Words defined in the Agreement have the same meaning here. In this DPA:
- Merchant means the business that accepted the Agreement. It is the controller of Customer Personal Data.
- Mersail means the provider identified in clause 1 of the Agreement. It is the processor of Customer Personal Data.
- Data Protection Law means all laws on personal data that apply to the processing, including the GDPR; the Italian Codice privacy (D.Lgs. 30 giugno 2003, n. 196); Directive 2002/58/EC and the national laws implementing it; the UK GDPR, the UK Data Protection Act 2018 and the UK Privacy and Electronic Communications Regulations 2003; the Swiss Federal Act on Data Protection; and US state privacy laws such as the California Consumer Privacy Act, each where it applies.
- controller, processor, data subject, personal data, processing, personal data breach and supervisory authority have the meanings given in the GDPR.
- Customer Personal Data means the personal data described in Annex I that Mersail processes on the Merchant's behalf.
- Sub-processor means a third party that Mersail engages to process Customer Personal Data.
- Restricted Transfer means a transfer of Customer Personal Data to a country outside the EEA (or outside the UK or Switzerland, for data subject to their laws) that Data Protection Law allows only with a safeguard.
- SCCs means the standard contractual clauses in the Annex to Commission Implementing Decision (EU) 2021/914.
- UK Addendum means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner (version B1.0), as amended or replaced.
- DPF means the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework.
- Notice Email has the meaning given in the Agreement: the Store's contact email address in Shopify, or another address the Merchant gives in the App.
2. Roles and scope
2.1 The Merchant is the controller of Customer Personal Data. If the Merchant processes it as a processor for another controller, the Merchant confirms that this controller has authorised this DPA, Mersail acts as a sub-processor, and the Merchant remains Mersail's only point of contact.
2.2 Mersail processes Customer Personal Data as the Merchant's processor, as described in Annex I.
2.3 Mersail is an independent controller, and this DPA does not apply, for personal data it uses to run its relationship with the Merchant: account and contact details, acceptance records, billing and plan data, support correspondence and security records. The Privacy Policy covers that data.
2.4 This DPA applies for as long as Mersail processes Customer Personal Data, including after the Agreement ends and until deletion under clause 12.
2.5 The Merchant's obligations and rights as controller are those in this DPA, in particular clauses 3 (instructions), 6.5 (objection to Sub-processors), 8 and 9 (help from Mersail), 10 (breach notices), 12 (deletion or return) and 13 (information and audits).
3. The Merchant's instructions
3.1 Mersail processes Customer Personal Data only on the Merchant's documented instructions, including for transfers to third countries. The only exception is where EU or Member State law that applies to Mersail requires other processing. In that case Mersail tells the Merchant before processing, unless that law forbids it on important grounds of public interest (GDPR art. 28(3)(a)).
3.2 The Merchant's documented instructions are:
- the Agreement and this DPA;
- the Merchant's configuration and use of the App: installing it and granting its Shopify permissions, onboarding settings, creating and approving Campaigns, choosing audiences, turning abandoned-cart recovery and AI replies on or off, brand settings and FAQ, sending replies, using the emergency stop, asking for an export or switching under Agreement clause 21.8, and uninstalling; and
- other written instructions the Merchant sends to privacy@mersail.com that are consistent with the Agreement.
If an instruction needs a feature the Service does not offer, Mersail may decline it. The Merchant may then end the Agreement by uninstalling the App.
3.3 Mersail will immediately tell the Merchant if, in its opinion, an instruction infringes Data Protection Law. Mersail may stop following that instruction until the Merchant confirms or changes it.
3.4 The Merchant is responsible for:
- making sure its instructions comply with Data Protection Law;
- having a lawful basis for the processing and, where the law requires, each Customer's consent to marketing email;
- the accuracy of the consent states in its Store; and
- giving Customers the information GDPR arts. 13 and 14 require, including that it uses processors (among them an AI provider that stores data in the United States) to personalise emails from purchase history and to handle replies, and that Customers may object to direct marketing and related profiling (GDPR art. 21).
3.5 The Merchant will not instruct Mersail to process special categories of personal data (GDPR art. 9) or data about criminal convictions and offences (GDPR art. 10). Customer replies may still contain such data if a Customer writes it. Mersail processes that data only as part of sorting the reply with rules, answering, holding and deleting it, as described in Annex I.
3.6 The Service profiles Customers for direct marketing (segments and product recommendations) and sorts their replies with rules (not with AI; the AI only writes answers to product questions). It is not designed to make decisions that produce legal effects on Customers or similarly significantly affect them (GDPR art. 22), and the Merchant will not use it for such decisions, for example to refuse a Customer goods, services or credit.
4. Confidentiality
4.1 Mersail ensures that every person it authorises to process Customer Personal Data has committed to confidentiality or is under a statutory duty of confidentiality (GDPR art. 28(3)(b)).
4.2 At the date of this DPA, the only person with access to Customer Personal Data is the provider himself. Any employee or contractor who needs access in future will be bound to confidentiality in writing before access, and will get only the access they need.
4.3 Software tools the provider uses to operate the Service, such as AI coding assistants and connectors with access to the production email, hosting or database accounts, are either kept away from Customer Personal Data or used only under terms that forbid training on the data or with training turned off, and are listed in Annex III.
4.4 Mersail does not disclose Customer Personal Data except as this DPA allows, as the law requires (telling the Merchant first where the law allows), or to Shopify where Shopify's terms require it for data breaches, audits or deletion.
5. Security
5.1 Mersail takes the technical and organisational measures in Annex II (GDPR arts. 28(3)(c) and 32).
5.2 Annex II separates measures that are in place in the code (Part A) from measures to be in place before production launch (Part C). Part D lists measures that are not in place.
5.3 Mersail may change the measures, as long as the overall level of security does not go down.
5.4 The Merchant is responsible for the security of its own Shopify account and staff access, for the settings it chooses, and for deciding whether Annex II meets its needs.
5.5 Mersail holds no security certification, such as ISO/IEC 27001 or SOC 2. Some Sub-processors hold certifications; those belong to them, not to Mersail.
6. Sub-processors
6.1 Authorisation. The Merchant gives Mersail general written authorisation to engage Sub-processors. The Sub-processors in Annex III are authorised on acceptance.
6.2 Contracts. Mersail engages each Sub-processor under a written contract that imposes data protection obligations giving sufficient guarantees under GDPR art. 28(4), limits the Sub-processor's processing of Customer Personal Data to providing its service to Mersail, and requires it to keep the data secure and confidential. Known deviations: Resend and Render process their own service usage data (such as the source and destination of communications, and activity logs) as independent controllers under their terms. The data processing terms of Render, Supabase, Resend and Anthropic are incorporated into their terms of service and apply to Mersail's accounts.
6.3 Liability. Mersail remains fully liable to the Merchant for each Sub-processor's performance of its obligations.
6.4 Notice of changes. Mersail will notify the Merchant by email to the Notice Email, and in the App where possible, at least 10 days before:
- a new or replacement Sub-processor starts processing Customer Personal Data; or
- Mersail sends a category of Customer Personal Data to a listed Sub-processor that did not receive it before.
Adding any AI Provider other than Anthropic, including as a fallback when Anthropic is unavailable, is a change under point 1.
The notice will give the Sub-processor's name, service, the data involved, its location and the transfer mechanism. Mersail will publish the updated Annex III at https://app.mersail.com/privacy (section 4.1 of the Privacy Policy) and with this DPA at https://app.mersail.com/terms.
6.5 Objection. The Merchant may object in writing to privacy@mersail.com, within the notice period, on reasonable data protection grounds. The parties will discuss the objection in good faith. If they cannot resolve it, Mersail may avoid using that Sub-processor for the Merchant's data where this is feasible. Otherwise the Merchant may end the Agreement by uninstalling the App before the change takes effect, without penalty and with a refund through Shopify of fees prepaid for the period after that date.
6.6 Emergencies. If a Sub-processor suddenly stops its service, or a security problem requires an immediate change, Mersail may shorten the notice period in clause 6.4. Mersail still gives notice before the new Sub-processor receives any Customer Personal Data. Until then, Mersail pauses the affected processing (for example with the emergency stop) or uses only Sub-processors already listed in Annex III for that processing. The Merchant keeps its rights under clause 6.5, and the objection period runs from the notice.
6.7 Sub-processors' own providers. Sub-processors use their own sub-processors, listed on the pages linked in Annex III. For example, Resend lists Amazon Web Services for sending, and Supabase runs its databases on Amazon Web Services.
6.8 List on request. Mersail will give the Merchant, or Shopify, a current list of its service providers on request.
7. International transfers
7.1 Locations. Mersail is established in Italy. The Service's application and database run in Frankfurt, Germany. Resend stores account data, email metadata and logs in the United States. Anthropic stores data in the United States and may run requests in any geography where it has infrastructure; the model the Service uses cannot be limited to a region. Supabase contracts through a company in Singapore, and Sub-processors may give support and operations staff outside the EEA access to the systems they run for Mersail. Annex III gives the location and the transfer mechanism for each Sub-processor. By accepting this DPA, the Merchant instructs Mersail to make these transfers.
7.2 Transfers to Sub-processors. Mersail ensures that each Restricted Transfer to a Sub-processor is covered by:
- an adequacy decision, including Commission Implementing Decision (EU) 2023/1795 on the EU-U.S. Data Privacy Framework for Sub-processors on the Data Privacy Framework List; or
- the SCCs, in the module that fits, agreed with the Sub-processor or with its contracting entity in the EEA for onward transfers; or
- another safeguard under GDPR art. 46.
7.3 Merchants outside the EEA. Where the Merchant is outside the EEA and its processing is not subject to the GDPR, and Mersail transfers Customer Personal Data back to the Merchant (for example through the App, exports, data-request emails or held replies), the parties agree Module Four (processor to controller) of the SCCs, incorporated by reference, with these choices: clause 7 (docking clause) applies; the option in clause 11(a) does not apply; clause 17: Italian law; clause 18: courts of Ravenna, Italy; Annex I.A and I.B of the SCCs are completed by Annex I of this DPA. Where the Merchant is outside the EEA but its processing is subject to the GDPR (GDPR art. 3(2)), the SCCs cannot be used; the Merchant is bound by the GDPR directly, and this DPA applies as the contract between the parties.
7.4 United Kingdom. The Service is not offered to Merchants established in the United Kingdom, and it does not store, keep the orders of, or email Customers whose default address in Shopify is in the United Kingdom (Agreement clause 3.3). Where Customer Personal Data is still subject to UK data protection law, for example a Customer with no address on file, onward transfers to Sub-processors certified to the DPF UK Extension rely on the UK Data Protection (Adequacy) (United States of America) Regulations 2023. Other onward transfers rely on the SCCs as amended by the UK Addendum incorporated in each Sub-processor's data processing terms (Annex III), whose tables those terms complete.
7.5 Switzerland. For personal data subject to Swiss law, the transfer from a Merchant in Switzerland to Mersail in the EEA relies on Switzerland's recognition of the EEA as adequate. Onward transfers to Sub-processors certified to the Swiss-U.S. DPF rely on it; other onward transfers rely on the SCCs with the adjustments the Swiss Federal Data Protection and Information Commissioner requires, as incorporated in each Sub-processor's data processing terms. For those transfers, "Member State" in the SCCs includes Switzerland, and the competent authority is the Federal Data Protection and Information Commissioner.
7.6 If a mechanism fails. If a transfer mechanism is invalidated or stops applying, for example if the DPF is struck down, Mersail will rely on another mechanism (such as the SCCs in the Sub-processor's terms) and tell the Merchant. If no mechanism is available, the parties will discuss the next steps, and the Merchant may end the Agreement by uninstalling.
7.7 Transfer assessments. Mersail has assessed the transfers in Annex III; Annex IV summarises that assessment. Mersail reviews it when a Sub-processor, its terms or the relevant law changes, and at least once a year. Mersail will give the Merchant the information it reasonably needs for its own transfer impact assessment, free of charge.
8. Help with data subject requests
8.1 Taking into account the nature of the processing, Mersail helps the Merchant, by appropriate technical and organisational measures and as far as possible, to respond to requests from data subjects under GDPR arts. 12 to 22 (GDPR art. 28(3)(e)).
8.2 Requests sent to Mersail. If a data subject writes to Mersail about Customer Personal Data, Mersail will forward the request to the Merchant within 5 Business Days and will not answer it on the merits unless the Merchant authorises it or the law requires it. The exception is unsubscribing: when a Customer unsubscribes through the link in an email, Mersail applies it straight away, on the Merchant's standing instruction.
8.3 Shopify privacy requests. Shopify sends the App requests about Customer data. Mersail handles them as follows:
- Customer data request (
customers/data_request). Mersail will give the Merchant a copy of the Customer Personal Data it holds about that Customer, in a structured, commonly used, machine-readable format (JSON), within 10 Business Days of receiving the request, by email to the Notice Email. The App sends it automatically on receipt and retries a failed delivery. The copy covers the Customer record and derived profile, orders and line items, emails, engagement events, replies, abandoned-cart records, product recommendations and AI insights that name the Customer. - Customer deletion request (
customers/redact). Mersail deletes that Customer's personal data from the Service's database within 30 days of receiving the request; the App normally does this on receipt. Deletion covers the Customer record, orders and line items, emails sent to the Customer and their engagement events, product recommendations, replies and abandoned-cart records, and stored AI campaign insights that name the Customer. Copies held by Sub-processors are kept no longer than the periods in Annex III. - Store deletion request (
shop/redact). Clause 12 applies.
8.4 Other requests. For requests to access, correct, erase, restrict or port data, or objections, the Merchant may write to privacy@mersail.com. Mersail will help within 10 Business Days.
- Customer names, email addresses and consent states come from Shopify. The Merchant should correct them in Shopify, and the App picks up the change at the next sync (at onboarding, each time the App dashboard is opened, and when the Merchant clicks "Refresh customer sync"). Mersail will correct other Customer Personal Data on request.
- When a Customer unsubscribes in the Service, Mersail stops Campaign and abandoned-cart emails to that Customer from that Store at once, including during a Campaign that is already sending. The Service does not yet write the unsubscribe back to the Customer's email marketing consent in Shopify (Agreement clause 7.4), so the Merchant must update its Shopify records and its other tools. Opt-outs made in Shopify reach the Service at the next sync (Agreement clause 7.3).
8.5 Cost. Help under this clause and clause 9 is free. Only where the Merchant's requests for help are manifestly excessive, in particular because they are repetitive, may Mersail charge a reasonable fee based on its time, and only if the Merchant agrees the fee in writing before the work starts. Mersail never charges for handling Shopify privacy requests (clause 8.3) or unsubscribes.
9. Help with security, impact assessments and consultations
9.1 Taking into account the nature of the processing and the information available
to it, Mersail helps the Merchant meet its obligations under GDPR arts. 32 to 36
(GDPR art. 28(3)(f)). Mersail does this by providing this DPA and its Annexes, a
summary of its security measures (based on SECURITY.md, sent on request), answers to reasonable security questionnaires, and the information
the Merchant reasonably needs for a data protection impact assessment or a prior
consultation with a supervisory authority.
9.2 The Service involves profiling Customers for marketing and the use of AI. The Merchant is responsible for deciding whether it needs a data protection impact assessment.
10. Personal data breaches
10.1 Notice to the Merchant. Mersail will notify the Merchant without undue delay after becoming aware of a personal data breach affecting Customer Personal Data (GDPR art. 33(2)). This includes a breach at a Sub-processor, counted from when Mersail becomes aware of it. If Mersail does not yet have all the information in clause 10.3, it sends a first notice as soon as it can and the rest in stages.
10.2 How. Notice goes to the Notice Email, and to the App where possible.
10.3 Content. The notice gives, as far as the information is available (and in stages if needed): the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact point (privacy@mersail.com).
10.4 Response. Mersail takes reasonable steps to contain, investigate and mitigate the breach, keeps evidence, and cooperates with the Merchant. Mersail will not notify a supervisory authority or data subjects on the Merchant's behalf unless the Merchant asks in writing or the law requires Mersail to do so.
10.5 Shopify. Shopify's terms require Mersail to notify Shopify of any actual or suspected breach of Merchant Data within 24 hours of becoming aware of it, and to answer Shopify's questions. The Merchant authorises Mersail to share information about the breach and the Merchant's affected data with Shopify for that purpose.
10.6 Not an admission. A notice under this clause is not an admission of fault.
10.7 The Merchant's duties. The Merchant remains responsible for its own notifications, including to its supervisory authority (GDPR art. 33(1)) and to data subjects (GDPR art. 34).
11. AI transparency (EU AI Act)
11.1 Roles. For the AI features of the Service, Mersail is the provider and the Merchant is the deployer, within the meaning of Regulation (EU) 2024/1689 (the "AI Act"), art. 3. Article 50 of the AI Act applies from 2 August 2026.
11.2 AI replies. Mersail will design AI replies so that Customers are clearly told, at the latest with their first AI reply, that the reply was written by an AI system on the Merchant's behalf, unless this is obvious (AI Act art. 50(1) and (5)). Every AI reply ends with a notice, in the reply's language, that it was written by an AI assistant for the Merchant's Store. The Merchant's own replies, which it writes and sends in the App, are not labelled.
11.3 Marking AI-generated emails. Mersail marks every email whose subject line or text the AI system generated, including Campaign emails and AI replies, in a machine-readable format so that it can be detected as AI-generated (AI Act art. 50(2)). Each such email carries a message header stating that its content was generated with AI and naming Mersail as the provider, and its HTML part carries a matching metadata tag. Emails written entirely by the Merchant are not marked. Mersail does not add a visible AI notice to Campaign emails: they are not text published to inform the public on matters of public interest (AI Act art. 50(4)).
11.4 The Merchant's part. The Merchant will not remove, hide or change these notices or marks. The Merchant is responsible for its own obligations as deployer, including AI Act art. 50(4) where it applies, and for the AI literacy of its staff (AI Act art. 4).
11.5 Information. Mersail will give the Merchant information about how the AI features work, their limits, and the data they use (Annex III).
12. Deletion or return at the end
12.1 During the Agreement. Mersail applies the retention periods in Annex I, through an automated job that runs every day.
12.2 Return. At the Merchant's choice, Mersail returns Customer Personal Data before deletion, through the export and switching process in clause 21.8 of the Agreement. The Merchant makes that choice by a request while the App is installed. Once the request is made, the retrieval period in that clause applies, and Mersail keeps the data until it ends even if the Merchant uninstalls the App. If the Merchant uninstalls without a request, Mersail treats that as the Merchant's choice to have the data deleted (GDPR art. 28(3)(g); Regulation (EU) 2023/2854 (the "Data Act"), art. 25). The Merchant is told this before it accepts this DPA and in the App's settings. If the Merchant reinstalls the App before deletion runs, clause 12.4 applies and it can still make a request.
12.3 Deletion. When the Merchant uninstalls the App, Mersail immediately clears
the Store's Shopify access token and the email-sending key, and the Service stops
sending. Unless clause 12.2 keeps the data longer, Mersail deletes all Customer
Personal Data and other Merchant Data from the Service's database when Shopify
sends its store deletion request (shop/redact, normally about 48 hours after
uninstall), and in any case by day 22 after the uninstall, even if that request
never arrives. The 22 days run from Shopify's uninstall notification or, if that
notification is lost, from when Mersail's daily check finds that the App was
uninstalled.
12.4 Reinstalling. If the Merchant reinstalls the App before deletion runs, data not yet deleted is kept and this DPA continues.
12.5 Copies outside the database. Mersail makes sure that every other copy is gone within 30 days after uninstall:
- Backups. The database plan Mersail uses keeps no backups and no point-in-time recovery. If Mersail moves to a plan with backups, it will keep them for no more than 7 days, so that copies expire by day 30, and before using a restored database it will delete again any data that had already been deleted.
- Application logs. Application logs are kept for 7 days. They hold request metadata and identifiers, with email addresses and phone numbers masked.
- Sub-processors. Sub-processors keep copies for no longer than the periods in Annex III. Those periods run from when the Sub-processor received the data. A reply that arrives after uninstall is held without being sent to the AI Provider, and is deleted with the Store's data. Where a Sub-processor offers deletion on request, Mersail uses it.
12.6 Exceptions. The only exceptions to clauses 12.3 and 12.5 are:
- data the law requires Mersail to keep. Mersail keeps it confidential, uses it only for that legal purpose and deletes it when the obligation ends. Mersail does not expect Customer Personal Data to fall in this category;
- data kept for a retrieval period under clause 12.2; and
- a copy a Sub-processor keeps longer under its terms in a case Annex III describes (for example, content its safety systems flag).
12.7 If deletion cannot be done in time. If a copy cannot be deleted within 30 days after uninstall, including in the cases in clause 12.6(2) and (3), Mersail promptly tells the Merchant and Shopify (Shopify API Terms, section 6.2.3), and keeps protecting the data under this DPA until it is deleted.
12.8 Confirmation. Mersail will confirm deletion in writing on request.
13. Information and audits
13.1 Mersail makes available to the Merchant all information necessary to demonstrate compliance with GDPR art. 28, and allows and contributes to audits, including inspections, by the Merchant or an auditor it appoints (GDPR art. 28(3)(h)).
13.2 Documents first. Mersail first provides this DPA and its Annexes, its security summary, its Sub-processor list, and Sub-processor certifications or audit reports where it may share them. It also answers one reasonable written questionnaire every 12 months, within 30 days, and more often after a personal data breach or at a supervisory authority's request.
13.3 Audits. If the documents are not enough to demonstrate compliance, or a supervisory authority requires it, or after a personal data breach affecting the Merchant's data, the Merchant may audit Mersail on these terms:
- at least 30 days' written notice, with the scope agreed in advance;
- remotely by default (documents, video calls, screen sharing), and on site only where a remote audit is not enough;
- during Business Days and normal working hours;
- at most once every 12 months, except after a breach or at an authority's request;
- by the Merchant or an independent auditor bound by confidentiality;
- without access to other merchants' data or anything that would weaken security; and
- at the Merchant's own cost. Mersail's own time is free up to one Business Day per audit. Beyond that, Mersail may charge a reasonable daily rate agreed in writing before the audit, unless the audit finds that Mersail materially breached this DPA.
13.4 Sub-processors. Audits of Sub-processors take place through their reports and the audit rights in their terms.
13.5 Shopify. Shopify may audit Mersail under Shopify's terms.
13.6 Nothing in this clause limits the powers of a supervisory authority.
14. US state privacy laws
14.1 This clause applies where the Merchant is a "business" and Customer Personal Data includes "personal information" under the California Consumer Privacy Act (Cal. Civ. Code §1798.100 and following) and its regulations (11 CCR §7051), or under a similar US state law, such as those of Colorado, Connecticut, Utah, Virginia and the other states with comprehensive consumer privacy laws ("US State Privacy Laws").
14.2 Mersail acts as a "service provider" (or "processor"). It processes personal information only for the specific business purposes in Annex I, section B.6, and only on the Merchant's instructions in clause 3. The Merchant discloses the personal information to Mersail only for those limited and specified purposes. Annex I sets out the nature and purpose of the processing, the types of data and the duration.
14.3 Mersail will not:
- sell or share the personal information (as those terms are defined in the CCPA);
- retain, use or disclose it for any purpose other than those business purposes, or outside its direct business relationship with the Merchant; or
- combine it with personal information from other sources, including other merchants, except as the CCPA allows.
14.4 Mersail will comply with the obligations that apply to it and give the same level of privacy protection the law requires of the Merchant. Mersail will tell the Merchant within 5 Business Days if it decides it can no longer meet these obligations. The Merchant may take reasonable and appropriate steps to check that Mersail uses the personal information in a manner consistent with the Merchant's obligations (clause 13), and, on notice, to stop and fix unauthorised use, including by suspending processing or uninstalling the App.
14.5 Mersail will help with consumer requests under clause 8, keeps every person who processes the personal information under a duty of confidentiality (clause 4), deletes or returns it at the end (clause 12), and binds its Sub-processors to equivalent terms under a written contract, after notice and a chance to object under clause 6.
14.6 Mersail certifies that it understands and will comply with the restrictions in this clause.
15. Liability
15.1 Each party's liability under this DPA is subject to clause 23 of the Agreement.
15.2 Nothing in this DPA or the Agreement limits either party's liability to data subjects under GDPR art. 82, or its liability under the SCCs. Where both parties are liable to a data subject for the same damage, each may recover from the other the part that corresponds to the other's responsibility (GDPR art. 82(5)).
15.3 Clause 23.1 of the Agreement applies to this DPA. In particular, to the extent a breach of Data Protection Law is a breach of obligations arising from public-order rules under art. 1229(2) c.c., the cap in clause 23.3 of the Agreement does not limit liability for it.
16. Duration, precedence and law
16.1 This DPA starts when the Agreement starts and ends when all Customer Personal Data has been deleted under clause 12.
16.2 For personal data, the SCCs (where they apply) prevail over this DPA, and this DPA prevails over the Agreement.
16.3 This DPA may be changed under clause 25 of the Agreement. Changes that the law requires, such as new standard contractual clauses or a new UK Addendum, take effect as the law requires.
16.4 This DPA is governed by the law and jurisdiction clause of the Agreement (clause 27), except that the SCCs are governed by the choices in clause 7.3.
Annex I: Details of the processing
A. The parties
| Controller | Processor | |
|---|---|---|
| Name | The Merchant, as identified in the acceptance record (Agreement clause 3.1): business name as typed at acceptance, Shopify store domain | Alberto Clemente, self-employed sole trader (lavoratore autonomo, Partita IVA IT02831350398), trading as Mersail |
| Address | Business address as typed at acceptance | Viale della Repubblica 6, 48026 Russi (RA), Italy |
| Contact | Notice Email; name and role of the person who accepted, as typed at acceptance | privacy@mersail.com |
| Activity | Running an online store on Shopify and marketing to its customers | Providing the Mersail app |
| Role | Controller (or processor for another controller, clause 2.1) | Processor |
| Signature and date | Electronic acceptance in the App; date in the acceptance record | Same |
B. Description of the processing
B.0 Subject matter and duration
Subject matter: the processing of Customer Personal Data needed to provide the Service to the Merchant under the Agreement, namely AI-assisted email marketing, abandoned-cart recovery emails, handling of Customer replies and analytics for the Merchant's Store. Duration: the term of the Agreement, plus the deletion period in clause 12 (the database by day 22 after uninstall, every copy within 30 days after uninstall), or until the end of a retrieval period under clause 12.2, subject to clause 12.6.
B.1 Categories of data subjects
- Customers of the Merchant's Store that the App syncs from Shopify. A Customer record (name, email address, consent state) is stored only for Customers subscribed to email marketing, and is kept after an unsubscribe only while emails, replies or carts linked to it are kept. Orders of Customers who are not subscribed are stored without a name or email address, linked only by Shopify's customer ID. Customers who are not subscribed never receive Campaign or abandoned-cart emails.
- Anyone who starts a checkout or pays for an order on the Store. Shopify sends their checkout or order notification, which can include contact details, addresses and cart or order contents, to the Service whether or not abandoned-cart recovery is on. The Service reads it in memory and keeps nothing unless the email address matches a subscribed Customer while recovery is on.
- People who write to an address the Service uses to receive replies. These are usually Customers, but can be anyone who writes to that address.
- The Merchant's staff or other people named in content the Merchant enters, such as the sender name, email signature or FAQ.
B.2 Categories of personal data
- Identity and contact: first name, email address, Shopify customer ID (last names are not collected). If Shopify has no first name, the Service may derive one from the email address for use in emails.
- Marketing consent: a yes/no flag derived from the Shopify email marketing state, which after the first sync can only change from yes to no, and whether the Customer unsubscribed in the Service (by link, one-click header, spam complaint or a reply asking to stop). Only Customers subscribed to email marketing are stored. For a Customer who opts out, or whose data is erased, a one-way hash of the email address is kept (a suppression list) so they are never emailed again.
- Purchase history: order IDs, order dates and totals, and up to 20 line items
per order (product title, product type, vendor, quantity, price); the discount
codes used and the campaign tags (UTM source, medium, campaign, content) of the
store visits Shopify reports for the order, used only to link the order to a
campaign, and the attribution method (link, discount code or 7-day window); derived total
spent, order count, last order date, purchased categories and brands, and
segment (for example VIP, new, returning or prospect). The App does not request
read_all_orders, so each sync reads only orders from the last 60 days. Orders already stored are kept for 24 months from the order date (B.7), and no order older than 24 months is imported, so order history covers at most the last 24 months, starting 60 days before the first sync. Mersail will update this Annex before it requestsread_all_orders. - Checkout and order notifications: received for every checkout and paid order and read in memory (section B.1(2)). Stored only for a matching subscribed Customer while recovery is on: checkout ID and token, Shopify's checkout recovery link, time of last activity, status and a link to that Customer. The Service reads the email address only to find the match and does not store it separately. It does not store the phone numbers, addresses, cart or order contents or payment details in the notification.
- Emails sent: subject line and content of emails personalised for each Customer (which can include the first name and recommended products), send status, send time and the email provider's message ID; the products recommended in each email.
- Engagement: delivered, bounced, unsubscribed and spam complaint events, with times. Open and click tracking is turned off on Mersail's sending domain, and the Service discards any opened or clicked event, so no opens, clicks, IP addresses or device data are recorded. No other event details are stored.
- Correspondence: the sender's email address, the time received and the text of replies (with quoted earlier messages removed), which can contain any personal data the writer includes; the category the rules gave it; whether it was held for the Merchant; and the text of any reply sent, with whether AI wrote it.
- AI insights: AI-written campaign insights, which can quote a Customer's first name.
- Merchant content: names in the sender name, email signature or FAQ.
The Service does not read Customer phone numbers, postal addresses or payment details from the Shopify API, and does not collect passwords or government identifiers.
B.3 Sensitive data
None is intended. A Customer may include special categories of data in a reply. The Service does not ask for it, processes it only to sort, answer or hold the reply, and deletes replies after 365 days (section B.7). Safeguards: the data is not used to build segments or recommendations, is not added to any AI request other than an answer to that reply, and is covered by the measures in Annex II. On the Merchant's written request to privacy@mersail.com, Mersail deletes a specific reply within 10 Business Days.
B.4 Frequency
Continuous, while the App is installed.
B.5 Nature of the processing
Collection through the Shopify API and Shopify notifications; storage in a hosted database; segmentation, profiling for marketing and product recommendation; generation of email content, subject lines, replies and insights by sending selected data to the AI Provider; sending and receiving email through an email provider; sorting replies with rules and answering product questions automatically with AI while the Merchant has AI replies on; recording delivery, bounce, unsubscribe and complaint events and estimating attributed revenue; access logging; scheduled deletion; deletion on request and at the end.
B.6 Purposes (business purposes)
- Building audiences from purchase history and consent state.
- Writing, previewing and sending the Campaigns the Merchant approves.
- Sending abandoned-cart recovery emails, while the Merchant has them on.
- Receiving Customer replies, sorting them with rules, answering product questions automatically with AI (while the Merchant has AI replies on) or holding the reply for the Merchant, and sending the Merchant's own replies.
- Honouring unsubscribes.
- Measuring delivery and engagement, and estimating attributed revenue.
- Producing AI insights on the Merchant's Campaigns.
- Handling Shopify privacy requests and data subject requests.
- Keeping the Service secure, fixing errors and logging access, for the Service provided to the Merchant.
Customer Personal Data is not used to train or improve any AI model, for any other merchant, for Mersail's own marketing, or for sale.
B.7 Retention
| Data | Kept for | Then |
|---|---|---|
| Email bodies (HTML and plain text) and personalised preview samples | 180 days after sending (or after creation, if never sent) | The body text is erased. The email record, subject line and personalised product section are kept, as in the next row. |
| Orders and line items | 24 months from the order date. Older orders are not imported. | Deleted. The Customer's derived totals and segment are recalculated from the orders that remain. |
| Customer records, with that Customer's email records and subject lines, engagement events, replies and recommendations | Until 24 months have passed since the Customer's last order, the last email sent to them and the date the record was first stored, whichever is latest. A Customer deleted in Shopify is deleted at the next daily check. Earlier on a Customer deletion request (clause 8.3). | Deleted. The suppression list entry, if any, is kept. A Customer still subscribed in Shopify can be imported again by a later full sync; the 24 months then start again. |
| Products, Campaigns, AI insights | While the App is installed. | Deleted at the end (clause 12). |
| Engagement events | 395 days | Deleted |
| Customer replies, including replies the Merchant dismissed | 365 days after receipt | Deleted |
| Abandoned-cart records | 90 days after creation | Deleted |
| Access log entries (store, staff member's Shopify user ID, action, route, record count and time; no Customer Personal Data) | 395 days | Deleted |
| Records of Shopify privacy requests (store, kind of request, status, times; the Shopify customer ID for data requests only) | 395 days | Deleted |
| All data after uninstall | Until Shopify's store deletion request (about 48 hours), and in any case deleted from the database by day 22 after uninstall; no database backups are kept; every other copy gone within 30 days; longer only during a retrieval period (clause 12.2) | Deleted (clause 12) |
B.8 Sub-processors
See Annex III.
C. Competent supervisory authority
For a Merchant established in the EEA: the supervisory authority competent for the Merchant under GDPR art. 55 or 56. For a Merchant outside the EEA that is subject to the GDPR under art. 3(2): the authority of the Member State where its representative under GDPR art. 27 is established or, if it has none, the authority of a Member State where the affected Customers are. For a Merchant whose processing is not subject to the GDPR: no EU authority supervises the Merchant, and the SCCs Module Four in clause 7.3 apply. For Mersail: the Garante per la protezione dei dati personali (Italy).
Annex II: Technical and organisational measures
Part A: In place in the code
| # | Measure |
|---|---|
| A1 | App request authentication. Every App API request must carry a Shopify session token. The token's signature, audience, expiry and destination store are checked, and only active installations are accepted. The staff member's Shopify user ID from the token is recorded on access-log entries. |
| A2 | Install and tokens. The App is installed through Shopify's managed installation. Mersail obtains its access token by exchanging the session token with Shopify, and uses expiring offline access tokens with refresh tokens. There is no OAuth redirect flow. |
| A3 | Webhook authenticity. Shopify notifications are verified by HMAC-SHA256, compared in constant time; checkout and theme notifications must also carry their topic, be no older than 48 hours, and are processed only once per notification ID. Email provider notifications are verified by signature with a 5-minute tolerance and a replay check, and are rejected if no signing secret is configured. |
| A4 | Tenant separation. Database queries for merchant data are filtered by the authenticated merchant, and automated tests check that each route returns 404 for another store's records and lists only the store's own rows. Separation is logical, not physical. |
| A5 | Credential encryption. Shopify access and refresh tokens and the email-sending key are encrypted in the application (Fernet: AES-128-CBC with HMAC-SHA256) with dedicated keys that can be rotated without downtime. The application refuses to start in production with a weak secret. |
| A6 | Web security headers. HSTS (one year, including subdomains); a content security policy that allows framing only by the requesting Shopify store and the Shopify admin, allows scripts only from the App and Shopify's CDN, forbids framing of public pages, and sandboxes AI-generated previews; nosniff; a referrer policy; no server version header. |
| A7 | Encrypted connections. Calls to Shopify, the email provider and Anthropic use HTTPS endpoints fixed in the code. Connections from the application to the database require TLS in production. |
| A8 | Data minimisation from Shopify. The Customer sync requests only ID, name, email and marketing consent state. Checkout and order notifications arrive in full; the Service uses only the checkout ID, token and email, and stores only those identifiers, the time, the status and a link to an existing subscribed Customer (Annex I, B.1(2)). |
| A9 | Data minimisation for AI. Email-writing prompts carry first name, segment, favourite and purchased categories, personalisation goal, recency and the recommended products with the reasons they were chosen (which can name a brand the Customer bought), not email address, surname, spend, order IDs, postal address or payment details (Annex III). Replies are withheld from the AI Provider while AI replies are off, while the emergency stop is on, after uninstall and for unsubscribed Customers; replies in which the Service detects an email address or a phone number (North American, E.164, 00-prefixed and common EU formats) are held for the Merchant. |
| A10 | AI input and output checks. Untrusted text in prompts is length-limited, cleaned and stripped of the delimiters that separate it from instructions; known prompt-injection phrases cause a reply to be held. Must-escalate topics (orders, delivery, refunds, payments, accounts and personal data, unsubscribing, complaints and legal matters) are recognised in eight languages. Automatic mail is never answered, and a conversation gets at most 3 AI replies in 24 hours. AI answers are checked for placeholder text, restricted phrases, forbidden topics, contact patterns, links outside the Store and offers the Merchant did not set up. Campaign emails: scripts and event handlers are stripped, placeholder text blocks sending, and forbidden-topic words are removed from the visible body text. |
| A11 | Sending controls. Campaign and abandoned-cart emails go only to Customers who are subscribed and have not unsubscribed in the Service, checked again immediately before each email is handed to the email provider; each carries an unsubscribe link, one-click unsubscribe headers and the Merchant's postal address, and none is sent without that address. A sync never re-subscribes a Customer. The sender address is derived from the Store and cannot be set by the Merchant. Test sends and reply tests go only to the Merchant's own addresses. The emergency stop blocks creating, editing, scheduling and sending Campaigns, preview generation, test sends, abandoned-cart emails and AI replies (Agreement clause 5.9). AI replies are off by default. |
| A12 | Retention and deletion. A daily job applies the retention periods in Annex I. Customer and store deletion requests from Shopify cause hard deletion; shop/redact is acknowledged at once and processed in the background. A time-based purge deletes an uninstalled store's data by day 22 after uninstall, and the daily job also detects an uninstall whose notification was lost. The access and refresh tokens and the sending key are cleared at uninstall. Failures of the purge are reported, not hidden. |
| A13 | Access log. Every App route that returns or sends Customer Personal Data, and the Customer data request notification, writes an access log entry with store, staff user ID (for App requests), action (read, or export for any route that emails Customer data out), resource, record count, route and time. Log entries hold no Customer Personal Data and are kept 395 days. |
| A14 | Build checks. Automated tests run in continuous integration on every change, with a read-only token and actions pinned to commit hashes. Dependency vulnerability scans (pip-audit, npm audit) and a secret scan of the full history block a release when they find a problem. Runtime dependencies are installed from a hash-locked file. |
| A15 | Security policy. A written security policy and incident response plan (SECURITY.md): severity levels, containment (including the emergency stop), notice to Shopify within 24 hours, notice to merchants without undue delay, controller duties to the Garante, and a post-incident review. |
| A16 | Abuse limits. Requests are rate-limited per store (sending, AI, sync and other API calls) and per network address (unsubscribe), and request bodies are capped (1 MB, 256 KB for the App API). The App's API documentation is not served in production. |
| A17 | Credentials and personal data kept out of logs. Session tokens, hmac, session, OAuth code and state values and unsubscribe link codes in URLs are replaced with [REDACTED] before a request is logged; email addresses and phone numbers in log messages are masked; logs are structured with request and store identifiers. |
| A18 | No customer data in source control. Git hooks and a CI test block customer or order data files, and email addresses outside reserved and Mersail domains, from the code repository. |
| A19 | Privacy request records. Every Shopify privacy request is recorded with its status and attempts, kept 395 days as proof of completion; undelivered data requests are retried daily. |
| A20 | No storefront fetching. Brand style and logo are read only through the Shopify theme API. The Service never downloads pages from the Store or any website, and addresses typed by the Merchant are never fetched. |
Part C: To be in place before production launch
| # | Measure | Card |
|---|---|---|
| C1 | Production on a Render web service and a Supabase database, both in Frankfurt, with HTTPS at https://app.mersail.com, and production credentials separate from development. The application kept awake so scheduled jobs run (the Render Free instance type sleeps after 15 minutes without traffic). | SH-044, SH-047 |
| C2 | Encryption at rest confirmed for the production database; application logs at 7 days (Render Hobby workspace). | SH-044, SH-112 |
| C3 | Mersail's own email provider account, holding only Mersail's domain and used only by the Service (receiving replies needs a full-access key, so the separation is by account, not by key), the sending domain in Resend's us-east-1 region (United States) with open and click tracking off, and the inbound reply domain verified. | SH-108, SH-045 |
| C4 | Two-factor authentication and unique passwords on every production account (Render, Supabase, Shopify Partners, GitHub, Resend, Cloudflare, domain registrar, Anthropic). | SH-044 |
| C5 | In-App acceptance of the Agreement and DPA, with a server-side gate: no sync and no email before the current version is accepted. | SH-036 |
| C6 | Operator tools (AI coding assistants, connectors) kept away from production Customer Personal Data, or covered by no-training commercial terms and listed in Annex III (clause 4.3). | SH-114 |
Part D: Not in place
- No security certification (such as ISO/IEC 27001 or SOC 2) for Mersail.
- No application-level encryption of Customer Personal Data (only credentials, A5).
- No database row-level security; tenant separation relies on query filters (A4).
- No database backups or point-in-time recovery on the current database plan.
- Operator access to the database is not logged (SH-072), and an access-log entry is not written when an external call fails after data was sent (SH-069).
- Checkout and order notifications are received for every Store, whether or not abandoned-cart recovery is on (SH-110).
- No self-service export (SH-113); no email alert when a reply is held (SH-116).
- Error tracking (Sentry, EU data region) is listed in Annex III. It is switched on only once this version is in force, or after notice under clause 6.4 to any Merchant who accepted an earlier version.
- One person operates the Service. There is no 24/7 monitoring or on-call backup.
- No external penetration test.
Annex III: Sub-processors
Checked against each provider's own pages and the official Data Privacy Framework List (https://www.dataprivacyframework.gov/list) on 5 November 2026. Recheck before publication.
AI tasks
Every AI task uses Anthropic's Claude Haiku 4.5 model. No other AI Provider receives data, and there is no fallback to another provider. Adding one requires notice under clause 6.4.
| Task | Customer Personal Data sent to Anthropic |
|---|---|
| Writing email bodies | First name (possibly derived from the email address; left out for broadcast Campaigns), segment, favourite category, personalisation goal, recency and days since last order, purchased categories, recommended products and the reasons for them (which can name the Customer or a brand the Customer bought); the Merchant's tone, language, brand voice, discount text and forbidden topics. No email address, surname, spend, order IDs, postal address or payment details. |
| Writing subject lines | First name (not for broadcast Campaigns), favourite category, personalisation goal, lead product, recommendation type and reasons, discount, seasonal theme. |
| Naming Campaigns | None. Only segment type or category, tone, language, discount and brand voice. |
| Answering replies | Only replies that pass the checks in Agreement clause 5.4, while the Merchant has AI replies on: the reply text (quoted history removed, cut to 1,200 characters), the Merchant's FAQ, and product details. Replies withheld or held by the checks are never sent. |
| Campaign insights | Campaign settings and metrics, up to eight subject lines with their send counts, and up to three body excerpts of 600 characters, which can include first names. |
| Grouping product categories | None. Product types only. |
Sub-processor list
| Sub-processor | Service | Customer Personal Data | Location | Transfer mechanism | Sources and notes |
|---|---|---|---|---|---|
| Render Services, Inc. | Application hosting and application logs | All data passes through the application; logs hold request metadata and identifiers | Frankfurt, Germany. Render's account and support systems are in the United States | DPF: EU-U.S., UK Extension and Swiss-U.S. Render's DPA provides the SCCs (Modules 1 to 3) and UK and Swiss terms if the DPF stops applying. | https://render.com/dpa, sub-processors at https://render.com/trust. 10 days' notice of new sub-processors. Render processes its own service usage data as a controller. |
| Supabase Pte. Ltd. (Singapore) | PostgreSQL database | All data the Service stores (Annex I) | Frankfurt, Germany (AWS eu-central-1) | SCCs: Module 2 or 3, governed by Irish law, with the UK Addendum and a Swiss addendum, incorporated in Supabase's DPA, which forms part of its terms on acceptance. | https://supabase.com/legal/dpa (version of 1 August 2026), sub-processors at https://supabase.com/legal/customer-resources/subprocessor-list. 30 days' notice of sub-processor changes to subscribers of its list, with 5 days to object. Breach notice without undue delay and where feasible within 48 hours. |
| Plus Five Five, Inc. (Resend) | Sending email, receiving replies, delivery and engagement events | Recipient email addresses; email content (including first names and recommendations); replies (sender, subject, text); delivery, bounce, unsubscribe and complaint events. Open and click tracking is off on Mersail's sending domain. | Email sent from Resend's United States region (us-east-1). Account data, email metadata, logs and API records also stored in the United States. | DPF: EU-U.S. and UK Extension. Resend's DPA incorporates SCC Modules 1 to 3 with UK and Swiss terms. | https://resend.com/legal/dpa, https://resend.com/legal/subprocessors. At least 14 days' notice of sub-processor changes. Resend processes its own service usage data as a controller. Mersail uses its own Resend account, not shared with other projects. |
| Anthropic Ireland, Limited (Anthropic's contracting entity for customers in the EEA, Switzerland and the UK; processing by Anthropic, PBC) | Every AI task (see above) | See AI tasks | Stored in the United States. Requests run in any geography Anthropic uses; Claude Haiku 4.5 cannot be limited to a region, and Anthropic offers no EU processing option. | Mersail to Anthropic Ireland, Limited: no Restricted Transfer (both in the EEA). Onward transfers to Anthropic, PBC in the United States are covered by the SCCs (Modules 2 and 3), UK Addendum and Swiss addendum in Anthropic's DPA. Not on the DPF List. | https://www.anthropic.com/legal/commercial-terms (Anthropic may not train models on customer content), https://www.anthropic.com/legal/data-processing-addendum (breach notice within 48 hours; 15 days to object to new sub-processors), sub-processors at https://www.anthropic.com/subprocessors. |
| Functional Software, Inc. (Sentry) | Error tracking for the application | Error reports: error type and message (email addresses and phone numbers masked), stack trace without variable values, request path without query string, user agent, request ID, the Merchant's internal Mersail ID, scheduled job name. No IP addresses, cookies, request bodies, Customer records or AI inputs and outputs. An error message can occasionally contain other data the application was handling. | Frankfurt, Germany (Sentry's EU data region; organization created in that region). Sentry staff in the United States may access the data for support. | DPF: EU-U.S., UK Extension and Swiss-U.S. Sentry's DPA provides the SCCs if the DPF stops applying. DPF status checked on the Data Privacy Framework List on 10 November 2026: Sentry.io, active for the EU-U.S. Framework, the UK Extension and the Swiss-U.S. Framework (non-HR data). | https://sentry.io/legal/dpa/, sub-processors at https://sentry.io/legal/subprocessors/. Data storage location: https://docs.sentry.io/organization/data-storage-location/. DPA version 5.1.0 accepted on the Sentry account on 10 November 2026. |
Retention by Sub-processors
Clause 12.5(3) relies on these periods. Each runs from when the Sub-processor received or generated the data.
| Sub-processor | How long it keeps Customer Personal Data | Source |
|---|---|---|
| Render | Application logs: 7 days on the Hobby workspace plan. No database is hosted on Render. | https://render.com/docs/logging |
| Supabase | No automatic backups and no point-in-time recovery on the Free plan. Database logs: 1 day. After the contract ends, a 30-day period to retrieve data, then deletion of all copies. | https://supabase.com/pricing, https://supabase.com/legal/dpa (clause 11) |
| Resend | Sent emails, events and logs: 30 days. All customer data deleted within 90 days after Mersail's Resend account ends. | https://resend.com/pricing, https://resend.com/legal/dpa |
| Anthropic | Inputs and outputs deleted within 30 days of receipt or generation. Inputs and outputs flagged by Anthropic's automated trust and safety systems as violating its Usage Policy: up to 2 years (classification scores up to 7 years). The flagged case is an exception under clause 12.6(3). | https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data |
| Sentry | Error events: 30 days (Developer plan). | https://sentry.io/pricing/, https://sentry.io/legal/dpa/ |
Operator tools (clause 4.3)
Tools Mersail's operator uses that can reach accounts holding Customer Personal Data. They are used only to operate and fix the Service, never to process Customer Personal Data for any other purpose. Checked on 10 November 2026.
| Tool | Accounts it can reach | Terms |
|---|---|---|
| Claude Code and Claude in Chrome (Anthropic) | Sentry and Resend through connectors; in the browser, whatever account the operator is signed in to | Claude Max subscription with "Help improve our AI models" turned off, so chats and coding sessions are not used for training |
Not Sub-processors
- Shopify is the source of the data and the Merchant's own provider.
- Cloudflare, Inc. answers DNS queries for mersail.com. Production traffic goes directly to Render and does not pass through Cloudflare. A Cloudflare tunnel is used only in development, with test stores.
- OpenAI and Google receive no data. The Service does not use them.
- Mail sent to support@, privacy@ and security@mersail.com is forwarded by Cloudflare Email Routing (Cloudflare, Inc.), which does not store it, to a mailbox at Google (Gmail), which does. It holds whatever Merchants and Customers write to those addresses. This mail is Mersail's own correspondence, which Mersail handles as controller (privacy policy §1.3), not Merchant data processed on the Merchant's behalf. A request about Customer Personal Data that arrives there is forwarded to the Merchant under clause 8.2 and deleted from the mailbox once it is closed, and no later than 30 days after it is forwarded. For users in the European Economic Area, Gmail is provided by Google Ireland Limited.
Annex IV: Transfer impact assessment (summary)
Mersail's assessment of the transfers in Annex III, made on 5 November 2026 under GDPR art. 46 and EDPB Recommendations 01/2020. It is reviewed under clause 7.7.
| Recipient | Transfer and tool | Data and exposure | Law of the destination | Measures | Outcome |
|---|---|---|---|---|---|
| Anthropic | Mersail to Anthropic Ireland, Limited: inside the EEA, no Restricted Transfer. Anthropic Ireland to Anthropic, PBC (United States): SCCs Modules 2 and 3 in Anthropic's DPA. | Selected fields only (Annex III, AI tasks): first names, product and segment data, reply text. No email addresses, surnames, spend, order IDs, addresses or payment data. Inputs and outputs deleted within 30 days unless flagged. | US: FISA section 702 and E.O. 12333 may reach a cloud and AI provider. E.O. 14086 safeguards (necessity, proportionality, Data Protection Review Court) apply to all transfers to the US, whatever the tool, as the Commission found in Decision (EU) 2023/1795. | Data minimisation; TLS to a fixed endpoint; no training; short retention; replies withheld in the cases in Agreement clause 5.4. | Acceptable with the SCCs. Residual risk low. |
| Supabase | Supabase Pte. Ltd. (Singapore) is the contracting party; data stored in Frankfurt on AWS eu-central-1. Remote support access from outside the EEA is possible. SCCs Modules 2 and 3 in Supabase's DPA. | All stored data, at rest in the EEA. Access from outside the EEA is occasional and for support or operations. | Singapore: government access powers exist (for example under the Criminal Procedure Code), with no record of use against EU cloud data. US: AWS is a US company; the CLOUD Act could reach data it controls; E.O. 14086 safeguards apply. | Storage in the EEA; TLS required; encryption at rest by the host; credentials encrypted by the application (Annex II A5); no backups on the current plan. | Acceptable with the SCCs. Residual risk low. |
| Resend | Plus Five Five, Inc. (United States): EU-U.S. DPF and UK Extension (adequacy), with the SCCs in Resend's DPA as fallback. | Email addresses, email content and replies, sent from and received in the US; metadata and logs stored in the US for 30 days. | US: as above. | DPF certification checked on the DPF List; open and click tracking off; 30-day retention. | Covered by adequacy; no further measures needed. |
| Render | Render Services, Inc. (United States): EU-U.S. DPF, UK Extension and Swiss-U.S. DPF (adequacy), with the SCCs in Render's DPA as fallback. | All data passes through the application in Frankfurt; logs 7 days; account and support systems in the US. | US: as above. | DPF certification checked on the DPF List; masking of email addresses and phone numbers in logs (Annex II A17). | Covered by adequacy; no further measures needed. |
| Sentry | Data stored in Frankfurt (EU data region). Access by Functional Software, Inc. staff in the United States for support: EU-U.S. DPF (adequacy), with the SCCs in Sentry's DPA as fallback. | Error reports only; email addresses and phone numbers masked; no IP addresses, request bodies, Customer records or AI data. | US: as above. | Storage in the EEA; scrubbing before sending (no user data, local variables, bodies, cookies or query strings); AI integrations disabled in the SDK. | Covered by adequacy (DPF listing active, checked 10 November 2026); residual risk low. |
If Decision (EU) 2023/1795 is annulled or suspended, the Resend, Render and Sentry rows move to their SCCs and are reassessed like the Anthropic row (clause 7.6).
Changes in this version
Version 0.2 (draft, 5 November 2026) replaces version 0.1 (draft of 15 September 2026): Anthropic is the only AI Provider and OpenAI and Google are removed; Supabase (database, Frankfurt) is added and Render now hosts only the application, in Frankfurt; no database backups on the current plan; data-request exports are complete and retried; customer deletion also removes AI insights that name the Customer; the post-uninstall purge is day 22 and starts when the uninstall notification is lost; AI replies are off by default and carry an AI notice; Annex II reflects the measures now in the code, and Part C lists only deployment work. Sentry (error tracking, EU data region) is added to Annex III and Annex IV (SH-142).