Privacy Policy
Last updated:
App: BudgetLenz — personal finance management for Android, iOS, and other supported platforms.
Data controller: Coreline Logics
Contact: info@corelinelogics.com
Scope: This policy applies only to the BudgetLenz mobile application. It does not describe the corelinelogics.com website or other Coreline Logics products—those may have separate policies at their own URLs.
This policy explains how we collect, use, store, and share information when you use BudgetLenz. By using the app, you agree to this policy. If you do not agree, please do not use the app.
1. Summary
- BudgetLenz is designed to help you track accounts, transactions, budgets, goals, subscriptions, and related financial information.
- Account and sync use Supabase (authentication and cloud database). Financial and app data you save while signed in may be stored on our Supabase project and on your device (local database for offline use and performance).
- Sign-in may use email and password, Google Sign-In, or Sign in with Apple, subject to those providers' terms and privacy notices.
- Optional features include device biometrics (to unlock the app), local notifications (reminders), camera / photo access (e.g. receipt capture), on-device text recognition (Google ML Kit) for images you choose to scan, and an in-app assistant that sends your messages to our backend (Supabase Edge Functions) to generate replies.
- We do not sell your personal information. We do not use third-party advertising or analytics SDKs in the app as of the last updated date above (this may change; we will update this policy if it does).
2. Information we collect
2.1 You provide or generate in the app
- Account data: email address, authentication identifiers, and profile details you choose to add (e.g. display name, avatar) when you register or sign in.
- Financial and organizational data: accounts, transactions, categories, budgets, goals, recurring rules, subscription trackers (services you subscribe to — not Google Play billing for the BudgetLenz app unless we separately disclose in-app purchases), notes, attachments, imports/exports you perform, and similar content you enter or upload.
- Assistant conversations: when you use the AI assistant, the text you send (and related conversation metadata) is sent to our servers and stored so the feature can work; responses are generated through our backend processing.
2.2 Automatically collected / technical data
- Device and app data: such as device type, OS version, app version, and diagnostic information needed to operate sync, notifications, and security features.
- Network activity: the app communicates with Supabase and, where applicable, exchange-rate or similar non-personal public APIs (e.g. currency rates) to provide features. Requests may include technical identifiers required by those services.
- Local storage: data is stored in an on-device database (e.g. Isar) for offline access, caching, and performance; when you use cloud sync, that data is also stored in Supabase under your account.
2.3 Permissions (Android / iOS)
We request access only where needed, for example:
- Internet — sign-in, sync, assistant, and updates.
- Biometric authentication — optional app lock; biometric data stays on your device; we do not receive your fingerprint or face data.
- Notifications — budget, subscription, or similar reminders you enable.
- Camera / photos — only if you use features that capture or choose images (e.g. receipts); processing for text extraction may use on-device ML where supported.
- Exact alarms (where applicable) — only if you enable scheduling that requires precise timing on your OS version.
3. How we use your information
- Provide, maintain, and improve BudgetLenz (including sync, backup, search, reports, widgets where supported, and the assistant).
- Authenticate you and protect your account.
- Send local or push-style notifications according to your settings.
- Comply with law, enforce our terms, and protect rights and safety.
4. On-device processing
- Biometric unlock: handled by your device's OS; we do not receive raw biometric data.
- Receipt / image text recognition: where implemented with Google ML Kit, processing may occur on your device. Google's policies may apply to the SDK; see Google's documentation for ML Kit.
5. AI assistant and automated processing
When you use the assistant, we transmit your messages to Supabase Edge Functions (and any model or service we configure there) to produce answers. That processing is automated. Do not include passwords, full card numbers, or other highly sensitive secrets in assistant messages. Conversation content may be stored in our database as part of the feature.
6. Third-party services
We rely on service providers who process data on our behalf:
| Service | Role | Learn more |
|---|---|---|
| Supabase | Authentication, database, serverless functions (e.g. assistant), file storage if used | Privacy Policy |
| Google Sign-In; optional ML Kit on device | Privacy Policy | |
| Apple | Sign in with Apple (where available) | Privacy Policy |
| Public APIs | e.g. currency / exchange-rate data (typically no personal financial data in requests) | Per provider |
We encourage you to read their policies. We are not responsible for their practices beyond our configuration of the app.
7. Legal bases (EEA / UK users)
Where GDPR / UK GDPR applies, we rely on contract (providing the service), legitimate interests (security, improvement, sync), and, where required, consent (e.g. optional notifications or marketing if we ever add it). You may withdraw consent where processing is consent-based, without affecting prior lawful processing.
8. Retention and deletion
- We retain your information while your account is active and as needed to provide the service, comply with law, resolve disputes, and enforce agreements.
- You may delete your account or specific data where the app provides that option; some residual backup retention may occur on our providers for a limited period.
- Local data on your device remains until you remove the app or clear data in the app/OS settings.
Step-by-step account and data deletion (including email fallback) is described on our "Delete account and data" page for Google Play users.
9. Security
We use industry-standard measures appropriate to the service (e.g. encryption in transit for API traffic, access controls on our backend). No method is 100% secure. You are responsible for keeping your password and device safe and for not sharing sensitive information in chat or unsecured channels.
10. International transfers
Our providers (e.g. Supabase) may process data in the United States or other countries. Where required, we rely on appropriate safeguards (such as standard contractual clauses).
11. Your rights
Depending on your location, you may have rights to access, correct, delete, port, or restrict processing of your personal data, and to object to certain processing. Contact us at the email above. You may also lodge a complaint with your local supervisory authority.
12. Children's privacy
BudgetLenz is not directed at children under 13 (or the minimum age in your jurisdiction). We do not knowingly collect personal information from children. If you believe we have, contact us and we will take steps to delete it.
13. Changes to this policy
We may update this policy from time to time. We will post the new version at this same BudgetLenz policy URL (or notify you in-app or by email for material changes where required). Continued use after the effective date means you accept the updated policy.
14. Contact
Operator and data controller for BudgetLenz:
Coreline Logics
30 N Gould St Ste N, Sheridan, WY 82801, United States
If you add analytics, crash reporting, ads, or Play Billing, update this BudgetLenz policy page and your Play Console Data safety section to match.