Nanbit Privacy Policy

What Nanbit stores on your phone

All of this lives in a database inside the app's own storage, which only Nanbit can read:

• Habits — the name, icon, color, schedule and daily goal you set, and its reminders: up to three times a day, and whether its nudge is on and at what time.
• Completions — which habit you marked done, on which day, and how many times.
• Settings — your display name, appearance choices (light or dark, and the app's color), the app icon you chose and whether Match my color is on, which day your week starts on, your reminder preferences, and some bookkeeping such as whether you have finished the introduction. The display name is whatever you type when the introduction asks your name, or later on the You tab. It is shown in two places, Today's greeting and the You tab. You can skip it.
• A summary cache — daily totals worked out from the above, kept so the calendars and totals are fast. It contains nothing new.
• Records you have deleted. When you clear a day, Nanbit marks that record as deleted and hides it everywhere in the app, but the row stays in the database file. When you delete a habit, it comes off Today and the widgets and its past days stay in History and Progress, so the habit and its completions stay in the database file too. A cleared day is never sent anywhere. A deleted habit and its past days go into the account backup if you sign in (section 6), and a backup your phone makes copies the database whole, deleted records included. Reset all data removes them along with everything else.

A copy for the widgets. Nanbit also keeps a small copy for its widgets, even if you never add one. It is outside the database, in storage that only Nanbit and its widgets can read. For the free Today widget it says which habits are due and which are done, today and for the next week, as marks and totals, with how far each habit is toward its goal, without the habits' names. With Nanbit Pro it also holds, for the Pro widgets, each habit's name, color and icon, its count and its streaks, its longest streak and which of the last two weeks' days it was done on, how much of each day of this week and of this month so far was done and which days were perfect, the app's color, and the identifiers of each day's reminders, for each habit and for the daily reminder, which Nanbit makes from a habit's internal identifier and the date, so that a tick on a widget can take them back. Once the store has told Nanbit that you do not have Nanbit Pro, the Pro widgets' copy holds only the Nanbit Pro face and nothing of your habits. Until the store has said so, a copy made while you had Nanbit Pro keeps what it last held. When you tick a habit on a widget, the widget writes a small note of it in the same storage (which habit, the day, the count and the time), which Nanbit reads when it next opens and then removes. The habit you choose for a one-habit widget is one of that widget's settings, which your iPhone keeps with the widget. Reset all data replaces the copy with one that holds no habits, and removes any tick note waiting there. If that replacement fails, the widgets can go on showing the last week they were given until Nanbit next updates them.

Deleting Nanbit deletes all of this from the phone, the widgets' copy included. It does not reach a backup the phone has already made — see section 4.

What leaves your phone

Nanbit itself sends three things, and a fourth only if you sign in: the backup, in section 6. Two more leave your phone without Nanbit sending them: its own backup, and an email you choose to send us.

1. Subscriptions, and the app knowing whether you have one

Nanbit uses RevenueCat to tell whether a subscription is active. Whether it contacts RevenueCat at all is settled when a version of the app is built: a version configured to sell subscriptions contacts it, and a version that is not does not contact it at all — not at launch, not when you open the subscription screen, not at any other time.

• When you open Nanbit, and when you return to it, the app asks RevenueCat what this installation is entitled to. This happens whether or not you have ever subscribed, and whether or not you have ever opened the subscription screen. What is sent is a random identifier RevenueCat generates for this installation of the app, the identifier Apple gives this phone for apps from Nanbit's developer, and ordinary technical details such as the app and operating-system version, the phone model, your preferred languages and your App Store country — and, as with any internet request, your device's IP address. Nothing about your habits is ever included. It cannot be: the app never gives RevenueCat any of your data.
• If you subscribe, Apple handles the purchase and the payment, through the App Store. Buying never gives Nanbit your card details, your Apple Account, your name or your email address. Apple's handling of your data is covered by Apple's Privacy Policy.
• RevenueCat, acting on our behalf, checks the purchase with Apple and tells the app whether the subscription is active. What is processed is your purchase history — which product was bought, when, and whether it is still active or in a trial — tied to those same identifiers. It is not your Apple Account, and it is not linked to your name or email. RevenueCat's handling of it is covered by RevenueCat's Privacy Policy.

This is used for two things: unlocking paid features and restoring your purchase on a new device, and aggregate subscription figures such as how many people subscribed in a month. It is not used for advertising, and it is not used to track you across other apps or websites.

2. Recovering from a crash

If Nanbit stops unexpectedly while it is starting up — from the moment it opens until a few seconds after its first screen appears — it can ask Expo's update service for a corrected version of its own code before it closes. It does not check at any other time: not on a normal launch, not while the app is running, and not after a crash later on.

That request carries the platform, the app version, a random identifier for this installation, and the error message: what went wrong in Nanbit's code and, if it went wrong while a screen was being drawn, which parts of Nanbit's code were drawing it, cut off after about a thousand characters. It is not a report about you or your habits — the messages Nanbit's code writes never include a habit, a day you ticked or a setting — and there is no crash-reporting service or dashboard behind it. But it is error text leaving the phone, and we would rather say so than describe the request as carrying less than it does. Expo's handling of it is covered by Expo's Privacy Policy.

The random identifier here is generated by the app. It is not your Apple Account, and not an advertising identifier.

3. Links you tap

The support, privacy and terms links open your browser at an ordinary web address. Nothing about you or your habits is attached; your browser behaves as it always does.

4. Your phone's own backup, which Nanbit does not send

If your iPhone backs itself up with iCloud Backup, that backup can contain Nanbit's database: your habits, completions and settings, and the deleted records described above. It may also contain the widgets' copy; whether iCloud Backup includes it has not been checked, so this policy assumes it can. Nanbit does not send any of it and cannot read it. It goes to your own Apple Account under your iPhone's backup settings, and Apple's privacy policy covers it rather than this one.

What is known: Apple documents that iCloud Backup includes the data of apps you have downloaded, and nothing in Nanbit keeps its database out of it. We have not yet watched a restore bring Nanbit's habits back.

So deleting Nanbit clears it from the phone, and Reset all data clears the database inside it and replaces the widgets' copy — but neither reaches a backup the phone has already made. What happens to that backup is up to your phone's backup settings, not to Nanbit.

5. An email you choose to send us, which Nanbit does not send

Report a bug and Request a feature let you write to us from inside Nanbit. When you tap Submit, Nanbit opens an email to us in Apple's Mail, filled in with what you wrote, or, if Mail has no account set up, in the mail app your phone opens for email links. If neither can take it (no mail app opens, Mail cannot send it, or it is too long to hand to another mail app), it shows our address with buttons to copy it and your message. Nanbit does not send the email. You see all of it in your mail app, you can change it, and it goes only if you send it.

A bug report adds three lines under what you wrote: the Nanbit version and build, your phone's model, and its system version. It adds nothing about your habits, your name or your purchases. A feature request adds nothing.

If you send it, it reaches us like any other email: from your email address, with whatever name your mail app sends, carried by your mail provider under its own privacy policy. It is kept in our inbox, which is Gmail, and read to answer you and to fix what you reported. The rights and the contact details below cover it as they cover purchase records.

6. Your account and its backup, if you sign in

This happens only if you sign in. Signing in is optional and free. Nothing in Nanbit needs an account, and buying or restoring a subscription never needs one. If you never sign in, nothing in this section happens.

Signing in. You can sign in with Apple or with Google. Apple asks you whether to share your name and your email address; if you choose Hide My Email, Apple gives Nanbit a random address that forwards to yours. Google shares your name, your email address and your profile picture's address. The one you choose then gives Nanbit a sign-in token, and Nanbit sends that token to Supabase, which creates your account. What Apple and Google each do with a sign-in is covered by Apple's Privacy Policy and Google's Privacy Policy.

What your account holds:

• The email address Apple or Google gave Nanbit, and the name and picture address they shared, if they did.
• The identifier Apple or Google gives Nanbit for you. It is not your Apple Account or your Google password.
• The backup: your habits, deleted ones included with their past days, your completions, and your settings, including your display name, plus the time it was saved. It does not include days you cleared, or the summary cache.
• A record of each sign-in: when it happened, the IP address it came from, and what kind of device and app made it.

When it is sent. While you are signed in, Nanbit saves the backup a couple of seconds after you change something, and again when you leave the app. If nothing has changed, nothing is sent. When you sign in, Nanbit fetches the backup your account already has. While Nanbit is open it keeps you signed in by renewing its sign-in with the server from time to time, and when you open it, your iPhone asks Apple whether you still allow Nanbit to use Sign in with Apple.

Where it goes, and how. Everything travels over an encrypted connection. It is kept by Supabase (Supabase Pte. Ltd.), which runs Nanbit's server, on servers in Singapore. The backup is stored as Nanbit writes it. It is not encrypted in a way that stops Supabase or Nanbit's developer from reading it. Supabase handles all of it for Nanbit under its data processing agreement.

Supabase's logs. Supabase keeps logs of the requests Nanbit makes to its server. They include your IP address, the rough location it points to, such as your city, what kind of device and app made the request, and, when you sign in, your email address. Supabase says it keeps these logs for up to 7 days, so anything in them that deleting your account cannot reach is gone on its own within that time.

Two other things are Supabase's, and it does not say how long it keeps them. It makes daily backup copies of Nanbit's database, so a deleted account can stay in those copies for a while. And it keeps records of connections to its own systems, for security.

More than one phone. You can be signed in on more than one phone. If another phone has backed up since this one did, Nanbit stops backing up this one and asks which copy to keep, so neither replaces the other without you choosing.

Signing out backs up one last time, then takes your habits off the phone, along with its reminders and the widgets' copy. They stay in your account, and signing in again brings them back. If the last backup cannot be made, Nanbit tells you before anything is removed.

Deleting your account is at You → the card under your name → Delete account. It needs an internet connection. First Nanbit asks Apple or Google to stop Nanbit's access to your account: with Apple, Apple's sheet appears once more so Nanbit's server can tell Apple to revoke it. Then it deletes your account, the backup and the sign-in records from Supabase, and then takes everything off the phone. It cannot be undone. If Nanbit cannot reach Supabase, nothing is deleted and nothing changes on the phone. If Apple or Google does not confirm, the account is still deleted and Nanbit shows you how to remove it from your Apple or Google settings yourself. Deleting cannot reach a backup your phone made earlier (section 4), or Supabase's logs, backup copies and security records, described above. You can also ask us to delete your account: write to the address under Contact, from the email address the account uses.

Moving to a new iPhone

If you signed in to back up, sign in the same way on the new phone and choose Restore: your habits come back from the backup (section 6).

Set up the new iPhone from your old one, or from its iCloud backup, and your habits come along with your other apps' data. Apple's backup includes the data of apps you have downloaded, and Nanbit keeps nothing out of it or out of a direct transfer. We have not yet watched this happen with Nanbit, so check your habits on the new phone before you erase the old one.

What Nanbit does not do

• No analytics about how you use the app. Nothing measures which screens you open, which habits you keep, or how often you come back. The only aggregate figures that exist anywhere are RevenueCat's subscription counts, described above.
• No advertising, and no advertising identifiers.
• No tracking, as Apple defines it: nothing about you is linked to data from other companies' apps or websites, for any purpose.
• No crash-reporting service. The one exception is the update request described in section 2, which carries the error's text.
• No account unless you choose one. Nanbit asks for a name to say hello with, and you can skip it; signing in is optional (section 6).
• No selling, renting or sharing of personal data.
• No location, contacts, photos, microphone, camera or health data. Nanbit never asks for them because it never uses them.

Notifications

Reminders are scheduled by your phone, locally, from the habits already on your device. There is no push server and no push token: nothing about a reminder leaves the phone, and Nanbit cannot send you anything but the reminders you set and, if you start a free trial of Nanbit Pro, one reminder before it ends (below). With Nanbit Pro a habit can have up to three reminder times and a nudge, one more reminder that comes only if the habit is still not done at its time. Because a reminder names the habit it is for, a habit's name can appear on your lock screen — that is your phone displaying it, not Nanbit sending it anywhere. A Nanbit Pro Lock Screen widget can show the names of habits still to do in the same way. You can turn notifications off at any time in the app or in your phone's settings.

The reminder before a free trial ends. If you start a free trial of Nanbit Pro, Nanbit schedules one notification on your phone for two days before the trial ends, at your daily reminder's time, or at 9 in the morning if that is off. It is titled "Free trial ends in 2 days" and says your free week (or free trial, if it is not seven days long) of Nanbit Pro ends in 2 days, and that you can keep it or cancel from You → Manage subscription. There is none for a trial of two days or less, and none unless the store says the trial will go on into a subscription: once it says it will not, as after you cancel, Nanbit takes the reminder back the next time it opens and hears from the store. Like every reminder, it is scheduled on the phone and nothing about it leaves it.

Your choices and controls

• See what Nanbit holds — your habits, completions and settings are all visible in the app. If you sign in, the backup is a copy of the same things (section 6).
• Sign out, or delete your account — at You → the card under your name. Both take your habits off the phone; deleting the account also deletes the backup (section 6).
• Hide individual records — clearing a day hides that record everywhere in the app. Deleting a habit takes it off Today and the widgets and stops its reminders, and keeps its past days in History and Progress. As described above, the underlying rows remain in the database file on your phone until you reset or remove the app.
• Delete everything on the phone — You → About Nanbit → Reset all data erases the database, deleted records included, and empties the widgets' copy and any tick note waiting in it. It leaves behind a little of Nanbit's own diagnostic bookkeeping, and it does not withdraw the notification permission you gave your phone, so it stops just short of a fresh install. Removing the app clears more. Neither reaches a backup your phone has already made (section 4).
• Manage or cancel a subscription — open the Settings app, tap your name, then tap Subscriptions. Canceling never deletes anything you have tracked.
• Ask us to delete purchase records — the subscription records held by RevenueCat are keyed to the identifiers described in section 1. If you want them erased, write to delorinodenver@gmail.com and we will action it. You may need to tell us roughly when and what you purchased, since we have no other way to find you.

How to reach us about your data

Write to delorinodenver@gmail.com. That address reaches Denver Delorino, who makes Nanbit, and it is the only route — there is no support desk and no ticketing system behind it.

If you have never signed in, nothing of your habits is held anywhere we can look. If you have, your account and its backup are on Nanbit's server, and you can delete them yourself in the app (section 6), or ask us to: tell us the email address your account uses. Otherwise the records we can look for are purchase records, and any email you have sent us: tell us roughly what you bought and when, or the address you wrote from. A reply normally takes a few days.

If you are in the UK or the EU, you have rights of access, correction, erasure, restriction, objection and portability over personal data. They apply to your account and its backup if you have one, the purchase records described above, and any email you have sent us. Your habits are on your phone, where you can see, change and delete them yourself. For anything else, write to us.

How long data is kept

Data on your phone is kept until you delete it, reset, or remove the app; a copy in your phone's own backup is kept under your backup settings (section 4). Records you delete inside the app stay in the database file until you reset or remove the app: a cleared day is hidden at once, and a deleted habit's past days stay visible in History and Progress.

An account and its backup are kept until you delete the account, or until we delete it at your request. Supabase's logs and backup copies can outlast it, as section 6 describes.

Purchase records are kept by Apple and by RevenueCat, for as long as needed to support restores, refunds and financial record-keeping.

An email you send us, a bug report, an idea or anything else, is kept in our inbox until we delete it, and you can ask us to.

Children

Nanbit is not directed at children under 13. It never asks for an age. It asks for a name to say hello with, which can be skipped. Without signing in, the only information it sends off the phone is the identifiers and subscription status described in section 1 and — after a crash while it is starting up — the text of the error. Signing in, which is optional, shares an email address and a name with Nanbit's server and backs up the habits (section 6).

Changes to this policy

If this policy changes, the date at the top changes with it. That date is the whole record. There is no notice: Nanbit does not send email, and promising a notice we would not send would be worse than saying so.

Contact

Questions, or a request about your data: delorinodenver@gmail.com.