Privacy Policy

This website

comeback.tansolutions.org is a website run by Tan Solutions. It sets no cookies and loads no advertising or third-party tracking scripts; page views are counted on the server that delivers the site, as described under “Visitor statistics” below, and a statistics script of our own runs only if you allow it, as described under “Statistics script” below. Fonts, images and styles are served from this domain; nothing is loaded from third parties.

The site is hosted on Cloudflare Pages. Like any web host, Cloudflare processes standard request data, such as your IP address and browser type, to deliver the pages and protect the site from abuse. See Cloudflare’s privacy policy.

If you email us, we use your message and email address to answer you. How support emails are handled is explained under “Support emails” below.

Questions: support@tansolutions.org

Visitor statistics

To see how this website is found and used, the server that delivers it counts page views itself. For each page you open, it records the page’s address (without query parameters), the time, where you came from (another website’s domain only, or, for our own pages, the page’s address without query parameters), campaign tags in the link (utm_source, utm_medium, utm_campaign, utm_content and utm_term), the country Cloudflare derives from your IP address, the page’s language, whether the page was not found, and, from your browser’s identification, only the device type (phone, tablet or computer) and the browser family. Once a day, it also records three things Cloudflare derives from your IP address: the region (such as the state or province), the continent and your time zone (such as UTC+1). Along with these, it records the operating system family (such as iOS or Windows) from your browser’s identification, and the first language set in your browser (two letters). The steps of the waitlist (sending the form, the sign-up being recorded and your confirmation) are counted too, without your email address. All of this comes from what your browser sends with every page request: no script is used for these page-view statistics, and for them nothing is stored on your device or read from it beyond that. The separate script described under “Statistics script” runs only with your consent.

To tell visits apart without cookies, the server combines your IP address, your browser’s identification and the site’s name with a random value that changes every day, and keeps only the resulting pseudonymous code (a salted SHA-256 hash). The random value is deleted once the day is over (UTC); after that, the code can no longer be worked out again from your IP address and your browser’s identification, and it is not linked to your visits on other days. We don’t store your IP address or your browser’s identification. Requests from known bots and from hosting or cloud networks are marked and counted separately; we don’t store which network it was.

Cloudflare (Cloudflare, Inc.) delivers this website and processes the statistics for us; they are stored in a Cloudflare database in the EU. Cloudflare may process page requests outside the EU under its data processing terms, which include the EU Standard Contractual Clauses. Each entry is deleted after 13 months. Only we use the statistics, to improve this website. We do not share them, and we do not combine them with your waitlist entry or any other data about you. This is based on our legitimate interest in understanding how our website is found and used and in improving it (GDPR Art. 6(1)(f)). You can object at any time (GDPR Art. 21) by writing to support@tansolutions.org. If your browser sends the Global Privacy Control signal, we do not record the visit. Because the code changes every day, we can usually not link earlier entries to you (GDPR Art. 11). Your rights are described under “Your rights” below.

Besucherstatistik

Um zu sehen, wie diese Website gefunden und genutzt wird, zählt der Server, der sie ausliefert, die Seitenaufrufe selbst. Bei jedem Seitenaufruf speichert er die Adresse der Seite (ohne Parameter), den Zeitpunkt, woher Sie kamen (bei anderen Websites nur deren Domain, bei unseren eigenen Seiten die Adresse der Seite ohne Parameter), Kampagnen-Kennzeichen im Link (utm_source, utm_medium, utm_campaign, utm_content und utm_term), das Land, das Cloudflare aus Ihrer IP-Adresse ableitet, die Sprache der Seite, ob die Seite nicht gefunden wurde, und aus der Kennung Ihres Browsers nur die Geräteart (Smartphone, Tablet oder Computer) und die Art des Browsers. Einmal am Tag speichert er außerdem drei Angaben, die Cloudflare aus Ihrer IP-Adresse ableitet: die Region (etwa das Bundesland oder die Provinz), den Kontinent und Ihre Zeitzone (etwa UTC+1). Dazu kommen die Art des Betriebssystems (etwa iOS oder Windows) aus der Kennung Ihres Browsers und die erste in Ihrem Browser eingestellte Sprache (zwei Buchstaben). Auch die Schritte der Warteliste (das Absenden des Formulars, die Aufnahme der Eintragung und Ihre Bestätigung) werden gezählt, ohne Ihre E-Mail-Adresse. All das stammt aus den Angaben, die Ihr Browser bei jedem Seitenaufruf ohnehin mitsendet: Für diese Zählung der Seitenaufrufe wird kein Skript eingesetzt, und dafür wird darüber hinaus auf Ihrem Gerät nichts gespeichert und nichts ausgelesen. Das unter „Statistik-Skript“ beschriebene, davon getrennte Skript läuft nur mit Ihrer Einwilligung.

Um Besuche ohne Cookies zu unterscheiden, verbindet der Server Ihre IP-Adresse, die Kennung Ihres Browsers und den Namen der Website mit einem täglich wechselnden Zufallswert und behält nur den daraus gebildeten pseudonymen Code (einen Hashwert mit Salt, SHA-256). Der Zufallswert wird gelöscht, sobald der Tag vorbei ist (UTC); danach lässt sich der Code nicht mehr aus Ihrer IP-Adresse und der Kennung Ihres Browsers neu bilden, und er ist nicht mit Ihren Besuchen an anderen Tagen verknüpft. Ihre IP-Adresse und die Kennung Ihres Browsers speichern wir nicht. Anfragen bekannter Bots und aus Netzen von Hosting- und Cloud-Anbietern werden gekennzeichnet und getrennt gezählt; das Netz selbst speichern wir nicht.

Cloudflare (Cloudflare, Inc.) liefert diese Website aus und verarbeitet die Statistik in unserem Auftrag; gespeichert wird sie in einer Datenbank von Cloudflare in der EU. Cloudflare kann Seitenaufrufe auch außerhalb der EU verarbeiten, auf Grundlage seiner Auftragsverarbeitungsbedingungen, die die EU-Standardvertragsklauseln enthalten. Jeder Eintrag wird nach 13 Monaten gelöscht. Nur wir nutzen die Statistik, um diese Website zu verbessern. Wir geben sie nicht weiter und führen sie nicht mit Ihrem Eintrag in der Warteliste oder anderen Daten über Sie zusammen. Grundlage ist unser berechtigtes Interesse, zu verstehen, wie unsere Website gefunden und genutzt wird, und sie zu verbessern (Art. 6 Abs. 1 lit. f DSGVO). Sie können jederzeit widersprechen (Art. 21 DSGVO), indem Sie an support@tansolutions.org schreiben. Sendet Ihr Browser das Signal Global Privacy Control, erfassen wir den Besuch nicht. Da der Code täglich wechselt, können wir frühere Einträge in der Regel nicht Ihnen zuordnen (Art. 11 DSGVO). Ihre Rechte finden Sie unten unter „Your rights“.

