Privacy Policy

Who we are

Metricky is built and operated by Grön IT AB, a company registered in Sweden, which is the data controller for any personal data described in this policy. Questions and requests: gronitab@gmail.com.

The offline app: no data collected

On iOS and Android, Metricky works fully offline without an account. In that mode every metric, entry, attachment and preference is stored only on your device. Nothing is transmitted to us — there is no account, no telemetry and no analytics. Data leaves the device only if you explicitly use the export feature, and then it goes where you send it, not to us.

The cloud tier: what we store

If you create an account for multi-device sync, we store:

• Your email address and a password hash — used to sign you in and, rarely, to contact you about your account.
• End-to-end encrypted data. Your metrics, entries, notes and preferences are encrypted on your device before upload. Our servers store ciphertext plus a per-row code (an HMAC) used only to scope rows to your account.
• Operational metadata — row timestamps, row counts and approximate payload sizes, which the sync protocol needs to function.
• Transient server logs including IP addresses, kept briefly for security and debugging, then discarded.

Your encryption passphrase generates a key that never leaves your devices. We cannot read your metric names, entry values, notes or preferences — and because the passphrase is never transmitted, we could not decrypt your data even if compelled to try. The flip side is real: if you lose the passphrase, we cannot recover your data either.

Health and fitness data

Metricky can read health and fitness data from Health Connect on Android and Apple Health on iOS, so that figures you already record elsewhere appear as metrics alongside everything else you track. This is entirely optional: nothing is read unless you turn on an import for a specific metric and grant the permission, and you can revoke it at any time in Health Connect or Apple Health, or by turning the import off in Metricky.

What we read

Metricky requests read access only to the types it can chart, and only for the types you have actually bound to a metric:

• Steps
• Weight (body mass)
• Heart rate
• Resting heart rate
• Sleep
• Active calories burned
• Distance (walking and running)

Metricky never writes to Health Connect or Apple Health, and it does not request write permission. Access is read-only, and only while the app is open — Metricky does not read health data in the background.

How we use it

Imported readings are turned into ordinary Metricky entries on your device and used for exactly one purpose: showing you your own data — charts, streaks, summaries and the correlations between your metrics. All of that analysis runs on your device.

Where it goes

On the offline tier, health data never leaves your device. If you use a cloud account, entries created from health data sync like every other entry: they are end-to-end encrypted on your device before upload, so our servers hold ciphertext we cannot read. We do not receive your health data in a readable form at any point.

What we never do with health data

• We never use health or fitness data for advertising or marketing, and we run no ad networks.
• We never sell, rent or transfer it to data brokers, information resellers or any other third party.
• We never use it to train machine-learning or AI models.
• We never use it for, or make it available for, decisions about credit, lending, insurance, employment or housing.
• We never share it with anyone other than you — and because it is encrypted before it reaches us, we could not.

Retention and deletion

Health-derived entries live on your device for as long as you keep them, and you can delete any entry, or a whole metric and its history, at any time in the app. On the cloud tier the encrypted copies are retained while your account exists and are purged when you delete your account, ageing out of our encrypted backups within 30 days; the section on data retention and deletion below applies to health-derived entries in full. Revoking the Health Connect or Apple Health permission stops any further reading immediately; entries already imported stay in your own data until you delete them.

What we never do

• No advertising, and no ad networks in the app or on this site.
• No third-party analytics or tracking pixels.
• No selling, renting or sharing of your data with anyone.

Cookies

The web app uses a single session cookie to keep you signed in. There are no marketing or analytics cookies, which is why you don't see a cookie banner.

Data retention and deletion

Cloud data is kept for as long as your account exists. If you cancel the cloud tier, a full export is produced first, your account is deleted and the ciphertext on our servers is purged. Devices that were paired keep their local copies and continue working as standalone offline installs. We also keep routine database backups (which contain your data only in its end-to-end encrypted form) for up to 30 days, after which deleted data ages out of them automatically.

Your rights

Under the GDPR (and equivalent laws elsewhere) you have the right to access, correct, export and erase your personal data, and to lodge a complaint with a supervisory authority — in Sweden, the Integritetsskyddsmyndigheten (IMY). Most of these rights are built into the product: export and account deletion are self-service in Settings. For anything else, email gronitab@gmail.com.

Changes to this policy

If this policy changes in a way that matters, we will update this page and the "last updated" date above, and notify cloud-account holders by email before the change takes effect.