Privacy Policy

1. Who we are

Budket ("Budket", "we", "us") makes the Budket iPhone app, a personal budgeting app. This policy explains what the app and this website do with information about you. It is written to be read, not to be survived — if anything here is unclear, ask us and we will answer in plain words.

Budket was previously published under the name LogMyPays. Some links, such as the App Store address and our support mailbox, still carry the old name; it is the same app and the same people.

2. What we never ask for

The simplest privacy guarantee is not to hold the data in the first place. Budket does not ask for, and cannot see:

• Your bank. There is no bank connection, no open-banking provider and no card linking. Nothing is imported from an account, because the app is never given one.
• A password. Sign-in is through Apple or Google only, so there is no Budket password to store, leak or reset.
• Your contacts, location, calendar, health data or microphone. The app requests none of these permissions.
• Your photo library, in bulk. Scanning uses the camera, or a single image you pick. The app does not browse your library.

3. Your account

You create an account with Sign in with Apple or Sign in with Google. That provider tells us a user identifier and, depending on what you allow, an email address and display name. We use them to recognise your account and to keep your records attached to it — not to market to you.

If you use Apple's "Hide My Email", we only ever see the relay address Apple generates. That is fine; the app works the same way.

Authentication and our database are operated on Supabase, which hosts the account and enforces row-level security so that one account cannot read another's data.

4. What we store

In your account we keep the records the app is for:

• Your buckets, their budgets and the changes you have made to them;
• Your transactions — amount, date, bucket, merchant or note, and line items where a scan produced them;
• Your settings: display name, avatar choice, base currency, language and the day your budget month resets;
• Your scan allowance for the current month, so the limit can be metered fairly;
• Your support tickets and the messages in them, if you write to us from inside the app.

This is stored so your budget is not trapped on one handset — reinstall the app or move to a new iPhone and your records come back. It is transmitted over TLS and encrypted at rest by our hosting provider. We do not sell it, rent it, or share it with advertisers or data brokers. We have no advertising SDK in the app at all.

Receipt and document images are not in that list. They are written to the app's own storage area on your device and are never uploaded to our servers.

5. Receipt and document scanning

When you scan a receipt or a document, the image is sent over an encrypted connection to Microsoft Azure Document Intelligence, which performs the optical character recognition that extracts the merchant, the date, the total and the line items. The request is made by our own server function, so your device never holds the Azure credentials.

Microsoft processes the image transiently for that single request and does not use it to train its models. Once the text has come back, the image is not retained by the service. The photograph stays on your phone, inside the app, and you can delete it there.

What we keep afterwards is the result you accepted: a transaction, its fields, and the count of scans you have used this month.

Scanning is an optional feature. If you never use it, no image of yours ever leaves your device through Budket.

6. Subscriptions

Budket Pro is sold as an auto-renewing App Store subscription. Payment is handled entirely by Apple — we never see your card details. Entitlements are managed through RevenueCat, which receives an anonymous identifier for your account and your purchase history so the app can tell whether Pro is active. RevenueCat has no access to your budgets or transactions.

7. Support messages

If you message us through Settings → Support → Talk to Us, the ticket and your messages are stored in your account so that a person on our side can read and answer them. Closing a ticket marks it resolved, and it is deleted automatically after 30 days.

8. Analytics and crash reports

There is no analytics SDK, no tag manager and no advertising identifier in the app. We rely on the crash and performance reporting Apple provides in App Store Connect for devices whose owners have opted in to sharing it with developers, which is aggregated and not tied to your identity.

This website is just as quiet: budket.app loads no web fonts, no analytics and no third-party scripts, and sets no cookies. Our host keeps ordinary server logs, which include IP addresses, for security and troubleshooting.

9. Children

Budket is not directed at children under 13, and we do not knowingly collect information from them. If you believe a child has created an account, write to us and we will delete it.

10. Your rights and deletion

You can erase everything yourself: Settings → Data & Privacy → Delete Account & Data. That deletes your account and the records held with it. It cannot undo an App Store purchase — a subscription is cancelled in your Apple subscription settings, not here.

Depending on where you live you may also have the right to access a copy of your data, to correct it, to object to processing, or to complain to a data protection authority. Ask us and we will help; we do not charge for it and we do not make you prove a reason.

We keep your records for as long as your account exists. Support tickets are removed 30 days after they are closed.

11. Changes to this policy

If this policy changes we will update the page and the date at the top of it. Changes that materially affect what happens to your data will be announced in the app as well.

12. Contact

Questions, requests or corrections: support@logmypays.com. Pro subscribers can also message us from inside the app, which is usually faster because we can see what went wrong.