Last updated: 17 October 2026
The Dutch version of this text is the source. If the two versions differ in meaning, the Dutch version prevails.
Refinds engages a small number of service providers in order to deliver the service. This page sets out what kind of parties they are, what we use them for, which data they process in doing so, and where that happens.
This page is the only place where this list lives. The privacy statement links here and does not repeat the list, so that two versions can never arise.
Why this page names categories and not trade names. We describe every recipient by its function, the data it processes and the country where that happens — not by its trade name. The GDPR allows this: Article 13(1)(e) speaks of "recipients or categories of recipients". If you want to know which specific party sits behind a category, we will give you that name on request, free of charge, via the contact address in §7.
These are parties that process personal data on our instructions and for our purposes.
| Category of provider | What for | Which data | Where |
|---|---|---|---|
| Our hosting provider | Hosting of our servers, databases and file storage; management of the domain and DNS; the mailbox in which your messages to us arrive (support@, privacy@, info@) | All data held on our servers: listings, accounts, uploads, logs. Plus the content of the email you send us, with your name and email address | EU (contracting party established in Cyprus) |
| Our delivery service for outgoing email | Delivering our outgoing email: sign-in codes, confirmations, notifications to shop owners | Recipient’s email address, subject and content of the message, delivery status | Processing in the EU region (eu-west-1); company established in the United States — transfer on the basis of the EU-U.S. Data Privacy Framework and the European Commission’s standard contractual clauses |
| Our AI service for text and imagery | Automated writing and translation of the descriptions in the guide; assessing uploaded photos before publication | For texts: factual data about a shop or place. For moderation: the uploaded photo itself | United States — transfer on the basis of the European Commission’s standard contractual clauses |
| Our error-monitoring service | Error monitoring of the website, the app API, the data processing and the administrative environment | Error message, page involved, browser type, timestamp. Session replay is off; web addresses are stripped of query parameters and access links before transmission | Storage in the EU; company established in the United States — transfer on the basis of the EU-U.S. Data Privacy Framework and the European Commission’s standard contractual clauses |
| Our geocoding service | Converting addresses into coordinates, so that shops and markets appear on the map | The address of a shop or market (for a sole trader that may also be a home address) | Netherlands |
| Our platform for reading public sources | Reading publicly accessible sources for the data collection | Publicly accessible business data, including shops’ contact details | Czech Republic (EU) |
| Our storage service for the off-server back-up | Storing the daily database back-up off our own server | The full database, encrypted — that service holds no key and cannot read the contents | European Union (Slovenia; storage in Germany) |
| Our post-handling service | Receives and scans the post sent to our postal address | The content of your letter, with your name and address | Netherlands; the service uses sub-processors with technical access outside the EU (United Arab Emirates) — transfer mechanism available on request via §7 |
These are parties that receive data without processing it on our instructions. They decide themselves what to do with it; their own privacy statement applies.
| Recipient | When | What they receive |
|---|---|---|
| Our map-imagery service | As soon as you open a map on the website or in the app | Your IP address and which map tiles your device requests; we pass nothing else on. Where that party has its servers is for it to decide — see its own privacy statement. |
| Apple (Sign in with Apple) | Only if you use that button | Your choice to sign in to Refinds; Apple gives us an identifier and, if you allow it, an email address |
| Google (Sign in with Google) | Only if you use that button | Likewise |
| Apple App Store / Google Play | When downloading and updating the app | Whatever those stores record about their own users; we have no influence over that |
We use no advertising networks, no analytics services with identification and no social media embeds that load by themselves.
For completeness, so that no one has to guess:
| Category of service | What for | Why no personal data goes there |
|---|---|---|
| Our build and distribution service for the app | Building and distributing the app files | Processes our source code and build artefacts, not user data |
| Our availability monitor | Checking whether our services are reachable | Sees only our own addresses and the response to them, no user data |
| Our supplier of bundled public business listings | Supplying public business listings for the data collection (see privacy statement §7.3) | We send it only a category and an area, no personal data |
These entries appear on the list because a decision is still outstanding. We include them rather than leave them out, so that the list can hold no surprises.
| Subject | Status |
|---|---|
| Final party for monitoring and log collection — the error-monitoring service and the availability monitor are already running; the formal choice and account ownership still need to be recorded, and a separate log service is under consideration |
| Party | What it would be for | Status |
|---|---|---|
| Google (Business Profile) | Letting shop owners link their business profile to their listing | Parked until after the public launch; the integration is switched off and no data whatsoever is exchanged. If it is switched on, it goes on this list first, with a signed agreement. |
| Meta (Facebook / Instagram) | The same for a Facebook page | Likewise |
| A specialised translation service | Translating texts supplied by shop owners themselves | Decided on 30 August 2026 not to put it into use. We translate with the existing chain. No data whatsoever goes to it: the integration has been taken out of the software and the access key has been removed from our server. If it returns later, it goes on this list first, with a signed agreement. |
If we engage a new provider, we add its category here before it is put into use and update the date at the top. If something material changes for account holders, we tell them.