Privacy

Privacy policy

Tally is built to know as little about you as possible. Your accounts stay on your phone, encrypted, and the developer never receives them. This policy explains what that means in detail, for the app and for this website.

Effective

At a glance

Summary of Tally’s data practices
Data the app collectsNone. Nothing you add to Tally leaves your phone unless you export a backup yourself.
Data shared with othersNone. Nothing is sold, shared or used for advertising.
Where your accounts areOnly on your phone, encrypted.
Internet accessThe Android release has none.
Deleting your dataDelete accounts in the app, erase the vault, or uninstall Tally.

Who this covers

This policy covers the Tally authenticator app for Android and this website, tally.mohammadhajeer.com. Tally is developed and published by Mohammad Hajeer, referred to here as “the developer”.

If you install Tally from Google Play, Google’s own terms and privacy policy apply to the Play Store and to your Google account. They are separate from this policy.

What the app keeps on your phone

To show your codes, Tally stores on your phone:

  • Your accounts: for each one, the service name, your account name, its secret setup key and its code settings (algorithm, number of digits and period), whether you pinned it, and when you added it. These are kept only in Tally’s encrypted vault.
  • Your preferences: appearance, auto-lock and idle-lock timing, the date of your last backup on this phone, and which notices you’ve dismissed. These hold no account information and are stored in Tally’s private app storage.

None of this is sent to the developer or to anyone else. The developer has no server that could receive it and no way to see it.

How it’s protected

The vault is encrypted on your phone, and its key is protected by the Android Keystore. It opens only after you confirm with your fingerprint or your phone’s screen lock (PIN, pattern or password). Tally asks Android to leave the vault out of automatic cloud backups and device transfers. How Tally protects you explains this in detail.

Fingerprint checks are handled entirely by Android. Tally never receives your fingerprint, face data or screen-lock PIN; it only learns whether Android confirmed it’s you.

Camera and photos

Tally asks for the camera only so you can scan the QR code a website shows when you set up two-factor authentication. The camera runs only while the scanner is open. Images are decoded on your phone and are not saved, uploaded or logged. The permission is optional: you can type the setup key instead, and you can turn camera access off at any time in Android’s settings.

You can also choose a picture of a QR code, such as a screenshot. Android’s photo picker gives Tally only the picture you select, so Tally needs no permission to your photos. Tally reads the code from it on your phone and doesn’t keep, upload or log the picture.

Network, analytics and ads

The Android release of Tally doesn’t request internet access, so the app can’t send data anywhere itself. It contains no analytics, advertising, tracking or crash-reporting services, and it doesn’t use an advertising ID.

Tally 1.4.1 and later contain no Google Play library. Updates arrive through the Play Store’s own automatic or manual updates, as for any other app.

Versions up to 1.4.0, if installed from Google Play, could ask the Play Store app whether an update was available, using Google’s in-app updates library. Google Play performed that check and any download. According to Google, the library collects device metadata, the app’s version and the list of its installed modules and asset packs, to determine whether an update is available and how large it is; Google states that this data is encrypted, isn’t transferred to third parties and is deleted after a fixed retention period. No account names, setup keys or codes were involved.

Settings has Help, Send feedback, Rate Tally and Share Tally links. Each opens another app you choose (your browser, email app, the Play Store or Android’s share menu) with a fixed page, address or message. The feedback email’s subject names the app version. Tally adds nothing else and sends nothing itself; what you then send is up to you.

Backups you create

You can export an encrypted backup file. It’s created only when you ask, protected by a password you choose (or six words Tally generates on your phone), and saved where you pick in Android’s save screen. Tally never stores or sends that password.

If you save a backup to a cloud storage service, that service holds the encrypted file under its own terms. The file can’t be read without its password.

You can also import accounts from another authenticator’s export, such as a Google Authenticator export code or an Aegis or 2FAS file you choose. Tally reads it on your phone, adds only the accounts you confirm to the encrypted vault, and doesn’t keep, upload or log the export. If the export has a password, Tally uses it only to open the file and doesn’t store it.

Moving to a new phone

Tally can send your accounts from your old phone to your new one as a series of QR codes that the new phone scans. The codes travel only from one screen to the other phone’s camera: nothing goes over a network, to the developer or to anyone else.

The codes are encrypted for a one-time key that exists only in the new phone’s memory while its transfer screen is open, so a photo or video of them can’t be read. Neither phone saves the transfer to a file, and both forget its keys when the transfer screen closes.

Copying codes

When you tap a code, Tally copies its digits to Android’s clipboard and marks them as sensitive, so Android 13 and later keep them out of clipboard previews. A minute later Tally clears the copy, or as soon as you next open Tally if you’ve switched apps, since Android doesn’t let apps reach the clipboard in the background. Apps you paste into can read what you paste. If you copy Tally’s generated backup words, Tally clears them from the clipboard after 30 seconds.

Keeping and deleting data

Everything Tally stores stays on your phone until you remove it:

  • Delete a single account from its actions menu in the app.
  • Remove everything with Settings › Erase vault, which also destroys the key that protected it.
  • Uninstalling Tally deletes its data from your phone. Without a backup, accounts can’t be recovered afterwards.

Backup files you’ve exported are yours: they stay wherever you saved them until you delete them. Because the developer never receives what you store in Tally, there is nothing from the app for the developer to delete or hand over on request.

This website

This website is a set of static pages. The site itself sets no cookies, uses no analytics, advertising or tracking, and loads its fonts from this site rather than from third parties.

If you choose a light or dark theme here, your browser remembers it in its local storage on your device. It isn’t sent anywhere, and you can clear it by clearing this site’s data in your browser.

The site is hosted by Vercel. To deliver pages and protect the site, Vercel processes technical information about each visit, such as your IP address, the approximate location derived from it, your browser and the page you request. Vercel acts as a processor on the developer’s behalf and describes its practices in its privacy policy. The developer can view basic request logs (such as the page, time, response status and browser) in Vercel’s dashboard for a limited period set by the hosting plan. Vercel’s analytics products aren’t used on this site.

Emailing support

If you email mohammadhajeer.dev@gmail.com, the developer receives your email address and whatever you include, and uses them to reply to you. The address is a Gmail account, so Google handles those messages under its own terms. Please never send setup keys, codes, QR codes, backup files or backup passwords.

Changes to this policy

If Tally’s handling of data changes, this policy will be updated before the change takes effect, and the effective date above will change with it.

Contact

Questions about this policy can be sent to mohammadhajeer.dev@gmail.com.