Privacy Policy

Effective 14 August 2026 · applies to Nibble for iOS, version 1.0

The short version

Nibble has no accounts, no servers, and no analytics. There is nothing to sign up for.
Your numbers live in Nibble's own storage on your device, and are deleted when you delete the app.
Health data is read-only, limited to two totals, and is never transmitted by Nibble.
Nibble shows no ads, contains no tracking or analytics code, and sells nothing to anyone.

What Nibble stores, and where

Everything you create in Nibble is written to a private container on your device that the app and its widgets share. For each metric that is: the name you typed, its current value, its goal and unit if you set them, a short history of recent values used to draw the sparkline, and your layout and colour choices.

That container is local storage. It is not a copy of something held elsewhere — there is no elsewhere. Nibble has no backend, so there is no account database, no server-side profile, and no export of your metrics leaving your device on Nibble's initiative. Deleting a metric removes it; deleting the app removes all of it.

Health data (Apple Health / HealthKit)

If you add a Steps or Water metric, Nibble asks for permission to read from Apple Health. Specifically and only:

HKQuantityTypeIdentifierStepCount — your step count
HKQuantityTypeIdentifierDietaryWater — your logged water intake

Nibble reads today's total for those types and nothing else. It requests no other health or fitness type, and it reads no history, no workouts, no heart rate, no sleep, no medical records.

The permission is read-only. Nibble requests an empty write scope, so it cannot add, change, or delete anything in Apple Health, and the permission sheet iOS shows you reflects that: it lists a read section only.

Health values are used for one purpose — displaying that metric in the app and on your widgets. They are written to the same on-device container as your other metrics. Nibble does not transmit them anywhere, does not sync them to iCloud, does not use them for advertising or marketing, and does not use them to build a profile of you.

You can withdraw the permission at any time in Settings › Privacy & Security › Health › Nibble. The metric stays, and simply stops updating.

Numbers Nibble fetches from the internet

Some metrics are fed by a web request, and those requests necessarily leave your device:

The Bitcoin and Ethereum presets request a public price from Coinbase (api.coinbase.com). No key, no account, no personal data — the request asks for a public exchange rate.
A custom JSON metric requests the URL you entered, so it contacts whichever service you chose to point it at.

As with any web request, the service you contact can see that a request arrived and the IP address it came from, and its own privacy policy governs what it does with that. Nibble sends no identifier, no account, no device name, and no health data along with these requests — only the plain request for the address you configured. The connection uses an ephemeral session, so no cookies or cached credentials from those services are kept on your device.

If you add no internet-backed metric, Nibble makes no network requests at all.

Share cards

When a metric beats its goal, Nibble can turn it into an image you can post. This only ever happens when you tap share.

The card shows the metric's name, its current value and unit, its goal, and the pet. If the metric is a Health metric, that number appears on the card — a card for a step goal shows your step count. The card deliberately does not include your history, so it carries one day's figure rather than a series of every previous attempt.

Where the card goes is entirely your choice. Nibble draws the image on your device and hands it to the standard iOS share sheet. Nibble does not upload it, does not post it anywhere, and has no account with any service that could receive it. Once you choose a destination — Photos, Messages, a social app — that app's own privacy policy governs what happens next. Nothing is ever shared automatically or in the background.

The daily check-in notification

Nibble can send one reminder a day. It is off until you turn it on in the app (Metrics → the bell icon), which is also the only moment Nibble asks iOS for notification permission — nothing is requested when you first launch the app.

The reminder is scheduled on your device, by iOS. There is no push server, no push token, and no remote notification of any kind: Nibble hands iOS a time of day and a fixed piece of text, and iOS shows it locally. Because of that, no information about you leaves the device to make a reminder happen, and the developer has no way to know whether one was ever delivered.

The text is the same for everyone and contains none of your data — no metric name, no value, no goal, and no progress. It reads:

Check in with your pet
Your pixel pet is on your Home Screen — see how today is going.

That is deliberate. A notification preview can be read off a locked screen by anyone holding your phone, so the reminder says nothing about what you track or how it is going. Nibble also sets no app-icon badge.

You can withdraw it at any time — the in-app toggle, or Settings › Notifications › Nibble. If you turn permission off in iOS Settings, the in-app switch turns itself off to match, so it never claims to be sending reminders that iOS is discarding.

Purchases

Nibble Pro is a one-time In-App Purchase handled entirely by Apple. Apple processes the payment; Nibble never sees or stores your name, card, or billing details. All Nibble learns from Apple is whether the purchase is active on your Apple Account, which is what unlocks the paid layouts.

What Nibble does not do

No user accounts, logins, or profiles.
No analytics, telemetry, or crash-reporting SDK — no third-party code of that kind is in the app at all.
No advertising and no ad network.
No tracking of you across other apps or websites, and no use of the advertising identifier.
No selling, renting, or sharing of your data — there is no collected data to sell.
No server operated by the developer, so no backups, logs, or copies of your metrics exist off your device.

This is why Nibble's App Store privacy label reads Data Not Collected. The label is a description of the app's design, not a promise layered on top of it.

Children

Nibble collects no personal information from anyone, including children. It has no sign-up, no messaging, no user-generated content shown to other people, and no advertising.

Your control over your data

Delete any metric inside the app to remove it and its history.
Revoke Health access in Settings › Privacy & Security › Health › Nibble.
Delete Nibble to remove everything it stored, including its widget data.

There is no data-access or deletion request to file, because the developer holds no copy of your data to access or delete.

Changes to this policy

If Nibble's behaviour changes in a way that affects this policy, the policy is updated here with a new effective date before the change ships. In particular, if any future version were to transmit health data off the device, that would be stated here explicitly and reflected in the App Store privacy label.

Contact

Questions about this policy, or about privacy in Nibble: app.contact.support@gmail.com.