Privacy Policy for Budgetty
Budgetty (“the app”, “we”, “us”) is a personal budgeting application that turns photos of your receipts into organized spending records. This Privacy Policy explains what information the app collects, how it is used, and the choices you have. By using Budgetty you agree to this policy.
- Your financial data (receipts, items, prices, categories, budgets) is stored locally on your device. We do not sync it to our servers.
- To create records from a receipt, the image or PDF you submit is sent to our processing service and to our AI provider, used only to extract the data, and is not stored afterward.
- We require an account (email or Google sign-in) so the app can authenticate you. We do not sell your data or use it for advertising.
- The app sends crash reports so we can fix bugs. These contain technical diagnostics only — never your receipts or financial records — and you can turn them off at any time on the Account screen.
1. Information we collect
a. Account information. Budgetty requires you to sign in. Authentication is handled by Google Firebase Authentication. Depending on how you sign in, this includes your email address, and, for Google sign-in, your Google account identifier and display name. We use this solely to create and secure your account.
b. Receipt content you submit. When you scan or upload a receipt (photo or PDF), the image is transmitted to our cloud processing service and to our AI provider (Anthropic) to extract structured information such as store name, date, line items, prices, and discounts. The image is processed in transit and is not retained on our servers after extraction. Your receipt data is used only to create your records and is not used to train AI models.
c. Financial records. The extracted records (items, prices, quantities, categories, stores, dates, discounts) and any budgets you set are stored locally on your device using the app's on-device database. This data is not transmitted to or stored by us.
d. Settings. Your preferences (theme, accent color, currency, date format) are stored locally on your device.
e. Purchase information. If you buy a subscription, the transaction is processed by the store you installed Budgetty from — Google Play Billing on Android, or Apple's App Store on iOS. We receive confirmation of your subscription status from that store but do not receive or store your payment card details.
f. Crash and diagnostic reports. To find and fix bugs, Budgetty uses Firebase Crashlytics to report crashes and errors. When the app crashes, the report may include the stack trace of the failure, your device model, operating system version and app version, basic device state at the moment of the crash (such as available memory and storage), and a randomly generated app-installation identifier that lets us tell one crashed installation from another. This identifier is not your name, email, or advertising ID, and Budgetty does not use an advertising identifier at all. Crash reports never contain your receipts, items, prices, budgets, or any other financial record. This is on by default and you can turn it off at any time using the Crash reporting switch on the Account screen; turning it off stops collection from that point on.
We do not collect location data or contacts, and Budgetty contains no advertising SDKs and no behavioural or usage-analytics SDKs — the crash reporting described in (f) is the only diagnostic data the app sends.
2. How we use information
- To authenticate you and provide access to the app.
- To extract and categorize the data from receipts you submit.
- To provide premium features to subscribers and enforce free-tier limits.
- To diagnose crashes and improve the app's stability, where crash reporting is enabled.
- To maintain the security and integrity of the service.
We do not use any of this information for advertising, profiling, or automated decision-making, and we do not sell it.
3. Service providers (subprocessors)
- Google Firebase (Authentication and serverless processing) — Google Ireland Ltd. / Google LLC. Receipt-processing runs in the European Union (europe-west1).
- Firebase Crashlytics (Google) — receives the crash and diagnostic reports described in Section 1(f), where you have left crash reporting enabled.
- Anthropic (Claude AI) — used to extract data from the receipt images you submit.
- Google Play Billing (Android) / Apple App Store (iOS) — process subscription purchases.
Each provider processes data only as needed to deliver its part of the service.
4. Data retention
- Account data: retained until you delete your account.
- Receipt images: not retained after extraction.
- Financial records and settings: stored on your device and retained until you delete them in the app or uninstall the app. You may also export them to a file of your choosing using the in-app backup feature; that file is controlled by you.
- Crash reports: retained by Firebase Crashlytics for up to 90 days.
5. Your rights and choices
- Access / export: You can export your data at any time from the Account screen.
- Delete local data: You can delete individual receipts and items in the app, or remove all local data by clearing the app's storage or uninstalling it.
- Delete your account: Use “Delete account” on the Account screen, or see Section 6 below.
- Turn off crash reporting: Use the “Crash reporting” switch on the Account screen. It is on by default; switching it off stops the app sending any further crash or diagnostic reports.
- Depending on where you live (for example, the EEA or UK under the GDPR), you may have rights to access, correct, delete, or restrict processing of your personal data.
6. Account and data deletion
You can permanently delete your account and all on-device data directly in the app from the Account screen (“Delete account”). You may also request deletion of your account and the authentication data associated with it by contacting us at kamskstudio@gmail.com. We will process your request within a reasonable period.
7. Children's privacy
Budgetty is not directed to children under 16, and we do not knowingly collect personal information from them.
8. Data security
We use industry-standard measures, including encrypted transport (HTTPS/TLS) and authenticated access to our processing service. No method of transmission or storage is completely secure, but we work to protect your information.
9. Changes to this policy
We may update this policy from time to time. Material changes will be reflected by updating the “Last updated” date above.
10. Contact
Data controller: Kamsk Studios
Contact: kamskstudio@gmail.com