Privacy Policy: Shopatch Sats Price
Last updated: 24 August 2026
This policy covers the Shopify app Sats Price, running at sats.shopatch.com. The website shopatch.com is covered by a separate policy, because a different relationship applies there: towards site visitors Shopatch is the controller, while inside the app Shopatch processes shop data on behalf of the merchant.
Who is responsible
Shopatch, Werner Mathias Bundschuh, an Individual Entrepreneur registered in Georgia (IE Reg. No. B25175473, see Legal Notice). Contact: [email protected].
The place of business is outside the EU, so a representative under Art. 27 GDPR has been appointed. For data subjects in the EU, that representative is the direct route.
Representative in the EU
We value your privacy and your rights as a data subject and have therefore appointed Prighter Group with its local partners as our privacy representative and your point of contact for the following regions:
- European Union (EU)
Prighter gives you an easy way to exercise your privacy-related rights (e.g. requests to access or erase personal data). If you want to contact us via our representative, Prighter or make use of your data subject rights, please visit the following website: https://app.prighter.com/portal/shopatch
The short version
The app processes no personal data of your customers. That is not a promise, it is a design decision you can read off the single permission it asks for:
read_themes
Deliberately not requested: write_themes, read_products, read_orders, read_customers, read_customer_events. The app cannot retrieve customer data at all, and it cannot write to your theme files. What we do not hold, we cannot mishandle.
The one permission serves exactly one purpose: to read whether you have switched the block on in your published theme, so the app can tell you instead of guessing. That single question is the most expensive one in support.
Two roles, and they are not the same
For your shop data (the name of your published theme and its app embed settings) Shopatch acts as your processor. The data is yours; it is read only to answer whether the second price is switched on, and only on your instruction, which you give by installing the app.
For your own contact details (the shop domain) Shopatch is the controller, because that data serves our relationship with you as a customer, not the running of your shop.
What the app reads
| What | Why | Stored |
|---|---|---|
| The app embed settings of your published theme | so the start page can say whether the block is on | no, read and dropped |
| Your shop domain | so the installation can be recognised at all | yes, in the session |
| The currency a page is showing | so the rate matches the price beside it | no |
| Your subscription status | because the second price is what you pay for | no, asked of Shopify each time and held in memory for minutes |
Theme settings are fetched, used and dropped. They are not written to disk and not sent anywhere else.
What the app stores
- The session: your shop domain and an offline access token, so the app can work at all. That is one table, and it is the only one the app has.
- Nothing else. There is no copy of your catalogue, no price history, no record of your visitors, and no analytics of any kind.
The session table comes from Shopify's app template and carries columns for logged-in staff accounts (name, email). This app uses offline sessions only, so those columns stay empty.
The app writes operational log lines while it runs. They can name your shop domain and an error message. They never contain customer data.
What happens in your storefront
The block asks for the rate at your own shop domain, through Shopify's app proxy. Your shoppers' browsers therefore never contact our servers, and no request of theirs carries our name.
Shopify forwards that request to us with a signature, the shop domain, a timestamp and the requested currency. When a customer is signed in to your shop, Shopify also adds a logged_in_customer_id. The app neither uses nor stores it; it is not written to disk and it plays no part in what the block shows.
The block sets no cookie. It keeps the fetched rate in the browser's sessionStorage for the length of that tab, so a visitor browsing ten products does not trigger ten requests. What is kept there is a number and a timestamp, nothing about the person.
Where the rate comes from
Our server, not the visitor's browser, fetches the exchange rate from public price endpoints: mempool.space, and beneath it a broad source for currencies mempool.space does not know. Those requests carry no data about you, your shop or your customers. They ask a public price and nothing else.
Legal basis
- Showing the second price, reading the embed status, checking the subscription: performance of a contract, Art. 6(1)(b) GDPR. This is the service you install the app for.
- Shop data: processed on your behalf under Art. 28 GDPR. Towards your own customers you remain the controller.
Who else processes the data
The app runs entirely on infrastructure we operate ourselves. One processor is involved in operating it:
| Processor | What for | Where |
|---|---|---|
| Scaleway SAS | application hosting (Serverless Containers) | Paris, France (fr-par) |
| Scaleway SAS | database (PostgreSQL), holding the session table | Paris, France (fr-par) |
Scaleway SAS is a French company; the data stays inside the EU and no transfer to a third country takes place. Shopify itself is not our processor: it is the source of the data, and you already have your own agreement with it.
There is no transfer to advertising networks, analytics services or AI providers. No part of your shop data is used to train a model.
How long it is kept
- While the app is installed, the session stays, because without it the app cannot answer your shop at all.
- When you uninstall the app, the session is deleted immediately (
app/uninstalled). - On erasure (
shop/redact, which Shopify sends 48 hours after uninstallation) everything belonging to your shop is deleted. In practice that is the session, because there is nothing else. - Your theme is never written to by us, in either case: the app holds a read permission only. When you uninstall, the block disappears from your storefront and from the theme editor. What stays in your theme settings is a single inert line that your own theme editor wrote when you switched the block on, and it restores your setup if you ever install the app again. This was measured on 24 August 2026, not assumed.
The webhooks the app listens to
| Webhook | What happens |
|---|---|
customers/data_request | we confirm that no customer data is held |
customers/redact | there is nothing to delete, see above |
shop/redact | the session of that shop is deleted, and there is nothing else to delete |
app/uninstalled | the session is deleted |
app/scopes_update | the stored permissions are brought in line |
Every one of them verifies Shopify's signature before doing anything. A request without a valid signature is rejected.
Your rights
You have the right of access, rectification, erasure, restriction, data portability and objection, and the right to lodge a complaint with a supervisory authority. The quickest route is the Prighter portal linked above, or [email protected].
What the app deliberately does not do
- It writes nothing into your theme. Theme settings are read to recognise whether the block is on, never written.
- It reads no products, orders or customers. It takes the price from the page as rendered, so it does not need to ask for it.
- It sets no cookie and loads no tracker in your storefront.
- It counts nothing. There is no analytics, no visitor count and no record of which pages were viewed.
- It sends nothing to an AI provider.
Changes to this policy
If what the app does with data changes, this page changes with it, and the date at the top moves. This is the first version, written when the app went into production hosting at Scaleway on 23 August 2026.