Almon is an envelope budgeting app for iPhone and Mac, made by Caleb Stratton. This page covers what the app stores, where it goes, and who can read it.
What Almon stores
Almon only stores what you type into it. There is no account to create and no profile:
- Transaction amounts, dates, vendors, descriptions, and notes
- Names and descriptions for your budgets, envelopes, and folders
- Account names, and whatever balances you record against them
- Recurring templates and how they split money between envelopes
- App preferences, like which list style you prefer
Almon never asks for your contacts, photos, camera, microphone, location, or health data, and it has no way to reach them. It does not connect to any bank, and it will not import anything on its own. Every number in the app is one you typed, or one you brought in from a file you picked yourself.
Where it goes
On your device
By default nothing leaves the device you entered it on. It sits in Almon's own storage, and it gets included in your device backups the same way any other app's data does.
In your iCloud account
Turning on sync for a budget tells Almon to copy that budget into your private iCloud database, using Apple's CloudKit service, so your other devices can see it. That is your own iCloud storage, attached to your Apple Account. Apple handles it as part of iCloud under Apple's Privacy Policy.
I cannot read any of it. Developers have no access to the contents of a user's private CloudKit database. Your transactions, your balances, even whether you have opened the app: none of that is visible to me.
With people you invite
You can share a budget with someone else, a partner for instance, using Apple's built-in CloudKit sharing. That only happens when you pick a specific person and send them an invitation. They can see and edit the budget you shared with them and nothing else, and you can cut off their access whenever you want. Apple handles the whole exchange. None of it routes through any system of mine.
Files you export
Exporting a CSV or a budget archive hands the file straight to you, and you choose where it goes. After that the copy is yours to look after, and this policy no longer covers it.
What Almon does not do
There is no analytics or telemetry in Almon. No usage data is reported to me or to anyone else. There are no ads, no ad or tracking libraries, and nothing that follows you across other apps or websites. The app contains no third-party SDKs at all, and makes no network connection except to Apple's iCloud on your behalf. I could not sell your data if I wanted to, because it never arrives.
Diagnostics
Almon writes technical messages to your device's system log, things like whether a sync attempt worked, which helps when something needs troubleshooting. Those stay on the device. If you have separately chosen to send diagnostics or crash reports to Apple in your iOS or macOS settings, Apple handles that under their own policy. Any crash report that reaches me describes the failure, not your budget.
Your control over your data
You can turn sync off for any budget and keep it on one device. Deleting a budget in the app removes it from iCloud too. Revoking a share cuts off the other person's access right away. Deleting the app clears its data from that device, and any iCloud copy can be removed from your device's iCloud storage settings. You can also export everything at any time, as a CSV or as a full archive.
There is no request to file with me for a copy of your data, or to correct or erase it, because I never hold it in the first place.
Children
Almon is a general purpose budgeting tool and is not aimed at children. I do not knowingly collect information about anyone, whatever their age.
Changes to this policy
If a future version of Almon changes how data is handled, I will update this page and the effective date at the top before that version ships. Anything significant will show up in the app's release notes too.
Contact
Email support@calebstratton.com for help with the app, bug reports, or feature requests, or caleb.a.stratton@gmail.com with questions about privacy specifically.