Launch waitlist

The waitlist is closed: Comeback is on the Shopify App Store now, and we take no new sign-ups. If you joined the launch waitlist, we store your email address, the language you chose, your country choice (the United States or another country), the page you signed up on, the version of the consent text you agreed to, and when you signed up, when the confirmation email was sent, when you confirmed and when the launch email was sent to you. We asked for the country only because US law requires a postal address in our emails to the United States. We also keep a hash of your confirmation link and the number of confirmation emails sent. We don’t store your IP address. To limit abuse, we counted sign-ups per IP address as a hash with a salt that changed daily, and deleted those counts within a day; this was based on our legitimate interest in keeping the list free of abuse (GDPR Art. 6(1)(f)).

Your address was only a request until you clicked the link in the confirmation email (double opt-in). Addresses that weren’t confirmed can no longer be confirmed, and they are deleted 7 days after sign-up. If you confirmed, we use your address only for one email about Comeback’s launch on the Shopify App Store, based on your consent (GDPR Art. 6(1)(a)). We keep it until you leave the list, and at the latest until 3 months after the launch email has gone out. Every email has a link to leave the list, which deletes your address at once. You can also write to support@tansolutions.org. Leaving doesn’t affect emails already sent.

The list is stored in a Cloudflare database (Cloudflare, Inc.) in the EU. Our own server sent the confirmation emails, and sends the launch email, through Google’s SMTP relay. While the list was open, Cloudflare Turnstile, a check by Cloudflare that keeps automated requests out and reads signals from your browser to do so, checked each sign-up; this was based on our legitimate interest in keeping automated sign-ups out (GDPR Art. 6(1)(f)). Our server is in Thailand. Cloudflare and Google may process your data outside the EU under their data processing terms, which include the EU Standard Contractual Clauses. Your rights are described under “Your rights” below.

Warteliste zum Start

Die Warteliste ist geschlossen: Comeback ist jetzt im Shopify App Store, und wir nehmen keine neuen Eintragungen mehr an. Wenn Sie sich in die Warteliste zum Start eingetragen haben, speichern wir Ihre E-Mail-Adresse, die gewählte Sprache, Ihre Angabe zum Land (USA oder ein anderes Land), die Seite, auf der Sie sich eingetragen haben, die Version des Einwilligungstexts, dem Sie zugestimmt haben, sowie die Zeitpunkte der Eintragung, des Versands der Bestätigungs-E-Mail, Ihrer Bestätigung und des Versands der E-Mail zum Start an Sie. Nach dem Land haben wir nur gefragt, weil E-Mails in die USA nach US-Recht eine Postanschrift enthalten müssen. Außerdem speichern wir einen Hashwert Ihres Bestätigungslinks und die Zahl der versendeten Bestätigungs-E-Mails. Ihre IP-Adresse speichern wir nicht. Um Missbrauch zu begrenzen, haben wir Eintragungen pro IP-Adresse als Hashwert mit einem täglich wechselnden Salt gezählt und diese Zählungen innerhalb eines Tages gelöscht; Grundlage war unser berechtigtes Interesse, Missbrauch der Liste zu verhindern (Art. 6 Abs. 1 lit. f DSGVO).

Ihre Adresse war nur eine Anfrage, bis Sie den Link in der Bestätigungs-E-Mail angeklickt haben (Double-Opt-in). Nicht bestätigte Adressen lassen sich nicht mehr bestätigen und werden 7 Tage nach der Eintragung gelöscht. Haben Sie bestätigt, nutzen wir Ihre Adresse nur für eine E-Mail zum Start von Comeback im Shopify App Store, auf Grundlage Ihrer Einwilligung (Art. 6 Abs. 1 lit. a DSGVO). Wir speichern sie, bis Sie sich austragen, längstens bis 3 Monate nach dem Versand der E-Mail zum Start. Jede E-Mail enthält einen Link zum Austragen, der Ihre Adresse sofort löscht. Sie können uns auch an support@tansolutions.org schreiben. Der Widerruf berührt nicht die Rechtmäßigkeit der bis dahin versandten E-Mails.

Die Liste wird in einer Datenbank von Cloudflare (Cloudflare, Inc.) in der EU gespeichert. Unser eigener Server hat die Bestätigungs-E-Mails über das SMTP-Relay von Google versendet und versendet auf demselben Weg die E-Mail zum Start. Solange die Liste offen war, hat Cloudflare Turnstile, eine Prüfung von Cloudflare, die automatisierte Anfragen fernhält und dafür Signale aus Ihrem Browser ausliest, jede Eintragung geprüft; Grundlage war unser berechtigtes Interesse, automatisierte Eintragungen fernzuhalten (Art. 6 Abs. 1 lit. f DSGVO). Unser Server steht in Thailand. Cloudflare und Google können Ihre Daten außerhalb der EU verarbeiten, auf Grundlage ihrer Auftragsverarbeitungsbedingungen, die die EU-Standardvertragsklauseln enthalten. Ihre Rechte finden Sie unten unter „Your rights“.

Statistics script (only with your consent)

The page-view counting described under “Visitor statistics” works without a script. Separately, and only if you click “Allow” in the bar at the bottom of the page, a small script of our own runs on this website. On each page, it measures which of our buttons and links you click (the button’s name and the page it leads to; for links to other websites, only their domain), how far you scroll (in steps of 25%), how long the page is in view (up to 30 minutes), the screen size class (phone, tablet, laptop or large screen), whether your device is set to light or dark mode, the steps you reach in the live demo, and how fast the page loads and responds (the measures LCP, CLS and INP). When you leave or hide the page, your browser sends these to our own server. They are stored with the same daily-changing pseudonymous code as the page views, in the same Cloudflare database in the EU, and deleted after 13 months, as described under “Visitor statistics”. The script sets no cookies, stores nothing on your device and reads nothing else from it.

Nothing loads before you choose, and “Decline” is as easy as “Allow”. To remember your choice, we store it in your browser’s local storage (the entry cb-stats-consent: “allow” or “decline” and the day you chose). We ask again after 12 months. If your browser sends the Global Privacy Control or Do Not Track signal, the script does not run and we do not ask.

The legal basis is your consent (GDPR Art. 6(1)(a); for running the script on your device, § 25(1) of the German TDDDG). You can change your choice or withdraw it at any time with “Privacy settings” at the bottom of every page; the script stops at once. Withdrawing does not affect what was recorded before. Questions: support@tansolutions.org.

Statistik-Skript (nur mit Ihrer Einwilligung)

