Tallymile Privacy Policy
Last updated: October 15, 2026
The short version
The app collects nothing. There is no Tallymile server, no Tallymile account, no Tallymile cloud, and Tallymile's own code makes no network requests on its own: not to us, not to analytics companies, not to Apple. There is one optional exception you control: if you turn on street address lookup in Settings, the app asks Apple's geocoder to turn a drive's start and end coordinates into addresses (section 7). It is off by default. iOS itself may contact Apple's location service when GPS starts (section 8). The only personal data we ever hold is an email you choose to send us (section 12).
Your drives, places, vehicles and reports stay on your device, encrypted, until you export them or erase them yourself. The one exception is the address lookup above: when you turn it on, each new drive's start and end points go to Apple.
Every claim below describes how the software is built as of the date above, and you can check the network claims yourself rather than take them on trust (section 2 tells you how). Read the rest the same way: as a description of a design, not as a guarantee that nothing can ever go wrong on your phone. Where iOS imposes a limit on what we can say, we say so plainly (section 8), and section 9 explains what no app, ours included, can promise you. This policy is a plain-language notice. The contract is the Terms of Use, which contains our limited warranty that the app matches its described design, and the limits on our liability.
1. What Tallymile stores (on your device)
Tallymile keeps your drive log in a local SQLite database on your iPhone.
| Data | Where it lives | Sent to us or to any server? |
|---|---|---|
| Drives: start and end times, start and end coordinates, distance | Encrypted local database | Only the start and end coordinates, to Apple, if you turn on address lookup (section 7); otherwise never |
| GPS points recorded during a drive | Encrypted local database | Never |
| Your tag for each drive (business or personal) and purpose | Encrypted local database | Never |
| Notes, parking and toll amounts | Encrypted local database; notes carry a second encryption layer | Never |
| Named places (a name and a coordinate), vehicles, odometer readings | Encrypted local database | Never |
| Government mileage rates and any overrides you enter | Encrypted local database | Never |
| Times automatic detection was paused or off | Encrypted local database | Never |
| Saved reports (PDF and CSV files) | Protected local files, excluded from backups | Only if you share them |
| Settings and preferences | Device only | Never |
| App lock PIN (as a salted PBKDF2 hash) and lockout state | Device Keychain only | Never |
| Database encryption key | Device Keychain only | Never |
A drive log is a location history. We treat it that way: it is encrypted at rest, kept out of backups, locked behind your PIN or Face ID if you choose, and never copied anywhere by the app, except the start and end points of new drives, which go to Apple's geocoder only while address lookup is on (section 7).
2. What Tallymile does not do
- No network requests of its own. Tallymile's code makes no network calls except the optional address lookup described in section 7, which is off until you turn it on. There is no maps SDK. Route thumbnails are drawn on the device from your own GPS points, not downloaded map tiles. With address lookup off, the app works fully in Airplane Mode.
- No account. No name, email, phone number or sign-up of any kind.
- No analytics or telemetry. No Firebase, Mixpanel, Amplitude or anything like them.
- No crash reporting. If Tallymile crashes, we do not find out unless you email us.
- No advertising identifiers. No IDFA, no ad SDKs, no tracking.
- No third-party services. The only third-party dependency is GRDB, a local SQLite library, in a build that includes SQLCipher for database encryption. Neither makes network calls. Their copyright notices and license texts are shown in the app under Settings > About > Acknowledgements, and the Terms of Use list them in section 11.3.
- No in-app purchases. There is no StoreKit code in the app. You pay once on the App Store; the app itself never talks to a payment system.
- No push notifications. Reminders are scheduled on your phone by the app and delivered by iOS once you allow notifications. Tallymile is never registered with Apple's push service and has no server to send from. A new-drive reminder shows the drive's time and distance, never a place, and the app icon can show how many drives are untagged.
- No Home Screen widgets and no app groups. Widgets keep snapshots of your data outside the app lock, so there are none, and no other process shares the app's data container. The one on-device exception is an optional Live Activity: while a drive is being recorded, the elapsed time, the distance so far and whether the drive was started by you or detected can appear on the Lock Screen and in the Dynamic Island. A drive you start with Start shows it at once; a drive Tallymile detects in the background shows it once you open Tallymile during the drive, because iOS lets an app start a Live Activity only while it is on screen. It never shows where you are, is drawn on your device by iOS, is not registered for push updates, and disappears the moment the drive ends. Turn it off in Settings.
- No automatic tagging. Tallymile never decides whether a drive was business or personal. It does not infer a tag from your history, your schedule, or the places you name. Every tag is one you chose, with a tap in the app or in a file you imported, and the report says so. Untagged drives have no purpose.
Check it yourself. Put your iPhone in Airplane Mode with address lookup off and record a drive with the Start button: recording, the drive list, tagging, reports and exports all keep working. If you want to go further, run a proxy or packet capture while using Tallymile, or open Settings > Privacy & Security > App Privacy Report on your iPhone, which lists the network domains each app has contacted. Those tests show you the app's network behavior. They cannot show you encryption at rest, the Keychain protection class, backup exclusion or how Erase Everything works; for those you are relying on the written description in this policy and in the Terms of Use, backed by the limited warranty in the Terms. If you ever see Tallymile do something this policy says it does not do, email admin@lomalabsllc.com with what you saw and how to reproduce it (please do not send your drive data). We will investigate and, where a report is confirmed, fix the app or fix the description, whichever is wrong, within a reasonable time.
3. Encryption and app lock
Your data is protected in layers:
- Database encryption at rest. The entire SQLite database is encrypted with AES-256 (SQLCipher). The key is generated on your device and stored only in the iOS Keychain with a device-only protection class, so it never leaves the device and is not included in any backup.
- iOS file protection on top. The database files also use iOS Data Protection with the class iOS calls complete until first user authentication: after your iPhone restarts, the files stay encrypted and unreadable until you first unlock it. After that first unlock they stay readable even while the screen is locked, which is what lets a drive that ends while the screen is locked still be written.
- Notes get a second layer. Drive notes are encrypted again with their own key before they are stored, so even a decrypted database file would not expose them in plain text.
- App lock PIN. If you set a PIN, it is never stored anywhere. Tallymile derives a PBKDF2 hash using a random salt generated each time you set a PIN, and keeps only that hash and its salt in the Keychain. Failed-attempt lockout state also lives in the Keychain. iOS does not remove Keychain items when an app is deleted, but Tallymile deletes its own old entries on the next fresh install, so deleting and reinstalling starts you over with no data and no app lock. Even if one of those deletions failed, the old key would open nothing and no lock would be set.
- Biometrics. You can lock the app with Face ID or Touch ID instead of a PIN. Biometric matching is handled by iOS, which offers your device passcode if the scan fails; Tallymile never sees your face or fingerprint data.
- Siri and Shortcuts respect the lock. While the app lock is on, a Siri or Shortcuts request to tag a drive, pause detection or anything else that reads your drives answers "Open Tallymile to do that." and changes nothing until you have unlocked the app; the app locks again whenever it leaves the screen. Starting a drive, stopping one and resuming detection still work, and a stop then says only "Drive saved.", with no distance.
What these layers do and do not do. Encryption at rest protects your database from someone who copies the files without the key. The app lock protects against someone who has your unlocked phone in their hand. Neither protects against everything. If your iPhone is jailbroken, compromised by malware, unlocked and left with someone who knows your passcode, or affected by a flaw in iOS itself, the protections we build on top of iOS can be bypassed, and we would have no way to know. We describe the layers accurately, we keep them current as best we can, and we do not claim they are unbreakable. Section 9 says more about this.
4. Backups: your Tallymile data is excluded
Tallymile's database and saved reports are deliberately excluded from iCloud backups and local device backups. The encryption key is likewise unrecoverable from any backup.
This is a privacy feature with a real cost, and we want you to understand it: if you lose or wipe your device, your drive log is gone. No backup will restore it. If your log matters to you, and for a tax record it usually does, export a report regularly (section 6) and store the files somewhere you trust. A monthly reminder to export is on by default in Settings and is delivered once you allow notifications; you can turn it off there. There is no backup file feature: the reports you export are the only copy.
5. Location and motion
- Manual mode. Location is used while you have a drive started, and for a single fix when you tap Use my current location to name a place. Outside those moments, the app asks iOS for nothing.
- Automatic mode. If you choose it, Tallymile asks for the Always location permission and for motion activity. iOS then wakes the app when you arrive at or leave a place you have named, when you leave the spot where your last drive ended, when your phone has moved a long way, or when it detects a departure. Arriving at a named place only helps end a drive in progress; nothing is stored from the wake-up itself. The app checks motion activity to see whether you are driving, and if so records the drive with GPS until you stop. Drives shorter than about half a mile are not saved in this mode. Between drives, the app does not run GPS; it waits for iOS's low-power wake-ups. Everything iOS gives the app is processed and stored on the phone. The only part that leaves it is each new drive's start and end points, sent to Apple if you turn on address lookup (section 7).
- Motion activity tells the app whether you are driving, walking or still. It is used to start and stop drives. It is not stored.
- You can switch to manual mode in Settings, pause detection with the Pause switch in Settings or the Pause Tallymile Siri shortcut (a timed pause keeps iOS's coarse significant-location-change wake-up registered so detection can resume when the pause ends, but nothing is detected or recorded while paused; an indefinite pause turns detection fully off), or turn location off for the app in iOS Settings at any time. The app remains usable in manual mode with the When In Use permission.
6. Export, reports and sharing
Reports (PDF and CSV) are generated on your device. Saving a report keeps a copy in the app's protected files. Sharing a report opens the standard iOS share sheet and you decide where it goes: Files, AirDrop, Mail, a bookkeeping app. If you send it to iCloud Drive, email or another service, that copy is governed by that service's privacy policy. That is your call to make, and yours only. Your data is never locked in: the CSV opens in any spreadsheet. Tallymile never sends a report on its own and has no way to send anything to an employer, an accountant or a tax authority; a report reaches them only if you send it. Reports carry the date of the app's rate table and the rates used, which are figures from the app, not information about you.
7. Optional address lookup
Drives are recorded as coordinates and labeled with the places you have named. If you would rather see street addresses, you can turn on Look up street addresses in Settings. When it is on, Tallymile sends the start and end coordinates of each new drive to Apple's geocoding service, skipping any endpoint that is already inside a named place, and stores the address it gets back in your encrypted database. For most people that includes their home address, unless Home is a named place. Apple describes how it handles those requests in its own privacy policy; we have no access to them and no record of them. The switch is off by default, nothing is sent while it is off, and turning it off stops future lookups immediately. Addresses already stored stay in your database until you edit or erase them.
8. Honest limits: assisted GPS and detection
- Assisted GPS. When any app uses GPS, iOS itself may contact Apple's location services to get a faster satellite fix. That traffic comes from the operating system, not from Tallymile, and no app can prevent it. In Airplane Mode it stops, GPS keeps working (it is receive-only), and so does Tallymile.
- Detection has limits. Automatic detection depends on iOS waking the app and on motion activity confirming that you are driving. Drives shorter than about half a mile are not saved in automatic mode; drives that begin in an underground garage and the first stretch of any drive can be missed or recorded late. The app tells you this during setup and in the Privacy screen, offers a manual Start button, asks you during setup to review your drives weekly, and offers a weekly reminder. It never claims to catch every drive.
9. What no app can promise
Everything in this policy describes the software we ship, and you can verify its network behavior in an afternoon. Here is what this policy is not: a guarantee that your data is safe no matter what.
No software is free of defects, and none is immune to compromise. Tallymile runs on a phone we did not build, on an operating system we do not control, next to other apps you chose. If the phone is lost while unlocked, if iOS has a vulnerability, if you install something that should not be trusted, if you back up or screenshot or share data yourself, or if there is a bug in our code that we have not found yet, your data may be exposed or lost, and nothing on this page would have prevented it.
So please read the statements in this policy for what they are: a description of how the app is designed, as accurate as we can make it on the date above, together with the tools to check the parts you can check. They are not a guarantee that nothing can go wrong. The Terms of Use put this in legal language: a limited warranty that the app matches its described design, with a fix-or-refund remedy, and a limit on what we can be held liable for beyond that. We would rather tell you that here, plainly, than have you find it in the fine print.
Our commitment is this: we will not add data collection, we will not quietly change the architecture, and if we learn that any claim on this page is wrong, we will fix the app or correct the claim. If the architecture ever changes in a way that matters, the Terms of Use change with it, and the app asks you to accept the new version before you continue.
10. Erasing your data
Settings > Erase Everything permanently deletes:
- The database (all drives, GPS points, tags, places, vehicles, odometer readings, rates, report records and the times detection was off), which is wiped and re-keyed with a new key so the old key opens nothing
- Saved report files, caches and temporary files
- The notes encryption key, and the PIN hash and lockout state from the Keychain
The database key is replaced rather than removed: the new key opens only the empty database. If any step fails, Tallymile tells you exactly what could not be deleted instead of reporting false success.
Deleting the app removes the database and local files. iOS does not remove Keychain items when an app is uninstalled, so Tallymile cleans up after itself: on the next fresh install, when no database is present, it deletes its old encryption key, PIN hash and lockout state before doing anything else. Deleting and reinstalling therefore starts clean, with no data and no app lock, which is also the way past a forgotten PIN.
Reports you shared elsewhere are outside the app and outside this erase; delete them where you sent them.
There is no server copy to chase down. When it is gone, it is gone.
11. Children's privacy
Tallymile is not directed at children under 13. The Terms of Use require users to be at least 13, and a parent or guardian to accept the Terms for anyone under 18. Tallymile collects no personal information from any user of any age, because there is nothing to collect it with, which also means we cannot verify anyone's age.
12. Your rights, and the one thing we do hold: your email
The app sends no personal data to us or to anyone. We therefore have no user data to access, correct, port or delete: everything is on your device, under your control, and access, portability (CSV and PDF export) and erasure exist by default. If a privacy law where you live gives you rights over data a company holds about you, you are welcome to ask, and the honest answer will be that we hold none from the app.
If you email us. The one kind of personal data we do hold is correspondence you choose to send to admin@lomalabsllc.com: your email address, your name if you give it, and whatever you write, which for an arbitration opt-out or a refund request includes the approximate date you bought the app. We use it only to answer you and to keep a record of opt-outs, refunds and dispute notices where the Terms of Use require one. We do not share it, sell it or use it for marketing. A refund we pay ourselves needs a way to pay you, so we will ask for a PayPal address or similar and delete it once the refund clears. We keep ordinary correspondence only as long as we need it to help you, then delete it, and we keep opt-out, refund and dispute records for as long as the Terms make them relevant. You can ask us to delete your correspondence at any time, and we will unless we need it for one of those records. Please do not send us your drive log; if you do, we delete it once your report is handled.
Our website. Our website runs no analytics and sets no cookies. Our hosting provider may keep standard server logs, which we do not use to identify anyone.
13. Changes to this policy
Updates will be reflected in the "Last updated" date above and noted in App Store release notes when significant. Because there is no account, we have no way to notify you individually, so the date at the top is the record. The core commitment, no data collection and no network code beyond the one switch you control, is an architecture rather than a setting. We will not add data collection, and if the architecture ever changes the Terms change with it and the app asks you again. This policy is a plain-language notice, and the Terms of Use are the contract. If the two ever seem to disagree about what the app does, tell us, because one of them is wrong and we will fix it.
14. Contact
Email: admin@lomalabsllc.com
We are a small independent team and aim to reply within 5 business days.
Bottom line: Tallymile is built so that we never have your data. We cannot sell what we do not have, leak what we never received, or hand over what does not exist. What we cannot do is make your phone unbreakable, so treat this page as an honest description you are welcome to test, and read the Terms of Use for what that means if something goes wrong.