Budgetto Privacy Policy

Last updated: April 3, 2026

Short version: Budgetto is built to keep your financial data on your device. Optional cloud-backed features are limited in scope and are clearly user-triggered.

1. Data you import

Budgetto reads only the files you explicitly choose to import (for example CSV, PDF, XML, XLSX statements).

• Transaction fields (dates, amounts, merchant names, descriptions, balances) are processed locally.
• Core transaction storage is local on your device.

2. Local storage and encryption

• Transaction database is encrypted at rest using SQLCipher (AES-256).
• Encryption keys are stored in platform secure storage (Android Keystore / iOS Keychain).
• Local preferences and rules are saved in the app sandbox.

3. Optional AI categorization

If you use AI categorization, Budgetto sends a limited payload through the Budgetto proxy backend.

• Only merchant/category-candidate information required for categorization is sent.
• Amounts, balances, and full transaction histories are not required for this AI request path.
• The feature is opt-in and starts only after explicit user action.

4. Quota, purchases, and entitlement checks

To manage AI credits and premium features, Budgetto backend may process technical purchase and quota metadata.

• Anonymous app/device identifier used for quota and entitlement state.
• Google Play purchase verification metadata (for example product id and purchase token) when you make purchases.

5. Crash diagnostics

Budgetto uses Firebase Crashlytics to identify and fix app crashes.

• Crash stack traces and technical diagnostics may be collected.
• Crash reports are intended for reliability debugging, not advertising.

6. No account required

Budgetto does not require account registration or login to use core functionality.

7. Data deletion

• Use the in-app “Clear all data” action to erase local app data.
• Uninstalling the app removes local app data from the device.

8. Contact

Questions about this policy: adrianjago95@proton.me