Privacy Policy
App: Sabr (com.zilloris.sabr)
Updated: 15 October 2026
Contact: support@zilloris.com
The short version
Your habits stay on your phone. Their names, the amounts you log and the record of each day are stored on your device, and the app never uploads them. There is no account, no sign-in and no sync.
Whatever you choose, the app sends Google Firebase a few small things: a crash report if the app breaks or a save fails, a short note each time the app opens, and a request for a few settings, such as where this policy lives and whether to offer an update. None of them carries your habit names or anything you wrote.
From version 1.1, the app also asks if you want to send usage counts: short notes of which screens and buttons get used. They are off until you say yes.
There are no ads and no advertising identifier, and nothing is sold or used to profile you. Android's own backup, described below, can copy this app's data into your own Google Drive if you have device backup switched on.
What the app stores, and where
Your habits and what you named them, the amount you recorded each day, the days you missed, the cravings you held through, your settings and your answer about usage counts are stored in the app's own private storage on your device.
There is no account to make, nothing to sign in to, and no copy of any of it held by us. We have no server for it to be held on.
What leaves the device
What you send yourself. Settings can save your page as a CSV file, handed to Android's own share sheet. You choose where it goes — a mail app, a file, a cloud folder — and once it is there, that app's or that service's terms apply, not this one's.
Apart from that copy and Android's own backup (see Backup), your habit data never leaves the phone. The app itself sends only the things in the next section.
What the app sends
Crash reports (Firebase Crashlytics), whatever you choose. If the app crashes, or a save to your page fails, a report is sent so the fault can be fixed. It holds the technical trace, the app version, your phone's model, maker and Android version, the phone's state at that moment (memory and storage in use, battery, screen orientation, whether it is rooted) and a random installation number. If you said yes to usage counts, it also lists the last few counts sent before the fault.
Visit notes, whatever you choose. Each time the app opens, Crashlytics also sends a short note that a visit started: a random visit number, the time, the installation number, the app version and your phone's model. It tells us what share of visits end in a crash.
Settings (Firebase Remote Config), whatever you choose. When the app starts — about twice a day at most, including when the phone wakes it to redraw the widget or post a reminder — it asks Firebase where this policy and the terms live, and whether to offer an app update. The request carries the installation number, the app version, your phone's model and Android version, your language and region setting, your time zone and your network address. If you said yes to usage counts, it also carries the day the app was first opened and the same facts about your page that usage counts carry. What comes back is the two addresses and two update settings, nothing else.
The policy and the terms themselves are published at zilloris.com, on GitHub Pages. Opening one in the app downloads that page: an ordinary web request that carries your network address and nothing of yours.
Usage counts (Google Analytics for Firebase), from version 1.1, only if you say yes. Usage counts are short notes of which screens and buttons get used. They are not the amounts you log.
The app asks on Today, once there is a habit on your page: "Help make Sabr better?" It asks until you answer. "No, thanks", a tap outside the question or Back all count as no: no usage counts are sent and the app does not ask again. You can change your answer any time in Settings → Usage counts. Turning it off stops the counting at once.
A count says which screen opened or what was done: for example that a habit was added (and whether you are building or quitting it), a day was marked, a craving hold was started or ended, a setting was changed and to what (never the reminder time), a copy of your page was saved, or the widget was used. It never says which habit, never its name, and never anything you type. Your answer on the coming-back screen is never sent.
Every count also carries: a random number that stays the same on this copy of the app, so counts from one phone can be put together but not linked to your name; the time it was sent and your time zone; the day the app was first opened; the app version; your phone's model and Android version; your language and region setting; how you reached Sabr's Google Play page; and the country, region and city Google works out from your network address. It also carries a few rough facts about your page: how many habits you have (in steps such as "4–6"), how many you are building and quitting, the paper and text size, whether reminders are on, and that usage counts are on.
Because each count carries its time, a count such as "a day was marked" shows when you tapped. Counts of habits are rounded into steps; how long the app is open is measured exactly by Google Analytics.
The advertising identifier is switched off in the app and its permission has been removed. There are no ads, so there is nothing to measure for them.
Who handles it. Firebase and Google Analytics are run for us by Google LLC, which processes this data on our behalf under Google's privacy policy. Crash reports and visit notes are deleted on Google's standard schedule. Individual usage counts are kept for 2 months and then deleted; totals made from them, such as how many people opened a screen in a month, carry no identifier and can be kept longer. There is no account, so none of it can be looked up by who you are.
Permissions
Notifications, if you allow them, are used only for reminders about habits you have not marked done yet, at the time you chose. A reminder can be asked to come back later that day, or to leave a habit alone for a week. Every reminder is scheduled by your phone and created on your phone: there is no push messaging service and no message from a server. A reminder shows the habit's name, so it can appear on your lock screen; Android's notification settings can hide it. Declining costs you nothing else in the app, and you can turn reminders off in Settings or in Android at any time.
The app also holds Android's ordinary network permission, used only for what is described above: crash reports and visit notes, the settings request, the download of this policy and the terms, and usage counts if you said yes. Separately, Google Play on this phone checks over its own connection whether a newer version exists, so an update can be offered; that check carries nothing about your habits. The advertising-ID permission that analytics libraries usually bring has been removed. Analytics keeps one permission, which lets it ask Google Play how the app was installed.
On your home screen
The widget is optional, and if you add one it shows what the app shows: today's date, your habits and their names, and how far each has got today. That means the name of a habit can be read by anyone who can see your home screen, without unlocking anything. If that matters for a habit, don't add the widget — the app works exactly the same without it.
The widget is drawn on your phone from data already on it, and nothing it shows is sent anywhere. If you said yes to usage counts, adding a widget and opening the app from it are counted, without anything it shows.
Backup
If you have Android backup switched on, Android may copy this app's data into your own Google Drive. It is your Drive and your Google account, not ours: we have no account, no server, and no way to see it.
That copy holds everything the app keeps, including your answer about usage counts. On a phone restored from it, the app keeps your earlier answer instead of asking again; you can change it in Settings → Usage counts.
You can turn backup off in Android's own backup settings, and the app will not mind.
Deleting your data
Deleting the app deletes the page. Uninstalling Sabr removes everything it stored on your phone — your habits, your days, your missed days, your held cravings and your settings. We hold no copy anywhere. The only ways it can come back are the two copies that are yours: Android's own backup, if you have it switched on (see Backup), and a CSV export you saved from Settings — take one first if you would be sorry to lose the record.
A copy already taken by Android backup is removed through Android's backup settings, since that copy is in your Drive and not somewhere the app can reach.
Crash reports, visit notes and usage counts already sent to Firebase are held under random numbers with no account attached, expire as described above, and cannot be traced back to you by us. Turning usage counts off stops new ones; it does not delete counts already sent.
Children
Sabr is not directed at children under 13. It never asks anyone for a name, an email address, an age or anything else that says who they are. The crash reports, visit notes and usage counts described above carry only random numbers for this copy of the app and are not tied to a person of any age.
Changes
If this policy changes, the updated date above changes with it. The app downloads this page when you open the policy inside it, so it shows the current text; the copy built into the app is only what it falls back to when there is no connection.
Contact
Questions about this policy: support@zilloris.com