Data safety
This page is the long form of Relo's Google Play Data Safety declaration. The store form allows only a few fixed answers, so here is each one in full, with the reason behind it.
Effective 22 October 2026 ·
app.relo.tracker
No data is shared with third parties
Nothing collected by Relo is passed to anyone else, for any purpose.
No data is used for advertising
There is no ad network, no ad ID, and no advertising in the app.
Data is encrypted in transit
Every request between the app and our server uses HTTPS.
You can request deletion
Delete your account in the app, or email us and we will do it.
Every data type, declared
“Collected” means the data is sent off your device to us. “Shared” means it is passed to a third party. Data that stays in the app's own storage counts as neither, which is why most rows below are no.
| Data type | Collected | Shared | Notes |
|---|---|---|---|
| Name | Optional | No | Account management. Only if you create an account. |
| Email address | Optional | No | Account management, sign-in and password reset. Only if you create an account. |
| Passwords | Optional | No | Stored only as a bcrypt hash, never in readable form. |
| Photos and videos | No | No | Product photos and receipts stay in the app's private storage on your device. |
| Files and documents | No | No | Attachments and backup files stay on your device. |
| App activity and in-app items | No | No | Your products, dates, prices and notes never leave the device. |
| Financial info | No | No | Purchase prices you record are on-device only. Relo takes no payments. |
| Location | No | No | Not requested, not accessed, not approximated. |
| Contacts, calendar, messages, call logs | No | No | No permission is declared for any of these. |
| Device or other IDs | No | No | No advertising ID and no device fingerprint. |
| Crash logs and diagnostics | No | No | Written to the device so you can read and send them yourself. No reporting SDK. |
Security practices
- Encrypted in transit. HTTPS for every request the app makes.
- Passwords hashed. Stored with bcrypt; we cannot read them.
- Tokens in the Keystore. Sign-in tokens live in Android's hardware-backed keystore, not in ordinary app storage.
- Private app storage. The database and attachments sit in the app's private directory, which other apps cannot read.
- Deletion you control. Account deletion is in the app, and uninstalling removes everything local.
One limitation stated plainly: the local database is not separately encrypted with a password of its own, so anyone who can unlock your phone can open Relo. Use a screen lock. An in-app lock is planned.
Why so little is collected
Relo was built offline-first, so the app has nowhere to send your records and no reason to. There is no analytics SDK, no advertising SDK and no third-party crash reporter in the build. That is a design decision, not a promise we have to police: the code that would upload your items does not exist.
Requesting deletion
In the app, open Settings, then Account, then Delete account. That removes your name, email, password hash and tokens from our server; items on your device are untouched. If you cannot reach the app, email info@tinyapps.me from the address on the account and we will complete it within 30 days.
More detail
The privacy policy covers legal bases, retention periods, processors and your rights. The terms of use cover what the app does and does not promise. Anything still unclear, ask us through the contact form.