Die unter „Besucherstatistik“ beschriebene Zählung der Seitenaufrufe kommt ohne Skript aus. Davon getrennt und nur, wenn Sie in der Leiste unten auf der Seite auf „Erlauben“ klicken, läuft auf dieser Website ein kleines eigenes Skript. Es misst auf jeder Seite, welche unserer Schaltflächen und Links Sie anklicken (den Namen der Schaltfläche und die Seite, zu der sie führt; bei Links zu anderen Websites nur deren Domain), wie weit Sie scrollen (in Schritten von 25 %), wie lange die Seite sichtbar ist (bis zu 30 Minuten), die Bildschirmklasse (Smartphone, Tablet, Laptop oder großer Bildschirm), ob Ihr Gerät auf hellen oder dunklen Modus eingestellt ist, welche Schritte Sie in der Live-Demo erreichen, und wie schnell die Seite lädt und reagiert (die Messwerte LCP, CLS und INP). Wenn Sie die Seite verlassen oder ausblenden, sendet Ihr Browser diese Angaben an unseren eigenen Server. Sie werden mit demselben täglich wechselnden pseudonymen Code wie die Seitenaufrufe in derselben Datenbank von Cloudflare in der EU gespeichert und nach 13 Monaten gelöscht, wie unter „Besucherstatistik“ beschrieben. Das Skript setzt keine Cookies, speichert nichts auf Ihrem Gerät und liest nichts weiter davon aus.

Vor Ihrer Entscheidung wird nichts geladen, und „Ablehnen“ ist genauso einfach wie „Erlauben“. Damit wir uns Ihre Entscheidung merken, speichern wir sie im lokalen Speicher Ihres Browsers (der Eintrag cb-stats-consent: „allow“ oder „decline“ und der Tag Ihrer Entscheidung). Nach 12 Monaten fragen wir erneut. Sendet Ihr Browser das Signal Global Privacy Control oder Do Not Track, läuft das Skript nicht, und wir fragen nicht.

Rechtsgrundlage ist Ihre Einwilligung (Art. 6 Abs. 1 lit. a DSGVO; für das Ausführen des Skripts auf Ihrem Gerät § 25 Abs. 1 TDDDG). Sie können Ihre Entscheidung jederzeit über „Datenschutz-Einstellungen“ unten auf jeder Seite ändern oder widerrufen; das Skript stoppt sofort. Der Widerruf berührt nicht die Rechtmäßigkeit der bis dahin erfassten Angaben. Fragen: support@tansolutions.org.

Support emails

To answer the emails you send to support@tansolutions.org, we use text-processing service providers in the USA. Before your email leaves our own server, names, email and postal addresses, phone numbers and order details are replaced with placeholders; this is automatic and can occasionally miss a detail. The text with placeholders goes to Anomaly Innovations, Inc. (USA), which prepares the reply with a service provider of its own in the USA or the EU. On the free plan we use, Anomaly may use the text and the reply to develop and improve its own services. Anomaly is not certified under the EU-U.S. Data Privacy Framework, and we have not confirmed that its Standard Contractual Clauses apply to the free plan we use. Emails that our filter recognises as being about billing, refunds of a payment to Comeback, legal questions or data requests, and emails it is unsure about, go instead to Anthropic, PBC (USA), which prepares the reply. Before replies are sent, Anthropic, PBC also processes the text with placeholders and the draft reply of the other support emails to check them. You can object to this processing at any time (GDPR Art. 21) by writing to support@tansolutions.org. You can also ask us at any time to delete your support emails from our mailbox; that doesn’t reach copies these providers have already received.

Support-E-Mails (auf Deutsch)

Um E-Mails an support@tansolutions.org zu beantworten, nutzen wir Dienstleister in den USA, die Texte automatisiert verarbeiten. Bevor Ihre E-Mail unseren eigenen Server verlässt, ersetzen wir Namen, E-Mail- und Postadressen, Telefonnummern und Bestelldaten automatisch durch Platzhalter; dabei kann in seltenen Fällen eine Angabe übersehen werden. Der Text mit Platzhaltern geht an die Anomaly Innovations, Inc. (USA). Sie erstellt die Antwort mithilfe eines eigenen Dienstleisters in den USA oder der EU. Im kostenlosen Tarif, den wir nutzen, darf Anomaly den Text und die Antwort verwenden, um ihre eigenen Dienste weiterzuentwickeln und zu verbessern. Anomaly ist nicht nach dem EU-US-Datenschutzrahmen zertifiziert, und wir haben nicht bestätigt, dass ihre Standardvertragsklauseln für den kostenlosen Tarif gelten, den wir nutzen. E-Mails, die unser Filter als Anfragen zu Abrechnung, Erstattungen von Zahlungen an Comeback, rechtlichen Fragen oder Datenanfragen erkennt, und E-Mails, bei denen unser Filter unsicher ist, gehen stattdessen an die Anthropic, PBC (USA), die die Antwort erstellt. Bevor Antworten versandt werden, verarbeitet die Anthropic, PBC außerdem den Text mit Platzhaltern und den Antwortentwurf der übrigen Support-E-Mails, um sie zu prüfen. Sie können dieser Verarbeitung jederzeit widersprechen (Art. 21 DSGVO); schreiben Sie dazu an support@tansolutions.org. Sie können außerdem jederzeit verlangen, dass wir Ihre Support-E-Mails aus unserem Postfach löschen; Kopien, die diese Anbieter bereits erhalten haben, sind davon nicht erfasst.

E-Mails der App (auf Deutsch)

Die App versendet ihre E-Mails, etwa die Eingangsbestätigung eines Widerrufs, über das SMTP-Relay von Google aus unserem Google-Workspace-Postfach. Google legt von jeder dieser E-Mails eine Kopie im Ordner „Gesendet“ dieses Postfachs ab; bei der Bestätigung eines Widerrufs enthält sie Ihren Namen, Ihre E-Mail-Adresse, die Bestellung und Ihre Erklärung. Unser Server löscht diese Kopien 4 Tage nach dem Versand. Die Löschung läuft alle 6 Stunden, eine Kopie ist also spätestens 4 Tage und 6 Stunden nach dem Versand gelöscht. Kann eine E-Mail nicht zugestellt werden, kann die Unzustellbarkeitsnachricht, die in unser Postfach zurückkommt, sie zitieren; diese Nachrichten löschen wir nach demselben Zeitplan, gerechnet ab ihrem Eingang. Nach unserer Löschung kann Google eine Kopie in unserem Google-Workspace-Konto noch bis zu 55 Tage lang wiederherstellen; anschließend löscht Google sie endgültig. Für die Sicherungskopien von Google gelten Googles eigene Löschfristen. Dass eine Widerrufsbestätigung versandt wurde, halten wir im Widerrufsprotokoll fest (Zeitpunkt, Nachrichten-ID der E-Mail und ein Prüfwert ihres Inhalts); dieser Eintrag wird mit dem Protokoll aufbewahrt und gelöscht, wie in Abschnitt 6 beschrieben.

