Mersail Privacy Policy

Version 1.3

Effective date: 16 November 2026

Last updated: 16 November 2026

Summary

Mersail is an app for Shopify merchants. It reads a store's customers, orders and products from Shopify, groups customers into marketing segments, recommends products, writes marketing emails with an AI model and sends them. When the merchant turns it on, it also reminds shoppers about checkouts they did not finish, and answers product questions in replies to those emails. It reports on campaign results.

Mersail has two roles:

This policy explains what we collect, why, who receives it, where it is processed, how long we keep it and how it is deleted. "Controller", "Processor" and "Sub-processor" have the meanings they have in the EU General Data Protection Regulation (GDPR). The Merchant Agreement that governs our work for Merchants, with the Data Processing Agreement (DPA) it incorporates, is published at /terms.

1. Who this policy covers

1.1 Who is responsible

Mersail is operated by Alberto Clemente, a self-employed sole trader (lavoratore autonomo with a Partita IVA), established in Italy ("Mersail", "we", "us").

Data protection officer. Mersail has not appointed a data protection officer. GDPR Art. 37 requires one only where core activities consist of regular and systematic monitoring of people on a large scale, or of large-scale processing of special categories of data. Mersail's processing for Merchants is not on a large scale, and it processes no special categories of data by design. We review this assessment every year and as the service grows. Write to privacy@mersail.com for any data protection question.

United Kingdom. Mersail is not offered in the United Kingdom. The app does not let a store whose business is there accept its terms or sync any data, and for every other store it does not store or email Customers whose default address in Shopify is in the United Kingdom: during each sync it reads the country on that address, and a Customer in the United Kingdom gets no customer record, and their orders are not kept. A Customer with no address on file cannot be placed, so a few Customers in the United Kingdom can still reach Mersail. Because Mersail offers nothing to people in the United Kingdom and does not market to them, it has not appointed a representative under UK GDPR Art. 27.

Switzerland. Mersail has no representative in Switzerland. Swiss FADP Art. 14 requires one only from a controller whose processing of data about people in Switzerland is extensive, regular and high-risk; Mersail's processing as Controller (§1.3) is none of these.

1.2 People whose data we process

1.3 Our role for each kind of data

2. Data we collect

