This policy explains what the weight.it Android app and the mrclaus.io website do with data, why, where it is kept, who else is involved, and how you can delete it. Questions: privacy@mrclaus.io.

The short version

1. Who we are and scope

The app and this website are run by MrClaus, Spain. For the data handled by the website and for any data that reaches us, MrClaus is the controller under the GDPR. Contact: privacy@mrclaus.io.

This policy covers the weight.it app for Android and the mrclaus.io website. We will update it before an iOS version is offered, because the app would handle data differently there.

2. What stays on your device

Your journal entries (date, weight, note and optional photo), your name, profile picture, motivation, starting and target weight, milestones and settings are stored on your device. They leave it only if you use the Google Drive backup (section 4), share a recap (section 5) or transfer them to a new device (below). Photos are saved as files in the app’s own storage. Weights are stored in pounds and shown in the unit you choose.

The app turns off Android’s cloud backup for itself (allowBackup=false), so this data is not included in Google’s Android cloud backup. Android may still move app data when you transfer to a new device, so this is not a promise that it never leaves the device by your own action.

Security: the app keeps this data in its private storage on your device, which other apps cannot read. The app does not add its own encryption, so the data is protected by your device’s screen lock and, where your device supports it, Android’s storage encryption. The “Blur Progress Photos” setting only hides photos on screen. All connections the app makes to Google use HTTPS, and your Drive backup is protected by your Google account’s security; we have no access to it.

3. Google sign-in and profile data

Signing in with Google is optional. When you sign in, the app receives your Google basic profile: display name, email address and profile photo address. It uses the name to fill in your name, and downloads the profile photo from Google to use as your profile picture. It also shows your name, email address and photo in Settings so you can see which account is signed in. The email address is not stored by the app. The photo is also shown directly from Google’s servers in some places in the app. This data is used only for those purposes. It is not sent to us. The profile picture you keep is stored on your device and, if you use the Drive backup, is included in the backup (section 4).

Sign-in is only available in builds that include a Google client ID, which is the case for the Android release.

4. Google Drive backup

The backup is optional. It runs when you start a backup in Settings, or automatically after you change your journal if you switch on Auto-Backup in Settings (off unless you enable it). It uses the Google Drive scope drive.appdata, which gives the app access to a hidden app folder in your own Google Drive and nothing else in your Drive. We cannot see that folder or its contents; the data goes from your device to your Drive.

The backup contains health-related data: every entry’s date, weight, note and photo, plus your name, motivation, starting and target weight, theme and unit settings, photo-blur setting, achieved milestones and profile picture, plus entry IDs, a backup timestamp and the app version. Restore reads the same folder back onto your device.

Each backup is a separate copy that does not change afterwards, kept in the app’s hidden Drive folder. Google Drive keeps your latest backup, plus the newest one from each of the previous 7 days (days counted in UTC), photos included. Older copies are deleted automatically during a later backup and can’t be recovered. Because earlier copies are kept for those days, an entry or photo you delete in the app can still be in an older backup until that backup is deleted. A photo is deleted from Drive only when every backup that used it has been deleted; a photo that no deleted backup used stays until you delete the hidden app data (section 15).

Before a backup replaces one that this device did not make (for example after a fresh install, after Clear All, with another device, or once after an update), the app asks first. If you confirm, the replaced backup is kept for 7 days and then deleted for good. The same applies if you confirm replacing a backup with an empty journal. Backups do not sync between devices: each device keeps its own journal. Restore brings back the latest backup; the app has no screen to pick an older one.

The app has no button to delete the Drive copy. To delete it, see section 15.

5. Sharing a recap

The “Share recap” button writes a short text with your weekly change and total change. Nothing is shared unless you tap it, and you choose which app receives the text. The app does not send it anywhere itself. What the receiving app does with it is governed by that app.

6. Fonts

The app downloads its fonts, Merriweather and Caveat, from Google Fonts when it needs them. Google therefore receives your device’s IP address and the usual technical details of the request. See Google’s Privacy Policy. No journal data is part of this request.

7. Photos

The app picks photos from your gallery only. It does not use the camera. Entry photos are cropped on your device; a copy of each picked photo, including your profile picture, is stored in the app’s own storage.

8. Permissions

The release app’s merged Android manifest requests these permissions:

The app requests no camera, location, contacts, microphone or storage permissions.

9. What we do not use

The app has no analytics, no crash reporting and no advertising, and makes no network requests other than those described in this policy.

10. Google API Services User Data Policy

weight.it’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the features described above (sign-in, profile prefill, and the optional backup and restore). It is not transferred to us or anyone else, not used for advertising, and not read by humans.

11. This website

The site is served by Cloudflare, which, like any network provider, sees visitors’ IP addresses and technical request data. We use no cookies and no analytics, and we keep no logs ourselves. Email sent to an address at @mrclaus.io is forwarded by Cloudflare Email Routing to our inbox. If you write to us, we receive your message and address and use them to answer you.

12. Purposes and legal bases

Under the GDPR:

13. Who else handles data, and transfers outside the EEA

We sell data to no one.

14. How long data is kept

Data on your device stays until you delete it or uninstall the app. Drive backups are deleted automatically as described in section 4 (the latest backup plus the newest one from each of the previous 7 days are kept); a photo stays in Drive until every backup that used it is deleted, and a photo that no deleted backup used stays until you delete the hidden app data. The app has no button to delete the Drive copy; section 15 explains how. We keep no logs of website visits; Cloudflare keeps its own under its policies. Emails to us are kept as long as needed to deal with your request.

15. How to delete your data

16. Your rights

Under the GDPR you may ask for access to, correction or deletion of, restriction of, or a copy of data we hold about you, and object to processing. Write to privacy@mrclaus.io. Because the app keeps its data on your device and in your own Drive, you can already see and delete it yourself. You also have the right to complain to a supervisory authority; in Spain this is the Agencia Española de Protección de Datos (aepd.es).

17. Children

weight.it is intended for people aged 14 and over. It is not directed at children under 14. If we learn that we hold data, such as an email address, from someone under 14, we delete it. Parents or guardians who think this has happened can write to privacy@mrclaus.io. The journal itself stays on the device and in that person’s own Google Drive, where we cannot see or delete it; section 15 explains how to delete it. Signing in with Google follows Google’s own age rules.

18. Changes

We may update this policy, for example before an iOS version is offered. The effective date at the top shows the latest version.

19. Contact

Privacy: privacy@mrclaus.io. Everything else: support@mrclaus.io.