Effective date: 29 September 2026 Last updated: 18 November 2026

This policy explains how the Comeback app for Shopify handles personal data. Comeback is made and run by Tan Solutions ("we", "us"). Contact: support@tansolutions.org.


1. Two roles

Two groups of people have data in the app, and we play a different role for each:

  1. Merchants — the Shopify stores that install Comeback, and the people who run them. For this data we are the controller. See §3.
  2. The merchant's customers — the shoppers who ask for a return, an exchange or an EU withdrawal through the app. For this data the merchant is the controller and we are the processor: we act only on the merchant's instructions, under our Data Processing Agreement. See §4.

If you are a shopper with a question about your own return, exchange or withdrawal, please contact the store you bought from. The store decides what happens to your request and your data. If you can't reach the store, email us at support@tansolutions.org and we will pass your request to the store and help it respond.


2. What the app does

Comeback gives a Shopify store:

  • Self-service returns and exchanges for customers who are signed in to their Shopify customer account.
  • An EU withdrawal form that customers can use without signing in, on stores that ship to the European Economic Area. It records the customer's declaration, sends the customer an acknowledgement of receipt by email and creates a return request for the merchant.
  • A merchant admin inside Shopify: rules, the request queue, the withdrawal log and analytics.
  • A Gorgias connection, if the store turns it on: its support team sees a customer's requests next to their ticket in Gorgias (§4.7).

3. Merchant data (we are the controller)

Data Where it comes from What we use it for
Store domain, store name, contact email, store address, time zone, currency and language Shopify, when you install the app and while it runs Running the app for your store. Your store name, contact email and address also appear in the emails the app sends to your customers, as the store's details.
Shopify access tokens and the permissions you granted Shopify, when you install the app Calling Shopify's API for your store. Stored encrypted.
The alert email address or addresses you enter You, in the app's settings Sending you withdrawal alerts and notices about customer data requests. Stored encrypted.
Your settings: return rules, return address and instructions, tags, notes to customers You Running the app as you configured it.
Plan and billing status Shopify's billing system Applying your plan. We never see card or bank details; Shopify handles all billing.
Usage events, such as "app installed", "setup step completed" or "plan changed" The app Understanding how the app is used, so we can improve it. The events hold no names, email addresses or customer details.
Emails you send us You Answering your questions; the service providers involved are listed under Support emails in §5.

The app does not store the names or email addresses of your staff. Shopify gives the app a store-level session, not a record of who is signed in.

Legal basis. We process this data to perform our contract with you (GDPR Art. 6(1)(b)). Usage events and the review window rest on our legitimate interest in improving the app (Art. 6(1)(f)).

Emails to you. We send you service emails: withdrawal alerts, notices about customer data requests and notices about your account or these policies. We send you marketing email only if you have opted in, and every marketing email has an unsubscribe link. How we email businesses that don't use Comeback yet is explained in §3.1.

Reviews. We never offer anything for a review. Whether we ask never depends on your mood, on how you might rate Comeback or on what you think of the app. The app may show Shopify's own review window at the end of a task you finish in the app, never when the app opens.

  • It appears at most twice per install.
  • The first time, your first completed return must be at least 7 days old, or your first exchange at least 3 days old.
  • The second time needs at least 60 more days and 25 more completed returns.
  • It never appears during our 14-day trial.
  • Shopify shows the window. We learn only Shopify's answer, such as shown, already reviewed or not now. We never see your rating or what you wrote.
  • The setting "Don't ask me to review Comeback" in Settings stops it.

We do not sell or share personal data for advertising, and we do not use it for profiling.

3.1 Businesses we email about Comeback

We sometimes email online stores that don't use Comeback yet, to tell them about the app. We use only an address that the store publishes on its own website for general contact (such as info@ or hello@), never a mailbox named after a person. We write only to stores in countries whose law allows such emails between businesses without prior consent: today, companies in the United Kingdom, stores in Ireland and France, and stores in the United States. We don't email stores in other EU or EEA countries this way.

Data Where it comes from What we use it for
The store's name, country and published email address The store's own website Writing to the store about Comeback
The page where we found the address, and the date Our own record Telling you where your address came from; every such email says it
For stores in the United Kingdom: that the business is a company (a company name or number) The store's website or the public Companies House register Checking that UK law allows the email
For stores in Ireland and France: the country of the business that runs the store, and for France its legal form and SIREN number The store's legal notice Checking that the law of that country allows the email
A short note on public facts about the store, such as the countries it ships to and what its refund policy says The store's own public pages Making the email relevant to the store
When we emailed, and whether the email bounced, was answered or was opted out of Our own records Not writing twice, and keeping to opt-outs
A copy of each email we send you Our mailbox Knowing what we wrote, and answering your replies and requests

Legal basis. Our legitimate interest in telling businesses about a product that fits their store (GDPR and UK GDPR Art. 6(1)(f)). Each email is written for one store, and we send only a small number a day.

Where it is processed. The list is kept on our own server in Thailand. The emails go out through Google's SMTP relay from our Google Workspace mailbox (§5), and the copies of our emails are kept in that mailbox. If you reply, your reply is handled like any support email, as described under Support emails in §5, including the service providers named there.

