Privacy statement
What our apps do with your data, and what they don’t. Short, because there is little to tell: our apps keep nothing of yours on our servers. Three features are the exception, and all three are named below.
Who is responsible
The controller within the meaning of the GDPR is:
- Company
- Resa Health B.V.
- Address
- Herengracht 320
1016 CE Amsterdam
The Netherlands - For privacy questions
- support@resa.health
We have not appointed a data protection officer; we are too small and process too little for that to be required. Your questions reach us directly.
In the apps, everything stays on your device
Whatever you enter into a Resa app, or let it measure, is stored on your iPhone and processed on your iPhone. There is no account and no sign-in. Apart from the three exceptions below, no Resa server holds a copy of your data. If you back up your device, that backup goes encrypted to your own iCloud, that is Apple, not us, and we cannot reach it.
Apart from the three exceptions below, we receive no health data, no locations and no notes. If you delete an app, what was in it goes with the app, except what the app wrote to Apple Health, which you manage in Apple’s Health app.
What Apple looks up itself does not pass through us either. For an outdoor workout, Resa Steps fetches the weather at that moment from Apple (WeatherKit), using the place where you started. Resa Pain fetches the air pressure the same way, and Resa Sleep the weather and the name of the place where you slept. Maps come from Apple Maps. That goes straight from your iPhone to Apple; we do not see it.
A few other services see only what they need. If you scan a barcode or search for a product in Resa Food or Resa Vitamin, that code or search term goes to Open Food Facts, an open product database. The music in Resa Relax comes from our own server, which receives only the request for a track, without an account. And Resa Food keeps your recipes, weekly plan and shopping list in your own iCloud, so that they are on your other devices too; we cannot access that.
Apple Health and health data
Health data is a special category of personal data under Article 9 GDPR. Our health apps read and write it through Apple Health, and only when you grant permission per category in iOS. You can withdraw that permission at any time under Settings › Privacy & Security › Health. Because the processing stays on your own device and under your control, we never see this data.
AI in Resa Food is the first exception
Resa Food can have a photo or a description of your meal recognised by a language model, and such a model does not run on an iPhone. The feature is off by default, and the app explains what happens before you switch it on. If you switch it on, this is what happens:
The app sends the photos (at most three) or your description to our own server at Cloudflare. With a description, the names and portions of your own products go along too, so that the model recognises them. Our server passes it on to the Claude API of Anthropic PBC in the United States, and the answer comes back into the app. We do not store the photo or the text. Under its terms, Anthropic does not use them to train models and keeps them for at most 30 days. No name, email address or device identifier is sent along.
Because health data may be involved, the legal basis is your explicit consent (Article 9(2)(a) GDPR), which you give by switching the feature on. You withdraw it by switching the toggle in Food’s settings off again. The transfer to the United States is covered by the European Commission’s standard contractual clauses. If another app starts using AI too, it will be described here before that feature comes out.
Together in Resa Steps is the second exception
In Resa Steps you can share your steps with friends. If you do, something really does leave your device: your display name, your colour and your daily step total. They are stored on our own server, at Cloudflare, in a database in the EU. The server shows them only to the people you connect with yourself: your friends and the members of a group or challenge you are in, including anyone who joins later with the code. Open groups can be found by name, country, language and topic; people themselves cannot be searched for. If you take part in the monthly challenge, the levels or an open group, other participants see your nickname, your colour, your steps per day and your level, and your country if you switch it on. Never your real name. For that, taking part puts more on the server: your nickname, your country (only if you switch it on), per day whether you reached your goal (yes or no, not the goal itself), a profile photo if you choose one, and walks you share yourself (the line with pace and elevation, without the start and the end). Only your friends and the members of your private groups see your profile photo; a shared walk is seen by your friends and the members of your groups. If you step out, your profile photo and your walks are gone. As the operator of the app we can look into the database, for example to handle a report, but we use it for nothing else: no advertising, no analytics, nothing passed on.
There is no sign-in and no password. The first time you create or accept an invitation, the app makes a long random key that stays in your iCloud Keychain. Our server keeps only a hash of it, a form that cannot be turned back. So you are not identified by a name, an email address or a phone number. You choose the display name yourself, and as far as we are concerned it may be a first name or a nickname. The server also holds who is connected with whom, the groups and challenges you are in (name, members and, for a challenge, the goal and the days; for a challenge whose goal is based on your usual number of steps, that number too), and your device’s push address with the Together notifications you want, so that we can notify you through Apple when someone nudges you or accepts your invitation.
As long as you are connected to no one, not a single step leaves your device. The app only sends your daily totals once you have at least one friend, group or challenge with others, and at most the last 40 days, so that a monthly ranking adds up. Individual measurements, routes, workouts, heart rate, energy, sleep and the rest of your data from Apple Health never go along, only the number of steps per day. The server refuses anything sent alongside it.
If you step out again (your last friend removed, your last group or challenge left), the app itself deletes everything of yours on the server: your daily totals, your name and colour, your connections and your blocks. If you leave a group while you still have other friends, groups or challenges, your daily totals stay: they only go once you leave your last connection too. You do not need to email us for that. If there is no network at that moment, the app tries again later. On top of that, the server cleans up every night: daily totals older than 13 months are removed, and if you do not open Resa Steps for 13 months, everything of yours goes. One gap we would rather name ourselves: if you request an invitation link and then never add anyone, your display name and colour stay on the server until 13 months after you last opened the app, because there is no moment at which the app notices you stopped. No steps are stored with them. We will remove them sooner on request via support@resa.health.
If you join a challenge, your name stays in it until a week after it ends. If you nudge a friend, a signal goes onto the server (from whom, to whom and which day), so that they get a notification; it is gone again after about a week. If you report someone, the reason and the person you report go onto it, so that we can look at it; we keep a report for at most 13 months. If you block someone, that is stored on the server too. They cannot add you again and you no longer see each other’s steps, except in a challenge you are both in: there the other person still counts, without your name. If you do not want that, leave the challenge. And if someone enters a code that does not exist, the server keeps a hash of the IP address for at most a day, so that nobody can keep guessing codes.
Earlier versions of Resa Steps kept Together in a database at Apple (iCloud). When the app switches to our server, it sends along your iCloud user identifier and those of your friends there; the server keeps only hashes of them, to find your friends, groups and challenges again. As long as not everyone has switched, the app also still puts your daily totals in that iCloud database, so that friends with an older version keep seeing you. Once everyone has switched, that stops and we clean up the iCloud database.
Together is off until you switch it on yourself, and you switch it off by leaving your friends, groups and challenges. The legal basis is your own decision to take part: you give consent for it in the app, and you can withdraw it by stepping out (Article 6(1)(a) and, in so far as a daily step total is health data, Article 9(2)(a) GDPR).
Sharing live in Resa Steps is the third exception
During an outdoor workout you can create a link and send it. Whoever opens it sees, in the browser and without an account, where you are now, your route so far, distance, time, pace or speed, elevation, your battery and whether you have paused. Photos you take along the way with the camera button in the app go along. Your name, your steps and your heart rate do not.
That data goes to our own server, which runs at Cloudflare. The link is a long random code: only people who get it from you can follow along. With “Hide start and end”, the first and last 300 metres stay hidden, photos included, and you can also remove a photo from your followers afterwards. The viewing page loads the map from OpenFreeMap and a map library from unpkg.com; they see the IP address of whoever is watching and which part of the map is loaded.
When you stop the workout, your position is gone at once and the rest can be seen for one more hour as finished. At the latest 24 hours after the start nothing can be seen any more, and it is deleted at the server’s next clean-up. If you make no link, nothing goes to our server. The legal basis is your own decision to share, article 6(1)(a) GDPR; you withdraw it by stopping sharing.
Subscriptions and payments
At the moment we sell nothing in the apps. When a subscription arrives, payment runs entirely through the App Store: Apple is the seller and processes your payment details, and you cancel with Apple, in your Apple account. What we will then see of your subscription, and which service helps us with it, will be set out here before the subscription is available.
This website
resa.health sets no cookies. On resasteps.com one cookie remembers the language you choose yourself, for a year; nothing more. Neither site has a third-party analytics tool, ad network or tracker. The fonts are on our own server. We do count, with a small script from our own helpdesk (support.resa.health, at Cloudflare), how often a page is viewed, which links on it are clicked, how far the page is read and how long it stays open. Per day and hour we count the country, the kind of device (iPhone, Android or computer) and where you came from: the previous site or the campaign code in the link. We do not keep your IP address, there is no cookie, and nothing links two visits together. So we cannot see who you are or what one person looked at. Only the contact form loads something from outside: a check by Cloudflare (Turnstile) that keeps out spam and sees your IP address and details about your browser to do so. Your theme and language choice are stored in your own browser only.
The site is hosted by Cloudflare, which processes your IP address, the address requested, the time and the browser type on every visit in order to deliver and secure the site. Legal basis: our legitimate interest in a working, secure site (Article 6(1)(f) GDPR).
If you send the contact form, your name, email address and message arrive as a request in our own helpdesk at support.resa.health, which runs on Cloudflare with the data stored in the EU; our reply goes out through Google Workspace. We use those details only to reply, no newsletter, nothing passed on. We delete a closed request after one year, or sooner if you ask. To keep out abuse, the helpdesk counts submissions per IP address for one hour, and keeps an untraceable code of your email address for one day. Legal basis: your request itself, and our interest in being able to answer it. Cloudflare and Google are US providers; that transfer is covered by the European Commission’s standard contractual clauses. If you’d rather email us directly at hello@resa.health, your message ends up in the same place.
On resasteps.com and in our help centre at support.resa.health you can also ask a question in the chat. There, Robin, our AI assistant, answers first, and it says so. What you type goes to our own helpdesk (at Cloudflare, data in the EU). To write an answer, the helpdesk passes your question, the conversation so far and the matching articles from our help centre to the Claude API of Anthropic PBC in the United States. Under its terms, Anthropic does not use them to train models and keeps them for at most 30 days. Robin does not answer questions about your health, so please don’t put anything about it in the chat. A conversation Robin handles is deleted after 30 days. Questions he found no answer to are kept for 90 days, with nothing that can be traced back to you, so we can add to the help centre; a question with an email address or a long number in it is not kept. If you ask for someone on our team, the conversation becomes a request in the helpdesk, just like the contact form, and the same period applies. We only get your email address if you leave it yourself. The chat sets no cookie: your browser remembers a random key for 24 hours so you can continue the conversation, and we keep only an untraceable code of it. To keep out abuse, the helpdesk counts messages per IP address for one hour, without storing that address. Legal basis: your question itself, and our interest in being able to answer it. The transfer to the United States is covered by the European Commission’s standard contractual clauses.
How long we keep things
From most apps we receive nothing, so we keep nothing either. For Together in Resa Steps the periods from that section apply: daily totals for at most 13 months, a report for at most 13 months, everything gone as soon as you step out. What you share live can no longer be seen 24 hours after the start at the latest, and is deleted after that. We do not store a photo or description sent for recognition in Resa Food. Messages through the contact form or by email we keep while the matter is open and delete one year after it is closed, or sooner if you ask. A chat conversation with only Robin is deleted after 30 days, a question without an answer after 90 days; if a conversation becomes a request to us, the contact form’s period applies. Of the website we keep only the counted numbers per day, with nothing that can be traced back to you. Apple keeps the invoices; we keep our own books for seven years, as Dutch tax law requires.
Your rights
You have the right of access, rectification, erasure and restriction, the right to data portability, the right to object, and the right to withdraw a consent you gave. Email us at support@resa.health and you will hear from us within a month. For whatever is in the app you do not need us: it is on your own device and you delete it there yourself. What you put on our server with Together, you delete yourself by stepping out. If you want to know what we hold about you, or want it deleted without the app, email us.
If you are unhappy with how we handle your data, you can complain to a supervisory authority. Ours is the Dutch Autoriteit Persoonsgegevens, but you may also go to the authority of your own country or place of residence.
Children
Our apps are not aimed at children. Together and live sharing in Resa Steps and the recognition in Resa Food rely on your consent; if you are under sixteen, you may only switch them on with the consent of a parent or guardian.
Changes
If something material changes (a new processor, a new feature that sends data), we update this statement and mention it in the app. This version is dated 22 November 2026.