2.1 From the Shopify Admin API (with the Merchant's authorization)

Mersail requests these five scopes. Four only read data; write_customers is used for one thing only:

Scope What we read Purpose
read_customers Shopify customer ID, email address, first name (taken from the customer's default address when the account has none; last names are not read), the country on the default address (read only to leave out Customers in the United Kingdom, §1.1, and not stored), and email-marketing consent state, stored only for customers subscribed to email marketing. For someone who opts out, Mersail keeps a one-way hash of their email address, not the address, so it never emails them again Build audiences, personalise emails, and send marketing email only to Customers who are subscribed
read_orders Order ID, date and total; the ordering Customer (the same fields as above); up to 20 line items per order (title, product ID, product type, vendor or brand, quantity and unit price); the discount codes used on the order; and the campaign tags (utm_source, utm_medium, utm_campaign, utm_content) of the first and last store visit before the order, as Shopify's customer journey summary reports them Segments, product recommendations, and linking orders to campaigns in analytics
read_products Product ID, title, type, vendor, handle, status, publish date, main image address, price and compare-at price Choose and show products in emails and in automatic answers
write_customers Nothing is read with it. Mersail uses it only to set a Customer's email marketing consent to "unsubscribed" in the Merchant's Shopify admin when that Customer unsubscribes or complains through Mersail Keep the Merchant's Shopify records and other email tools in step with opt-outs (Shopify API Terms 2.3.17)
read_themes The published theme's settings file (config/settings_data.json: colour, colour-scheme and logo settings) and the logo image it names Match email colours and logo to the storefront. No Customer data is involved

Shopify also tells us when a Customer's consent was last updated and at what opt-in level; we do not store either. We do not read Customers' phone numbers, postal addresses (other than the name and the country on the default address), notes or tags, and we do not read shipping addresses, billing addresses or payment details on orders.

Order history. We do not request read_all_orders, so each sync can read only orders placed in the last 60 days. Orders we have already stored are kept for 24 months from the order date and then deleted (§8.1), and we never import an order older than 24 months. The totals, order counts and segments we compute therefore cover at most the last 24 months, starting 60 days before the store's first sync. We will update this policy before we ask Shopify for older orders.

What we compute. From orders we compute and store, for each Customer: total spent, order count, date of last order, the product types and brands they bought, and a segment (VIP, new, returning or prospect; the Merchant sets the VIP spending threshold). To report campaign revenue, we link an order to a campaign by the strongest evidence available, in this order: (1) the store visit that led to the order came from a link in that campaign's email, as shown by the campaign tags Shopify reports for the visit; (2) the order used a discount code offered in that campaign; (3) otherwise, the most recent campaign email sent to that Customer in the 7 days before the order. The analytics show which of the three methods linked each order.

Customers who are not subscribed. We store a Customer's name and email address only while they are subscribed to email marketing. A Customer who is not subscribed gets no customer record. Their orders are kept without a name or email address, linked only by Shopify's customer ID, and are used together with other Customers' orders to work out which products are often bought together in the store; if that Customer later subscribes, the orders are linked to them again, and a customers/redact request deletes them. When a subscribed Customer unsubscribes, their record is deleted at the next sync, unless Mersail has already emailed them, received a reply from them or tracked a cart for them; in that case the record is kept, marked as unsubscribed, for as long as those emails, replies or carts are kept (§8.1). Either way a one-way hash of the address stays on the suppression list so they are never emailed again.

Refreshing. Names, email addresses and consent state are refreshed each time the store's data is synced from Shopify: at setup, and afterwards when the Merchant opens the app's dashboard or clicks "Refresh customer sync". A Merchant who corrects a Customer's name or email address in Shopify therefore sees the change in Mersail after the next sync. For consent, see §3.6.

This data is accessed under Shopify's protected customer data requirements.

2.2 About the Merchant and its staff

From Shopify at installation:

Shopify installs Mersail from the Shopify admin and gives us no email address for the staff member who installs it. During setup we read the store's name, contact email address, currency and time zone from Shopify to pre-fill the setup form; the Merchant can change them. When Merchant staff use the app, we receive their Shopify user ID in Shopify's session token and record it on access-log entries (§2.3). Apart from the acceptance record below, we do not store staff names or email addresses.

When the Merchant accepts the Merchant Agreement, we keep an acceptance record: the store, the Shopify user ID of the staff member who accepted, the name and role they typed, the business name and address, the Notice Email (the address for notices under the Merchant Agreement), which versions of the Merchant Agreement and DPA were accepted and a fingerprint of their text, the clauses approved separately, the value of each acceptance box, when the one-time code we emailed to confirm the approval was entered (we never store the code), and the date and time.

Entered by the Merchant in the app:

Customers see in emails the sender name and sender address; a reply address, which is Mersail's own reply address on campaign emails and answers to replies when reply handling is set up, and otherwise the Merchant's reply-to address; and the postal address. Some of the data above is also sent to our AI provider as part of the requests described in §3.4.

2.3 Generated through use of the app

2.4 Billing and usage

Paid plans, when offered, are billed by Shopify through Shopify App Pricing and appear on the Merchant's Shopify invoice. Shopify processes the payment; Mersail never receives card or bank details. We read the store's current plan and its status from Shopify's Partner API. To apply the plan's email allowance, we count in our own database each email that counts towards it (campaign emails, automatic answers and test sends), linked to Mersail's internal ID for the email; nothing is reported to Shopify per email. Plan and usage records are kept while the app is installed and deleted with the store's data (§8.1). Shopify's payout statements to Mersail, which name the stores that paid, are kept as Italian accounting and tax law requires (§3.2). Plan prices and email allowances are not part of this policy.

3. How we use data, including AI processing

3.1 Customer data, on the Merchant's instructions

We use Customer data only to:

Apart from keeping our own server logs secure (§3.2), we do not use Customer data for our own purposes, and we do not combine one store's Customer data with another store's.

Profiling. We analyse each Customer's purchase history (spend, order count, how recently they ordered, and the product types and brands they bought) to place them in marketing segments and to choose which products to recommend. This decides which marketing emails they receive and what those emails show. It is done for the Merchant's marketing and is not used for decisions with legal or similarly significant effects. Product recommendations are computed separately for each store, from that store's own data, with fixed scoring rules. Scores for products that are often bought together use the orders of all the store's Customers, including Customers who are not subscribed.

3.2 Data we control: purposes, legal bases and retention

Data Purpose Legal basis (GDPR Art. 6(1)) Kept for
Store domain, access token, granted scopes, business profile and brand settings (§2.2) Providing the app to the Merchant (b) contract, where the Merchant is an individual; otherwise (f) our legitimate interest in performing our contract with the Merchant While the app is installed; then deleted as in §8.1
Store contact email address (§2.2) Service and security emails, notices under the Merchant Agreement and DPA, and privacy-request exports (b) contract; (c) legal obligation, for notices the law requires While the app is installed; then deleted as in §8.1
Acceptance records (§2.2) Recording that the Merchant Agreement and DPA were accepted, and proving it (b) contract, while the Merchant Agreement is in force; afterwards (f) our legitimate interest in establishing and defending legal claims While the app is installed; deleted with the rest of the store's data after uninstall (§8.1). We keep no separate copy
Plan and usage records (§2.4) Applying the Merchant's plan and email allowance (b) contract While the app is installed; then deleted as in §8.1
Shopify payout statements, invoices and our accounting records Accounting and tax (c) legal obligation 10 years from the date of the last entry (Italian Civil Code Art. 2220), and longer only while a tax assessment for that year is still open
Access log, privacy-request records, server and application logs (§2.3), including requests to unsubscribe pages Keeping the service secure, detecting abuse, investigating incidents, proving that privacy requests were completed, and meeting Shopify's data-protection requirements for apps (f) our legitimate interest in securing the service and meeting those requirements Access log and privacy-request records 395 days; server and application logs 7 days
Shopify user ID of staff who use the app (§2.2) Recording which staff account viewed Customer data, in the access log (f) our legitimate interest in securing Customer data and meeting Shopify's requirements As the access log
Emails sent to privacy@, security@ or support@mersail.com Answering questions and requests (b) contract, or (f) our legitimate interest in answering; (c) where the law requires us to respond 24 months after the last message in the conversation; records of data protection requests 395 days, as the privacy-request records
Requests to this page Keeping the page secure (f) our legitimate interest in securing the service As server logs
Any of the above, where needed Establishing, exercising or defending legal claims (f) our legitimate interest in protecting our legal rights Only as long as the claim requires

The store domain and Shopify's authorization are needed to install and run Mersail; without them the app cannot work. We make no automated decisions with legal or similarly significant effects about Merchants or their staff. We do not send marketing email to Merchants.

3.3 Your right to object

You can object at any time, on grounds relating to your particular situation, to our processing of your personal data based on legitimate interests (the rows marked (f) in §3.2). Write to privacy@mersail.com. We will then stop, unless we have compelling legitimate grounds that override your interests, rights and freedoms, or we need the data to establish, exercise or defend legal claims.

3.4 AI processing

To write emails, write answers to product questions in replies and produce insights, we send some data, including Customer personal data, to our AI provider, Anthropic (§4.1), through its API. Every task uses Anthropic's Claude Haiku 4.5 model. The table shows what each task sends.

Task Data sent
Email body The Customer's first name (if none is on file, a first name guessed from the email address), segment, favourite product category, personalisation goal, how recently they ordered and the days since their last order, and the product categories they bought; the recommended products' titles and categories and the reasons each was chosen, which can mention the Customer's first name and brands they bought before; the Merchant's sender name, tone, language, brand voice, discount text and forbidden topics. For broadcast campaigns, where one text is written for every recipient, the first name is left out of the request, although a reason for a product choice can still contain it
Subject line The Customer's first name when known (not for broadcast campaigns), favourite product category, personalisation goal, the lead recommended product and the reasons it was chosen; for seasonal campaigns, the first name and the season; the Merchant's discount text, tone, language and brand voice
Automatic answer to a reply The reply text with earlier quoted messages removed, up to 1,200 characters; the Merchant's product titles, types, product page addresses and discount percentages, business FAQ and forbidden topics. No other Customer data is added
Campaign insights The campaign's name and settings, the number of Customers targeted, the subject lines and first 600 characters of the text of up to 3 sent emails, up to 8 subject lines (140 characters each) with their send counts, top categories, send timing, and aggregated statistics by Customer group. Subject lines and email text can contain Customers' first names
Store overview insights Business name, industry, sender name, store domain, up to 3 recent subject lines, the number of subscribed Customers in each segment, and results for each campaign
Grouping product types into categories The store's product types only
Campaign names (shown only to the Merchant) Segment type or product category, tone, language, and the Merchant's discount text and brand voice. No Customer data

3.5 Model training

Mersail does not use Merchant or Customer data to train, fine-tune or improve any machine-learning or AI model. Product recommendations use fixed scoring rules computed for each store.

Anthropic's Commercial Terms do not allow Anthropic to train models on the content we send through its API. Mersail has not joined any Anthropic programme that shares data to improve its models, and sending feedback to Anthropic is turned off for Mersail's organisation (checked 10 November 2026).

3.6 Consent and unsubscribing

4. Sub-processors and other recipients

4.1 Sub-processors

We share the minimum data each Sub-processor needs for its function. We do not sell personal data, and we do not share it for cross-context behavioural advertising.

Sub-processor What it does for Mersail Data it receives Where the data is stored and processed
Render (Render Services, Inc.) Runs the application and keeps its logs All data described in §2 passes through the application; application logs (§2.3) Frankfurt, Germany (European Union). Render's account and support systems are in the United States
Supabase (Supabase Pte. Ltd.) Hosts the application's PostgreSQL database All data the app stores (§2) Frankfurt, Germany (European Union)
Resend (Plus Five Five, Inc.) Sends all email from the app (campaigns, checkout reminders, automatic and manual replies, unsubscribe confirmations, test sends, and privacy-request exports to Merchants); receives Customer replies; reports delivery, bounce, unsubscribe and complaint events. Mersail uses its own Resend account, not shared with other projects Recipient address; sender name, sender address and reply address; subject and content, including the Customer's first name, recommended products, discount text, the unsubscribe link and the Merchant's postal address; Customer replies; delivery, bounce, unsubscribe and complaint events. Open and click tracking is off (§5.3) Email is sent from Resend's United States region (us-east-1). Resend also stores account data, email metadata, logs and API records in the United States
Anthropic (Anthropic Ireland, Limited) Writes email bodies, subject lines, automatic answers, campaign names and insights, and groups product types into categories As listed in §3.4 Stored in the United States. Requests are processed in any geography Anthropic uses; the model we use cannot be limited to a region
Sentry (Functional Software, Inc.) Records application errors so we can find and fix them Error reports: the error type and message with email addresses and phone numbers masked, the code location (without the values of variables), the requested page without its query string, the browser type, a request ID, the Merchant's internal Mersail ID and the name of a failed scheduled job. No IP addresses, cookies, request bodies, Customer records, or AI requests and answers. An error message can occasionally contain other data the application was handling when it failed Frankfurt, Germany (Sentry's EU data region). Sentry is a United States company whose staff may access the data for support

Each Sub-processor is bound by a written data processing agreement that limits its use of the data to providing its service to Mersail. For Render, Supabase, Resend and Anthropic, the provider's DPA is part of its terms of service and applies to Mersail's account. Sentry's DPA is accepted separately in the account; Mersail accepted it on 10 November 2026 (version 5.1.0). The application sends AI requests only to Anthropic's API address, which is fixed in the code. Before a new or replacement Sub-processor starts receiving Customer personal data, or before we send a Sub-processor a category of Customer personal data it did not receive before, we update this list and tell Merchants in advance, as described in §12 and the DPA. If a Sub-processor stops its service or a security problem requires an immediate change, we may replace it sooner and tell Merchants as soon as we can.

4.2 Other recipients

The app's typefaces are served from our own server, so opening the app sends nothing to a font provider.

4.3 Copies held by Sub-processors

Deleting data from Mersail's database does not delete the copies Sub-processors keep for their own security and abuse monitoring under their data processing terms:

5. Cookies, browser storage and email tracking

5.1 In the app

The app sets no cookies. Signing in uses Shopify App Bridge session tokens, sent with each request rather than stored in a cookie.

Name Type Purpose Duration
mersail:shopify-launch-context Browser session storage Remembers the store domain and Shopify host for the browser tab, so sign-in can restart Until the tab is closed

This item is strictly necessary to provide the app the Merchant asked for, so it is used without a consent banner. Anything Shopify App Bridge stores in the browser is Shopify's and is covered by Shopify's privacy policy. The app uses no analytics or advertising cookies or similar technologies, and we have set up no analytics or advertising tracking on our Shopify App Store listing. If we ever add non-essential technologies to the app, this page or the listing, we will first ask for consent where the law requires it.

5.2 On this page

This page sets no cookies and loads nothing from third parties. Our server logs each request as described in §2.3.

5.3 In marketing emails

Open and click tracking is turned off on Mersail's sending domain. Our emails contain no tracking image, and their links are not rewritten to send the click through Mersail or an email provider. Links to the Merchant's store carry campaign tags (utm_source=mersail, utm_medium=email, utm_campaign and sometimes utm_content) so that Shopify can show which campaign a store visit came from (§2.1); the link still goes straight to the store, and Mersail learns about a visit only if it leads to an order. Mersail discards any open or click event an email provider reports, so it does not record when a Customer opens an email or clicks a link in it. Merchants cannot turn tracking on, and we will not turn it on without telling Merchants in advance, as the Merchant Agreement provides.

6. Data we do not collect

We do not ask for or read payment card numbers, bank details, passwords or government identification numbers. If a Customer writes such information in a reply, it is stored with the reply and deleted on the reply schedule in §8.1. Our automatic screening does not detect it, so it may be sent to our AI provider with the reply (§2.3). Merchants' payments for paid plans are handled by Shopify (§2.4).

7. Security

Breaches. If we become aware of a breach of Customer or Merchant data we process for a Merchant, we notify Shopify within 24 hours and affected Merchants without undue delay, so that they can meet their own obligations. Where we are the Controller (§1.3), we notify the Garante per la protezione dei dati personali within 72 hours unless the breach is unlikely to result in a risk to people's rights and freedoms, and the people affected without undue delay where the risk is high.

Our security policy is available to Merchants and to Shopify on request. Please report vulnerabilities to security@mersail.com.

8. Data retention and deletion

8.1 Retention schedule

A deletion job runs once a day at 04:00 UTC and deletes data whose period has ended, so data can remain for up to a day after the end of each period below.

Data Kept for Then
Email bodies (the personalised HTML and plain-text copy of each email, and the personalised preview samples shown to the Merchant) 180 days after sending, or after creation if never sent The bodies are erased. The delivery record (recipient, subject line, status, send time) is kept for analytics for as long as the Customer's record is kept (below)
Email events (sent, delivered, bounced, unsubscribed, complaint) 395 days after the event Deleted
Access-log entries (store, staff user ID, action, kind of data, record count, route, time) 395 days Deleted
Privacy-request records (§2.3) 395 days after the request Deleted
Customer replies, including replies the Merchant has dismissed 365 days after receipt Deleted
Abandoned-checkout records 90 days after the checkout was first recorded Deleted
Orders and their line items 24 months from the order date. Older orders are not imported Deleted. The Customer's total spent, order count, last order date and segment are recalculated from the orders that remain
Customer records, with the delivery records, email events, replies and product recommendations of that Customer Until 24 months have passed since the Customer's last order, since the last email we sent them, and since we first stored them, whichever is latest. A Customer deleted in Shopify is deleted at the next daily check. Earlier on customers/redact (§8.2) Deleted. A Customer who is still subscribed in Shopify can be imported again by a later full sync, and the 24 months then start again
Products, campaigns, AI insights, plan and usage records, and Merchant settings While the app is installed Deleted with the store's data after uninstall
All data of a Merchant who has uninstalled, except the acceptance records and accounting records kept under §3.2 Until Shopify's shop/redact request arrives (about 48 hours after uninstall), and in any case no later than day 22 after the uninstall Permanently deleted from the database
Server and application logs 7 days Deleted by the host
Database backups None are kept. On the database plan we use, there are no automatic backups or point-in-time recovery, so deleted data cannot be restored. When we move to a plan with backups, we will update this policy before relying on them —
Emails to our privacy, security and support addresses As §3.2 Deleted

Points worth stating plainly:

8.2 Uninstall and Shopify privacy requests

9. Your rights

9.1 Customers of a Merchant's store

Mersail processes Customer data on the Merchant's behalf, so please send requests to access, correct, delete, restrict, object to or receive a copy of your data to the Merchant whose store you shopped at. If we receive such a request directly, we forward it to the Merchant without undue delay and help the Merchant respond, including through the Shopify requests in §8.2. To stop marketing email at any time, use the unsubscribe link in any email (§3.6). For our own server logs of requests to our unsubscribe pages, where we are the Controller, §9.2 applies.

9.2 Merchants, staff, visitors, and Customers for our server logs

For the data we control (§1.3), you have the right to:

Write to privacy@mersail.com. We reply within one month. For complex or numerous requests we may extend this by two further months, and we will tell you within the first month if we do. Uninstalling the app also deletes the Merchant's data (§8.1).

Complaints. You can complain to the Italian supervisory authority: Garante per la protezione dei dati personali, Piazza Venezia 11, 00187 Roma, Italy; telephone +39 06 696771; email and certified email (PEC) addresses are on its contact page; www.garanteprivacy.it. You can also complain to the supervisory authority where you live or work, or where the infringement took place.

9.3 United States

Where US state privacy laws apply (for example the California Consumer Privacy Act as amended by the California Privacy Rights Act, or the Virginia and Colorado privacy laws), Mersail acts as the Merchant's service provider or processor. We process Customer personal information only to provide the services the Merchant has asked for. We do not sell it or share it for cross-context behavioural advertising, we do not retain, use or disclose it outside our direct business relationship with the Merchant, and we do not combine it with personal information from other sources except as those laws allow. Consumers should send requests to the Merchant, and we help the Merchant respond. Our service-provider and processor terms are in clause 14 of the DPA.

10. Children's data

Mersail is a tool for businesses and is not directed to children. We do not knowingly collect personal data from children under 16 (or under 13 where COPPA applies). If we learn that a store's Customer data we hold includes a child's data, we will tell the Merchant and delete it on the Merchant's instruction. If data we control belongs to a child, we will delete it.

11. International data transfers

Mersail is established in Italy. Our application and database run in Frankfurt, Germany. Some Sub-processors store or process data outside the European Economic Area (§4.1): Resend sends email from the United States and stores account data, email metadata and logs there; Anthropic stores data in the United States and may process requests in any geography it uses; and Supabase, Render and Sentry may give support and operations staff outside the European Economic Area access to the systems they run for us. For personal data transferred out of the European Economic Area we rely on:

Recipient Transfer mechanism Data processing terms
Render Services, Inc. EU-U.S. Data Privacy Framework; the Standard Contractual Clauses in Render's DPA apply if the Framework does not render.com/dpa
Supabase Pte. Ltd. (Singapore) Standard Contractual Clauses (controller-to-processor and processor-to-processor modules), incorporated in Supabase's DPA supabase.com/legal/dpa
Plus Five Five, Inc. (Resend) EU-U.S. Data Privacy Framework; the Standard Contractual Clauses in Resend's DPA apply if the Framework does not resend.com/legal/dpa
Anthropic Ireland, Limited Contracting entity in the EU. Anthropic's DPA incorporates the Standard Contractual Clauses (controller-to-processor and processor-to-processor modules) for transfers out of the European Economic Area, including processing by Anthropic, PBC in the United States anthropic.com/legal/data-processing-addendum
Google Ireland Limited (Gmail, for mail to our own addresses, §4.2) Contracting entity in the EU. Google's onward transfers to Google LLC in the United States rely on the EU-U.S. Data Privacy Framework Google's terms of service and privacy policy (consumer mailbox; Google is not our Sub-processor)
Functional Software, Inc. (Sentry) Data stored in Frankfurt; for access from the United States, the EU-U.S. Data Privacy Framework, with the Standard Contractual Clauses in Sentry's DPA if the Framework does not apply (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)) sentry.io/legal/dpa

We checked participation in the Data Privacy Framework on the Data Privacy Framework List on 5 November 2026. The Framework rests on the European Commission's adequacy decision, Implementing Decision (EU) 2023/1795. If that decision is annulled or suspended, we will rely on the Standard Contractual Clauses and update this policy.

For personal data from the United Kingdom we rely on the UK Extension to the EU-U.S. Data Privacy Framework (Render, Resend, Sentry) or the UK Addendum to the Standard Contractual Clauses (Anthropic, Supabase, Resend, Render, Sentry). For personal data from Switzerland we rely on the Swiss-U.S. Data Privacy Framework (Render, Sentry) or the Standard Contractual Clauses with the Swiss amendments (Anthropic, Supabase, Resend).

Merchants who cannot accept transfers to a particular country should review §4 and contact us before using Mersail.

12. Changes to this policy

When this policy changes, we update the Version and Last updated fields at the top. We tell Merchants about material changes by email to the store's contact email address and in the app. We tell them at least 10 days before a new or replacement Sub-processor (including another AI provider) starts receiving Customer personal data, or before we send a Sub-processor a category of Customer personal data it did not receive before, and Merchants may object as set out in the DPA. If a Sub-processor must be replaced urgently, we tell Merchants as soon as we can. Because Merchants own the relationship with their Customers, Merchants remain responsible for informing their Customers where required.

13. Applicable law

This policy is provided under the GDPR (Regulation (EU) 2016/679) and Italian data protection law (Legislative Decree 196/2003, as amended). The law that governs the contract between Mersail and Merchants is set out in the Merchant Agreement at /terms.

14. Contact

Privacy questions or data requests: privacy@mersail.com

Security reports: security@mersail.com

Operator: Alberto Clemente, self-employed sole trader (lavoratore autonomo with a Partita IVA), registered address Viale della Repubblica 6, 48026 Russi (RA), Italy, VAT number (Partita IVA) IT02831350398; not registered in the Registro delle imprese (no REA number)

Changes in this version

Version 1.3 replaces version 1.2 (draft of 15 September 2026, never published).