Your right to object. You can object at any time, free of charge: reply "unsubscribe", write to the opt-out address in the email, or write to support@tansolutions.org. We then don't email that address about Comeback again, and we move our copies of the emails we sent it to our mailbox's trash straight away (see "How long we keep it"). To keep to that, we keep the address on our do-not-email list, stored only as a keyed hash, not in readable form. You also have the rights in §7, and you can complain to the data protection authority where you live or work; in the United Kingdom, that is the Information Commission (formerly the Information Commissioner's Office, ICO); in Ireland, the Data Protection Commission; in France, the CNIL.

How long we keep it. We delete a store's entry from the list at the latest 3 months after the last email of the outreach it was collected for. If we don't email a store, we delete its entry at the latest 3 months after we found its address. We move each copy of an email we sent to our mailbox's trash 90 days after sending. This runs daily, so it happens at the latest 91 days after sending. If you object or ask us to delete your data, we move your copies to the trash straight away. Copies in the trash are deleted 30 days later, so a copy stays in our mailbox, including the trash, for at most 121 days. After that, Google can still restore it in our Google Workspace account for up to 25 more days, and then deletes it for good. On our server, the do-not-email entry and our send log are stored only as keyed hashes. We keep them so that we never write to an opted-out address again.

3.2 The withdrawal button check on our website

Our website has a free tool, the withdrawal button check. You enter a store's address. We then read up to four public pages of that Shopify store: its home page, its refund policy and up to two pages linked in its footer. We skip imprint pages, and we respect the store's robots.txt. Then we tell you whether we found a link or button with the legal wording for withdrawing from a contract.

What we process.

  • The store address you enter.
  • Your IP address and standard browser details, which reach Cloudflare with your request (§5).
  • The public pages we read. They hold the store's own business information, which can include a name, for example when one person runs the store.

Purpose. To answer your check, once.

Legal basis. Our legitimate interest in answering the check you ask for (GDPR Art. 6(1)(f)). The pages we read are ones the store publishes for its shoppers.

How long we keep it. We keep nothing: not the address you enter, not the pages we read, not the result. The tool runs on Cloudflare's network and keeps no logs of its own. There is no link to a result. Cloudflare may keep technical records of connections, such as IP addresses and times, to run and secure its network, under its own terms.

Who receives it. Cloudflare, Inc. hosts our website and runs the tool for us, as our processor. Where Cloudflare processes data, and under which safeguards, is set out in §5. The store sees a request from Cloudflare's network that names our tool. It does not receive your IP address.

Your rights under §7 apply here too.

Der Widerrufsbutton-Check auf unserer Website (auf Deutsch)

Auf unserer Website gibt es ein kostenloses Werkzeug, den Widerrufsbutton-Check. Sie geben die Adresse eines Shops ein. Wir lesen dann bis zu vier öffentliche Seiten dieses Shopify-Shops: die Startseite, die Rückerstattungsrichtlinie und bis zu zwei Seiten aus der Fußzeile. Impressumsseiten lesen wir nicht, und wir beachten die robots.txt des Shops. Danach sehen Sie, ob wir einen Link oder Button mit der gesetzlichen Beschriftung für den Widerruf eines Vertrags gefunden haben.

Welche Daten wir verarbeiten. Die eingegebene Shop-Adresse. Ihre IP-Adresse und übliche Browserangaben, die mit Ihrer Anfrage bei Cloudflare ankommen (Abschnitt 5). Die gelesenen öffentlichen Seiten. Sie enthalten Angaben des Shops über sein Geschäft, unter Umständen auch einen Namen, etwa wenn eine einzelne Person den Shop betreibt.

Zweck. Ihre Prüfung einmal zu beantworten.

Rechtsgrundlage. Unser berechtigtes Interesse, die von Ihnen angefragte Prüfung zu beantworten (Art. 6 Abs. 1 lit. f DSGVO). Die gelesenen Seiten veröffentlicht der Shop selbst für seine Kundschaft.

Speicherdauer. Wir speichern nichts: weder die eingegebene Adresse noch die gelesenen Seiten noch das Ergebnis. Das Werkzeug läuft im Netz von Cloudflare und führt keine eigenen Protokolle. Einen Link zum Ergebnis gibt es nicht. Cloudflare kann technische Verbindungsdaten wie IP-Adressen und Zeitpunkte nach eigenen Bedingungen aufbewahren, um sein Netz zu betreiben und zu schützen.

Empfänger. Cloudflare, Inc. betreibt unsere Website und das Werkzeug für uns als Auftragsverarbeiter. Wo Cloudflare Daten verarbeitet und mit welchen Garantien, steht in Abschnitt 5. Der Shop sieht eine Anfrage aus dem Netz von Cloudflare, die unser Werkzeug nennt. Ihre IP-Adresse erhält er nicht.

Ihre Rechte nach Abschnitt 7 gelten auch hier.


4. Customer data (the merchant is the controller; we are the processor)

We process the personal data of the merchant's customers only to run the features below, on the merchant's behalf. The merchant decides why this data is collected and what happens to each request. Merchants are responsible for telling their customers about this processing in their own privacy notice; this section is written to help them do that accurately.

4.1 Returns and exchanges (signed-in customers)

Data Source Purpose Kept by us?
Shopify customer ID The customer's signed-in Shopify session Checking that the order belongs to the customer Yes, with the request
Order number, items, variants, quantities, prices paid, product images and fulfilment status Shopify Checking eligibility and building the return or exchange Yes, with the request
Shipping and billing country (country only; we never read the street address from Shopify) Shopify Applying the merchant's rules for that region No, read when needed
Customer name Shopify Showing the merchant who made the request No, read from Shopify when the merchant opens the request
Customer email address and language Shopify Sending the customer our confirmation or decline email No, read from Shopify when the email is sent
Return reasons and any notes the customer types The customer Letting the customer explain the return Yes, notes stored encrypted
A note the merchant writes when declining The merchant Telling the customer why Yes, stored encrypted
The return parcel's carrier and tracking number The customer or the merchant Adding the parcel to the Shopify return so the store can follow it The number: no. We send it to Shopify, which keeps it on the return, and read it from there; our server logs keep only its last 4 characters. We keep the carrier, that a parcel was added and by whom, and a keyed one-way value of the number that stops it being added twice.
A return label file, which can show the customer's name and postal address The merchant, if they upload one Adding the label to the Shopify return, so Shopify can email it to the customer and the customer can download it from the return page No. The file passes through Cloudflare (§5) and our server to Shopify, in memory only. We check only that it is a PDF of at most 5 MB; we don't read what it shows, and we never save or log it. Shopify keeps it on the return. We read the download link from Shopify each time the page loads and don't store it. We keep only that a label was added, by whom, and the carrier.
Customer tags and the number of recent returns Shopify The optional frequent-returner and review-tag checks (§4.4) Only the resulting flag

Customers should not type sensitive information, such as health details, into a note.

4.2 The EU withdrawal form (customers who don't sign in)

Data Source Purpose Kept by us?
Full name and email address, as typed The customer The content the law requires in a withdrawal declaration, and the address for the acknowledgement of receipt Yes, stored encrypted, plus a keyed one-way index of the email address used for matching, redaction and abuse limits
Order number as typed, and the items selected The customer Identifying the contract, or the part of it, being withdrawn from Yes
The matched order's ID; the order's email address, read only to check the match; where the buttons are shown in the country's or the customer's own language, the order's language and country Shopify Finding the order the declaration refers to, and showing the withdrawal buttons in words the customer reads The order ID, yes; the order's email address, no; the language and country only as part of the record below
Date and time of receipt, a reference number and the page language; where the buttons are shown in the country's or the customer's own language, also the country and language of the words shown, where that language came from (the order, the store's link, the page or the country's default) and the version of our word list The app The record of the declaration, including which statutory words the customer saw Yes
A fingerprint (hash) of the declaration's content, and a fingerprint of the acknowledgement as sent The app Showing later that the record and the acknowledgement were not changed Yes
Email sending records: message ID and whether sending succeeded The app Showing that the acknowledgement was sent Yes
IP address The customer's connection Limiting abuse of a public form No. Only a keyed one-way value derived from it is kept, for about 48 hours (§6). If our server can't be reached, it is part of the encrypted submission held at Cloudflare (§5)

A declaration is never refused. If a submission goes over the abuse limits, or looks automated (for example, a hidden anti-spam field was filled in), it is still recorded and shown to the merchant; only the emails are slowed down or, for suspected spam, not sent.

Unmatched declarations. If the order number and email address don't match an order, the customer can still submit the declaration. We record it and pass it to the merchant for review, because refusing it could deny a genuine customer a legal right. So we may hold a name, an email address and a declaration from someone who turns out not to be a customer of the store. It is handled and deleted like any other declaration (§6).

4.3 Return history imported from a previous returns app

A merchant can upload the returns export (a CSV file) from its previous returns app, so that its analytics include past returns.

Data Source Purpose Kept by us?
The previous app's return number, the order number and the matched Shopify order ID; the return's status and outcome; the dates it was requested, approved, rejected, expired, refunded, exchanged and resolved; the currency and the return, exchange and refunded amounts; for each item, its SKU and title (where the file has them), the matched Shopify line item ID, the return reason and sub-reason (the merchant's own labels, at most 100 characters each) and the quantity The file the merchant uploads; the order ID from Shopify Showing the merchant's past returns next to Comeback's own, in its analytics Yes
Everything else in the file, including customer names, email addresses, addresses, notes, staff email addresses, gift card codes and tracking numbers The file the merchant uploads None No. These columns are read while the file is parsed and dropped at once. They are never stored or logged.

Until the import job has run, the kept fields wait on our server in a staging record. That record is deleted when the job ends, and at the latest 24 hours after the upload. The file itself is never saved. We also keep the headings of the columns the merchant matched (not the values under them), so that the next file with the same headings is matched automatically. A return whose order can't be found in Shopify is not imported; only the count is shown. To link a return to its order, we look up the order in Shopify by its order number and read only the order ID, its order number, and the line item IDs and SKUs, never customer details. Returns requested more than 24 months ago are not imported. Imported returns are included in our answer to a customer data request and deleted on a customer deletion request, both by order ID.

4.4 Automated steps

The app can approve a return or exchange automatically when it meets the merchant's rules. It never declines a request automatically. A request that fails a rule, goes over the plan's monthly allowance, or matches the merchant's frequent-returner threshold or review tags goes to the merchant for a manual decision. The frequent-returner and review-tag checks only send a request to review; the customer is not told about them, and they never block a request on their own. A customer who disagrees with any outcome can ask the store to look at it again.

The merchant, as controller, decides the legal basis for its processing. Our understanding, offered to help:

Processing Likely basis
Returns and exchanges the customer asks for Art. 6(1)(b): performing the sales contract and the store's returns policy
The EU withdrawal form and its acknowledgement Art. 6(1)(c): the merchant's legal obligation to provide a withdrawal function and to acknowledge receipt (Art. 11a of Directive 2011/83/EU, and national laws such as § 356a BGB). We carry out that obligation for the merchant, as its processor, on its instruction.
Abuse limits on the public form Art. 6(1)(f): preventing abuse of a form that needs no sign-in
Frequent-returner and review-tag checks Art. 6(1)(f): applying the store's return policy consistently
Imported return history Art. 6(1)(f): the merchant's interest in analysing its own past returns. Only pseudonymous data is kept, linked to a person only through the order.
Showing the customer's requests in the store's Gorgias (§4.7) The same basis as the request itself (rows above): the store answers the customer's own questions about it. Otherwise Art. 6(1)(f): the store's interest in answering customers quickly and correctly.
Blocking key guessing on the Gorgias connection (§4.7) Art. 6(1)(f): keeping the store's data secure
Claims and their photos (§4.8) Art. 6(1)(b): the store's duties for damaged, defective, wrong or missing items under the sales contract and the law. Keeping the photos for 120 days after the claim closes: Art. 6(1)(f), the store's interest in having evidence if a card payment is disputed.

4.6 What we don't collect

  • No payment card or bank details. Shopify handles all payments and refunds.
  • No file uploads from customers, except photos added to a claim (§4.8).
  • No government ID, health data or other special categories of data. None of our forms ask for them.
  • No tracking cookies, analytics pixels or advertising identifiers on the customer-facing pages.

4.7 Gorgias (only if the store connects it)

If a store connects Gorgias, its support team sees the status of your return, exchange or withdrawal in Gorgias. Gorgias sends us your email address only to find your requests; we don't keep it.

Gorgias is a helpdesk that the store chooses and has its own agreement with. The store connects it in the app and can disconnect it at any time (§5, "Not sub-processors").

Data Source Purpose Kept by us?
Your email address, from the store's support ticket Gorgias, when the store's support team opens or updates your ticket Finding your requests. We look for withdrawals made with that address, and for the one customer in the store's Shopify customers whose address matches it exactly. If no customer or more than one matches, no returns or exchanges are shown. No. So that one ticket doesn't search Shopify again and again, we hold a keyed one-way value of the address, with the matching Shopify customer ID, in memory for up to 10 minutes. Our server log keeps a short part of that value, never the address.
For your 5 most recent requests at most: the kind of request, the order number (or the withdrawal's reference number), its status and next step, the option you chose, item names and quantities, the value, the date you made it, and a link that opens it in the store's Shopify admin Our records of your requests Showing the store's support team where your request stands We send it to Gorgias for the store, and Gorgias keeps it under the store's own agreement. We send no name, email address, postal address, phone number, note or return reason.
The IP address of a caller that sends a key that doesn't exist The caller's connection Blocking anyone who tries to guess a key No. Held in memory for at most one minute. It is never stored or logged.

4.8 Claims with photos (damaged, defective, wrong or missing items)

A signed-in customer can make a claim for an item that arrived damaged, defective or wrong, or didn't arrive. The customer can add up to 5 photos per item to show the problem. The store's staff see the photos in the app and can download them. Photos can show a person, a home or an address label, so customers should photograph only the item and its packaging.

Data Source Purpose Kept by us?
The claim: the order, the items, what is wrong and any note The customer; the order from Shopify Letting the store decide the claim Yes, like a return request (§4.1); notes stored encrypted
Photos the customer adds The customer Showing the store the problem Yes, encrypted. We resize each photo and save it as a new image, which removes all hidden data, including the location where it was taken. We never save the original file. Photos are never sent in emails, exports or to other apps. A photo not added to a sent claim is deleted after 24 hours. The others are deleted 120 days after the claim closes (§6). If the customer has to send the item back and doesn't, 120 days after the return window ends.

5. Where data is processed, and who helps us

Our own server. The app and its PostgreSQL database run on one server that we operate ourselves, in Thailand. No hosting or database company runs it. Connections to the app reach this server through Cloudflare (see below). Customer data is stored at Cloudflare only while our server can't be reached (see "If our server can't be reached").

If our server can't be reached. A return request or withdrawal sent through the store while our server can't be reached may be received by our Cloudflare Worker instead. The Worker encrypts it with a key that only our own server holds. It then stores it at Cloudflare, in the EU, until our server collects it. That is normally within a minute of our server being back. An item still waiting after 14 days is deleted at Cloudflare. An item our server collected but could not process stays at Cloudflare, encrypted, until we fix the cause and collect it again, or delete it. The stored content is encrypted; the Worker reads it only in the moment before it encrypts it. Stored in readable form are only the store's address, a random item id and reference number, the time it was received, its size and technical flags. To limit abuse, we count submissions per IP address using a salted hash, with a new salt each day. That is pseudonymised, not anonymous. The counters are deleted within two hours. The Worker also keeps a list of the stores that use the app (store address, language and settings; no customer data), so it can turn away requests for other stores. Once our server has collected an item, it is handled like any other request or declaration, and deleted at Cloudflare.

Service providers that process personal data for us (sub-processors):

Provider What it does Data involved Location Safeguard
Google (Google Workspace) Sends the app's emails through Google's SMTP relay, and hosts our mailbox, which keeps a copy of each app email for 4 days (§6) and of each of our emails to businesses for up to 121 days, including 30 days in the trash (§3.1) Recipient name and email address and the email's content: acknowledgements, confirmations and decline emails to customers, alerts to merchants, support emails, and our emails to businesses (§3.1) Google's data centres, including in the USA Google's Cloud Data Processing Addendum, which includes the EU Standard Contractual Clauses
Cloudflare, Inc. (Cloudflare Workers, Durable Objects and Cloudflare Tunnel) Receives every connection to the app, from browsers and from Shopify, and forwards it to our server through an encrypted tunnel. The encryption of the connection ends at Cloudflare, so Cloudflare processes the content of requests and responses while they pass through. Our Cloudflare setup keeps no request logs. Only while our server can't be reached, it also stores return requests and withdrawals, encrypted, until our server collects them (see "If our server can't be reached"). Everything sent to or from the app, in transit: the data described in §3 and §4 (names, email addresses, order details, return reasons and notes), the content of Shopify's webhooks, the pages and exports merchants open, and IP addresses and browser details. Cloudflare may keep technical records of connections, such as IP addresses and times, to run and secure its network, under its own terms. Stored only while our server can't be reached: that content, encrypted with a key only our server holds; in readable form, the store's address, a random item id and reference, the time received, the size and technical flags; and salted IP-address hashes for abuse limits. The Worker also keeps a list of the stores that use the app (store address, language and settings; no customer data), so it can turn away requests for other stores. USA; requests are handled in Cloudflare's data centres worldwide, usually the one nearest the sender. Data stored while our server can't be reached: EU Cloudflare, Inc. is certified under the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework; Cloudflare's Data Processing Addendum also includes the EU Standard Contractual Clauses, the UK Addendum and the Swiss terms

Support emails. To answer the emails sent to our support address, we use text-processing service providers in the USA. Before an email leaves our server, names, email and postal addresses, phone numbers and order details are replaced with placeholders; this is automatic and can occasionally miss a detail. The text with placeholders goes to Anomaly Innovations, Inc. (USA), which prepares the reply with a service provider of its own in the USA or the EU. On the free plan we use, Anomaly may use the text and the reply to develop and improve its own services. Emails that our filter recognises as being about billing, refunds of a payment to Comeback, legal questions or data requests, and emails it is unsure about, go instead to Anthropic, PBC (USA), which prepares the reply. Before replies are sent, Anthropic, PBC also processes the text with placeholders and the draft reply of the other support emails to check them. You can object to this processing at any time (GDPR Art. 21) by writing to support@tansolutions.org. You can ask us to delete your support emails from our mailbox; that doesn't reach copies these providers have already received. The same facts in English and German are in the "Support emails" section at the top of this page.

Not sub-processors. Shopify is the platform the app runs on; merchants have their own agreement with Shopify. Gorgias, if a store connects it, is the store's own helpdesk, under the store's own agreement with Gorgias. We send it request details only because the store told us to, by connecting it (§4.7). Where Gorgias processes that data, and under which safeguards, is set by the store's agreement with Gorgias. Our website, comeback.tansolutions.org, is a separate static site on Cloudflare Pages and holds no app data.

International transfers. Thailand has no adequacy decision from the European Commission or the UK. When an EEA, UK or Swiss merchant uses the app, its customers' data is processed in Thailand under our Data Processing Agreement, which incorporates the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914, Module 2), the UK International Data Transfer Addendum and the Swiss adjustments. Merchant data (§3) is processed by us in Thailand under the protections in this policy. Google and Cloudflare process data in the USA and elsewhere under their own data processing terms. For support emails (see above), Anomaly Innovations, Inc. and Anthropic, PBC are in the USA, which has no general adequacy decision. Neither is certified under the EU-U.S. Data Privacy Framework. The terms under which we use Anthropic's service include no Standard Contractual Clauses; for Anomaly Innovations, Inc., we have not confirmed that its Standard Contractual Clauses apply to the free plan we use. Anomaly's own service provider is in the USA or the EU. We checked Anthropic, PBC on 1 October 2026 and Anomaly Innovations, Inc. on 16 November 2026. You can ask us for a copy of the relevant safeguards at support@tansolutions.org.

Thai law. We are established in Thailand, so Thailand's Personal Data Protection Act B.E. 2562 (2019) also applies to how we handle personal data.


6. How long we keep data

Data How long
Shopify access tokens and sessions Deleted as soon as Shopify tells us the app was uninstalled.
Everything else about a store: settings, requests, the withdrawal log, data-request records and usage events Deleted when Shopify sends its shop-deletion request (shop/redact), which Shopify sends 48 hours after the app is uninstalled. We delete the data when the request arrives; Shopify allows up to 30 days. If the store reinstalls the app before then, the data is kept, because the store is using the app again.
One customer's requests and withdrawal declarations Deleted when Shopify sends a customer-deletion request (customers/redact) for that customer. We find the data by the customer's Shopify ID, the orders Shopify lists and the email address, so an unmatched declaration made with the same email address is deleted too. Shopify sends this request 10 days after the customer asks, or, if the customer ordered in the last 6 months, once 6 months have passed since that order.
Imported return history Deleted 24 months after the return was requested, or earlier when the merchant deletes its imported history, on a customer deletion request for that order, or with the store's data. The staging record of an upload is deleted when the import job ends, and at the latest 24 hours after the upload.
Records of orders deleted on a customer deletion request (the Shopify order ID only), kept so that a later import can't bring them back 24 months, or with the store's data.
A declaration from someone who was never a customer of the store Deleted with the store's data, or earlier if the merchant asks us to delete it.
Abuse-limit values derived from IP addresses, email addresses or customer IDs Deleted about 48 hours after their time window.
Claim photos (§4.8) A photo not added to a sent claim: 24 hours after upload. The others: 120 days after the claim closes, which means it is completed, declined, cancelled or failed, or the store has processed it and the customer keeps the item. If the customer has to send the item back and doesn't, 120 days after the return window ends. Deleted earlier on a customer deletion request (customers/redact) or with the store's data (shop/redact). Backups keep deleted photos for up to 14 days.
A Gorgias lookup (§4.7) The email address is not kept. The keyed value of it and the matching customer ID: in memory, at most 10 minutes. The IP address of a caller that sends a key that doesn't exist: in memory, at most one minute.
Records of Shopify webhook deliveries (store domain and event type, no customer data) 30 days.
A return request or withdrawal received while our server couldn't be reached At Cloudflare, encrypted, until our server collects it, normally within a minute of our server being back. If it is still waiting after 14 days, it is deleted at Cloudflare. An item our server could not process is kept there, encrypted, until we fix the cause or delete it. Once collected, it is kept like any other request or declaration (rows above).
Returns-fallback bookkeeping on our server: the item id, its reference number and outcome, and the number of processing attempts and the type of error (no name, email address or postal address) 30 days, counted from receipt (the attempt count: from the last attempt). Deleted earlier with the store's data (shop/redact).
Backups We back up the database every night, encrypt each backup, and keep the last 14 backups. Data deleted from the database therefore disappears from backups within 14 days.
Our server's technical logs These record each request's method, web address, status and timing. They contain no names, email addresses or message text, but an address can contain a store's domain, an order number a merchant searched for, and the Shopify ID of an order, a customer or a staff account. The log files rotate by size, and older files are overwritten.
Emails the app sends We send them through Google's SMTP relay from our Google Workspace mailbox. Google files a copy of each one in that mailbox's Sent folder; for the acknowledgement of an EU withdrawal, the copy contains the customer's name and email address, the order and the declaration. Our server deletes these copies 4 days after they were sent. The deletion runs every 6 hours, so a copy is gone at most 4 days and 6 hours after it was sent. If an email can't be delivered, the bounce notice that comes back to our mailbox can quote it; we delete bounce notices on the same schedule, counted from when they arrive. After we delete a copy, Google can still restore it in our Google Workspace account for up to 55 days, and then deletes it for good. Google's backups follow Google's own deletion timelines. Our record that a withdrawal acknowledgement was sent (the time, the email's message ID and a fingerprint of its content) is part of the withdrawal log and is kept and deleted with it (rows above). Google keeps delivery records (sender, recipient, time and status, not the content) for a period Google sets. Recipients keep their own copies.
Support emails Kept in our mailbox while we need them to help you and to keep a record of what we agreed. We delete them when you ask, unless we need them to establish or defend a legal claim.
Businesses we email about Comeback (§3.1) The store's entry is deleted at the latest 3 months after the last email of the outreach it was collected for. An entry we never email is deleted at the latest 3 months after we found the address. The copy of each email we sent moves to our Google Workspace mailbox's trash 90 days after sending (at the latest 91 days). It is deleted from the trash 30 days later, so it stays in our mailbox, including the trash, for at most 121 days. Google can then still restore it for up to 25 more days, and then deletes it for good. If a store objects or asks for deletion, we move its copies to the trash straight away. The do-not-email entry and our send log, stored on our server only as keyed hashes, are kept so that we never write to an opted-out address again.
The withdrawal button check on our website (§3.2) Not kept. The store address you enter, the pages we read and the result are used for one answer, then discarded. Cloudflare may keep its own connection records under its own terms.

Merchants: export before you uninstall. Your withdrawal log can be exported as a CSV file on every plan, and your request history on the Growth and Pro plans. After your store's data is deleted, we cannot recover it. The customer keeps the acknowledgement email as their own record, and the Shopify returns the app created stay in your Shopify admin; they are Shopify's records, not ours.


7. Your rights

Customers of a store. The store is the right place to ask for access to, correction or deletion of your data, or to object to its use. If you write to us, we will pass your request to the store and help it respond. When Shopify tells us about a customer data request (customers/data_request), we notify the merchant by email, and the app offers the data we hold about that customer as a download the merchant can pass on.

Merchants. You can ask us for access to, correction, deletion or a copy of your data, or object to or ask us to restrict its use, at support@tansolutions.org. Uninstalling the app also starts deletion (§6). We answer within 30 days. You can also complain to your data protection authority; in Thailand, that is the Personal Data Protection Committee.


8. Security

  • In transit: every network connection is encrypted. Browsers and Shopify connect to Cloudflare with TLS; Cloudflare, our sub-processor (§5), forwards the traffic to our server through an encrypted tunnel, so the content is readable at Cloudflare while it passes through. From our server to Shopify and to Google's mail relay, connections use TLS.
  • Encrypted fields: customer names and email addresses from the withdrawal form, customers' notes, claim photos, merchants' decline notes, merchants' alert email addresses and Shopify access tokens are encrypted individually with AES-256-GCM. Each value is bound to its field and store, so it can't be decrypted anywhere else, and the keys are kept outside the database.
  • Everything else in the database (order numbers and IDs, item titles, settings) is stored without field encryption, on a server we operate ourselves. The server's disks are not fully encrypted today.
  • The withdrawal log can't be edited. The database itself rejects changes to declarations, and allows deletion only through the redaction steps in §6. Each declaration stores a fingerprint of its content, so any change made outside the app can be detected.
  • Access: only we operate the server. The app and database accept connections only from the server itself; outside traffic reaches the app only through the encrypted Cloudflare tunnel, which our server opens outwards, so the server accepts no connections from the internet.
  • Backups: each nightly backup is a full copy of the database, encrypted with public-key encryption (age) before it is stored on a second disk in the same server; the key that decrypts it is kept offline, never on the server, and the last 14 backups are kept.
  • Separate environments: tests run on separate, temporary databases with made-up data. Production data is never copied into test or development systems.
  • Breaches: if a personal data breach affects a merchant's data, we tell the merchant without undue delay, and within 48 hours of becoming aware of it.

9. Children

Comeback is a business tool for merchants. It is not directed at children, and we do not knowingly collect personal data from children.


10. Changes to this policy

If we change how personal data is used, we tell merchants by email to their Shopify account address and with a notice in the app, at least 14 days before the change takes effect. Other changes are posted on this page with a new "Last updated" date.


11. Contact

Tan Solutions support@tansolutions.org

This one address is for support, privacy questions and requests about your data.