Privacy policy
What the Marie Rosin Health apps collect, why, where it is kept, and how to get rid of it. Written to be read, not to be survived.
Last updated 23 September 2026.
Who is responsible
The data controller is Marie Wellness OÜ, registry code 17603292, registered in Estonia at Tähe tn 129b, 50113 Tartu.
For anything in this document, including a request to see or delete your data, write to apps@marie.ee.
What this covers
One Marie Rosin Health account is shared by all of the apps below, so this one policy covers every one of them: they read and write the same account. Where one app does something the others do not, it says so below.
- Marie Rosin Health The ecosystem app, which brings the others together under the one account.
- 4×4 Interval training, heart-rate recovery and the Cooper test.
- Resonance Breathing Guided breathing and its heart-rate measurements.
- Marie Functional 90 A 90-day functional training programme.
- Restart App Cold exposure and breathing.
When a new app joins, it is added to this list before it is released, together with anything it does that the others do not.
Some of the apps work entirely on your phone and never contact us at all. Apart from visits to this website, described under “This website”, nothing in this policy applies while you are signed out.
What we hold, and why
Your account
Email address, a name if you give one, and your password stored only as a hash we cannot reverse. Needed to have an account at all.
Facts about you that the training depends on
Date of birth, sex at birth, height, and weight. These are not profile decoration: every training zone in the 4×4 app is a percentage of a maximum heart rate derived from your age, and VO₂max estimates use your weight. We ask for a date of birth rather than an age because an age is wrong the day after it is written.
Your training
Sessions and their intervals, heart-rate readings taken from a chest strap during a session, heart-rate recovery figures, Cooper test results and VO₂max estimates, breathing sessions and their measurements, strength training sessions, and diary entries you write yourself.
Where you ran, but only if you turn it on
A session can record its route. Recording is off by default and has to be switched on. Backing that route up to your account is a second, separate switch, also off by default, with its own consent. A heart-rate trace says when you trained, while a route says where you live, which roads you use and what time you are not at home.
With route backup off, routes stay in the app's own storage on the phone and are removed when you uninstall it.
Purchases
Which subscriptions you hold and when they end. The payment itself is handled by Apple or Google; we never see your card, and we receive a receipt rather than a payment.
Consents
What you agreed to, which version of the text you were shown, and when. This record exists so that we can prove we asked, and so that you can see what you said yes to.
What we do not do
- No analytics, of any kind There is no analytics library, no crash reporter and no advertising SDK in any of the apps. This is checkable rather than a promise: none of them appears in any dependency list.
- No tracking and no advertising Nothing about you is used to build a profile for advertising, and nothing is shared with an advertising network.
- Nothing is sold We do not sell, rent or trade personal data, and there is no arrangement under which anyone else may use it for their own purposes.
- No health data in iCloud The apps do not put health information into iCloud or any other consumer cloud backup.
Your phone and our server are different places
Each app keeps its own database on the phone, and that is where a session is written first. Backing it up to your account is a setting you control. With backup off, your training stays on the device and we hold nothing but your account.
Uninstalling an app deletes everything it kept on the phone. It does not delete what is already in your account. That is what the deletion page is for.
Apple Health and Health Connect
If you allow it, the 4×4 app reads finished workouts, and on iPhone VO₂max readings, from Apple Health or Health Connect, so a run recorded by a watch can appear in your history. This is read-only: nothing is ever written back.
On Android the app deliberately does not ask for permission to read health history, so it cannot see anything older than the window it imports.
Maps
The map drawn over a recorded route uses no network at all by default: it is drawn from the points stored on your phone, and works with no signal.
If you switch the background map on, the app fetches map tiles from our map server. That request tells the server roughly which area you are looking at. The route itself is not sent, but the area is, which is why this is a setting rather than the default.
This website
apps.marie.ee sets no cookies, runs no analytics, and loads nothing from anywhere else: its fonts and images are served from its own server.
Like any web server, it keeps an access log: your IP address, the time, the page you asked for and the one you came from, and what your browser says it is. The log is used only to keep the site working and to look into abuse, which is our legitimate interest (Article 6(1)(f) of the GDPR), and it is deleted after 14 days.
The account deletion page sends your email and password straight to our server over an encrypted connection, and keeps nothing in your browser: close the page and the sign-in is gone.
Legal bases
Health and fitness data is a special category under Article 9 of the GDPR, and we process it only on your explicit consent (Article 9(2)(a)), recorded as described above. You can withdraw that consent at any time; withdrawing it does not make what happened before unlawful.
Your account and the provision of the apps rest on the contract between us (Article 6(1)(b)). Purchase records are kept because accounting law requires it (Article 6(1)(c)).
Backing training up to the account, and backing routes up, are each a separate consent and each refusable on its own. Refusing them does not stop the apps working on the phone.
Who else sees it
Our servers are run for us by a hosting provider in Estonia, under a contract that allows them to process data only on our instructions. Account email, such as a password reset, is delivered by a mail provider.
Apple and Google process your purchase and subscription status, under their own privacy policies, and may do so outside the European Economic Area under the safeguards their terms provide.
That is the whole list. Data is otherwise disclosed only if the law requires it of us.
How long we keep it
For as long as you have an account. When you delete your account, the data is removed from the database immediately. There is no waiting period and no retention window.
Encrypted nightly backups are kept for 14 days and then deleted, so a copy can remain in those for up to 14 days after deletion. Records of purchases are kept for as long as accounting law requires, separately from your training data.
Your rights
You can ask for a copy of your data, ask us to correct it, ask us to delete it, ask us to restrict or stop a particular use, and object to processing. You can ask for your data in a portable form. Write to the address at the top of this page and we will answer within one month.
You can delete your account yourself, without asking and without installing anything, at the account deletion page. The apps offer the same thing in their settings.
If you think we have handled your data wrongly, you can complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, www.aki.ee).
Children
These apps are not intended for people under 16, and we do not knowingly hold data about them. The training they prescribe is near-maximal effort and is written for adults.
Research
Some of the work behind these apps involves studies of breathing and heart-rate variability. Taking part in one is always a separate, explicit decision with its own information sheet and its own consent, and nothing you do in the ordinary apps enrols you in anything.
Security
Traffic between the apps and the server is encrypted in transit. Passwords are stored only as hashes. Access tokens are held in the phone's own secure storage. Access to the database is limited to the people who need it to run the service.
Changes
If this policy changes in a way that affects what we do with your data, we will ask again rather than assume the old answer still stands. The date at the top says when it last changed.