Privacy Policy — Make Yourself

Last updated: 1 October 2026

This policy describes what the Make Yourself app collects, why, where it goes, and how to get rid of it. It is written to match what the code actually does. If you find a difference between this page and the app's behaviour, the difference is a bug — please report it to the address at the bottom.

Who is responsible for your data: Danylo Kozak, the individual developer who makes and publishes Make Yourself (the "data controller").

Contact: [email protected]


1. The short version


2. What the app stores on your phone

All of this stays on the device unless you sign in and turn backup on:

3. What is sent off the device, and when

There are three separate things here, and they are worth keeping apart.

3.1 Diagnostics - for everyone, with or without an account

So that faults can be found and fixed, the app sends two kinds of technical data to Google Firebase:

Neither contains your tasks, notes, recordings, money figures, health data or the list of apps you block. This data is used only to check that the app works properly and to decide what to fix or improve. It is not used for advertising or to build a profile of you, it is not sold, and the app does not request or use the Android advertising ID.

The app also uses Firebase App Check with Google Play Integrity and, during sign-in, Google reCAPTCHA. Both exist to confirm that requests come from the genuine app and a real person, and to keep abuse out.

3.2 Your content - only after you sign in, and only to your own account

If you sign in with email or Google, the app uses Google Firebase (Authentication, Firestore, Storage) to back your data up and, if you use the Windows app too, to keep your devices in step. Your data is stored under a path tied to your account ID and is protected by server-side rules that permit access only to the signed-in owner.

What Category Why
Email address, account ID Personal info To sign you in and identify your data
Tasks, streaks, daily completions, progress App activity Backup, restore and sync between your devices
Focus session history and usage statistics App activity Backup, restore and sync between your devices
Chat entries, Ideas pages, Books, saved quotes User-generated content Backup, restore and sync between your devices
Photos, videos and voice recordings you make in the app, including Evolve progress photos Photos, videos, audio Backup, restore and sync between your devices
Sweet Money transactions, budgets and balances Financial info (self-entered) Backup, restore and sync between your devices
Sport log: training sessions, meals, and imported workouts and sleep Health and fitness Backup, restore and sync between your devices
The list of apps you have chosen to block App activity Backup, restore and sync between your devices

The Sweet Money figures are numbers you type in. The app has no access to any bank, card or payment account, and never asks for one.

3.3 Optional features that talk to another service

Each of these does nothing until you use it.

We do not sell your data, and we share it with nobody except the service providers named in this policy, who process it on our behalf to run the app.

4. Permissions, and what each one is genuinely for

4a. Health Connect and Strava

Both are off until you connect them on Settings → Connections, and both are read-only: the app never writes, edits or deletes anything in Health Connect or on Strava.

Health Connect (Android's health data store, which is where Garmin, Samsung Health, Fitbit and similar apps put their data). With your permission the app reads: exercise sessions, distance, calories burned (total and active), heart rate and resting heart rate, heart rate variability, sleep, steps, floors climbed, elevation gained, speed, cadence, oxygen saturation, VO2 max, weight and body fat. Each type is asked for separately and you can grant only the ones you want; the history permission is used only so a first import can reach further back than 30 days.

What it is used for: to show your own workouts, sleep and daily figures on the Sport page, next to what you log by hand, and to count imported workouts in your weekly training stats and calorie budget. Nothing else.

Strava. If you connect Strava, the app signs in to Strava with your consent (read access to your activities only) and imports your activities into the same Sport log. The Strava access token is stored only on your phone. Disconnecting removes it.

Where that data goes. Imported workouts and sleep are stored on your phone. Daily figures (steps, heart rate, oxygen saturation and the like) never leave the phone. If you sign in, the Sport log — including imported workouts and sleep — is backed up to your own private Firebase area with the rest of your data, and deleting your account deletes it. Health data is never sold, shared with third parties, used for advertising, or used to build profiles, and it is not used to train any model.

The use of information received from Health Connect will adhere to the Health Connect Permissions policy, including the Limited Use requirements. You can revoke the app's access at any time in Android's Health Connect settings, or disconnect a source on Settings → Connections.

5. Payments

Subscriptions are handled entirely by Google Play. The app never sees, receives or stores your card details, and Google does not share them with us. We receive only the fact that a subscription is active. Prices, renewals, cancellation and refunds are described in the Terms of Service.

6. How to delete your data

Uninstalling without a backup — read this before you delete the app

Your data lives on your phone. Uninstalling the app deletes it from the phone, and the app has no way to bring back anything that was not backed up first. The app does not warn you at the moment you uninstall it — Android does not tell an app it is being removed — so this is the warning.

Android's own device backup (Google One) may independently restore some app settings on a new install. That is a feature of your phone, not of this app, and nothing here relies on it.

We cannot recover data that was never backed up, and we do not accept responsibility for data lost by uninstalling the app or clearing its data without backing it up first.

6a. How long data is kept

6b. Your rights

If you are in the European Economic Area, the United Kingdom or another place with similar law, you have the right to see the data held about you, to have it corrected or deleted, to receive a copy of it, to object to its use, and to withdraw a consent you gave (for example by disconnecting Health Connect or Strava, or turning a permission off). You can do most of this yourself in the app; for anything else write to [email protected]. You also have the right to complain to your data protection authority.

The legal grounds are: providing the service you asked for (your account, backup and sync, paid features), your consent (permissions, Health Connect, Strava), and our legitimate interest in keeping the app working and secure (diagnostics and abuse protection).

7. Children

The app is not intended for children under 13 and we do not knowingly collect their data.

8. Security, and where your data is kept

Data in transit is encrypted (HTTPS/TLS); the app refuses unencrypted connections outright. Data at rest is held on Google Firebase infrastructure. Access is restricted by server-side rules that allow each account to reach only its own data. The app-lock password, if you set one, is stored only as a salted, iterated hash, never in readable form, and never leaves your device.

Where. Backups are stored on Google Cloud servers in the United States. If you are in the United Kingdom, the European Economic Area, or another country with similar rules, this means your data is transferred outside your region. That transfer relies on Google's standard contractual clauses and its certification under the EU–US Data Privacy Framework. If you would rather your content did not leave your own region, do not sign in - the app is fully usable without an account, and without one the only thing sent is the anonymous diagnostics described in section 3.1.

9. Changes

If this policy changes, the date at the top changes with it, and the current version is always the one published at this address.