Privacy
Privacy and data handling, written plainly.
finr is designed around on-device processing and local storage. The core promise is simple: track money movement from transactional SMS without forcing your finance history into a cloud account.
finr does not need a mandatory backend to read SMS, structure transactions, rebuild summaries, or keep your timeline usable. Export remains explicit and user-controlled.
The result is a finance workflow that stays close to the device, keeps permissions tied to real product behavior, and avoids collecting more than the app needs to function.
What finr reads
finr reads transactional SMS that indicate money moving in or out of your accounts. That message content is used to detect direction, amount, sender, time, bank clues, and related transaction context.
The goal is not inbox surveillance. The app is built specifically around bank and payment alerts that power the finance timeline.
What stays on your device
Core tracking is designed to work locally. Parsed transactions, categories, summaries, metrics, and related metadata are stored in the local Room database on the device.
finr does not require a cloud account or a mandatory backend dependency for its core tracking flow.
Why permissions exist
`READ_SMS` is required so the app can detect and parse transaction alerts. `POST_NOTIFICATIONS` is used for daily summaries and spend-limit notifications.
Permissions support specific product behavior rather than broad data collection. If a permission is not granted, the related feature cannot operate.
Exports stay user-controlled
finr supports CSV export for transactions, selected months, filtered results, and bank-card views.
Export only happens when the user asks for it. The app is structured so data sharing is explicit rather than automatic.
Local-first processing model
New SMS can be synced incrementally, duplicate ingestion is avoided, and summaries are rebuilt from local transaction state as records change.
That design keeps the product responsive offline and avoids making the app dependent on constant runtime connectivity.
Security controls
finr supports optional app-lock behavior using device security controls such as biometrics or device credentials.
Those controls are intended to protect access to the transaction timeline when the app is opened.
Website note
This marketing site can load anonymous analytics only after explicit user consent through the site consent banner.
That website behavior is separate from the Android app’s local-first finance workflow.
Current status
finr is still under active development. The product direction is clear, but wording and policy details may continue to be tightened before broader public release.
The implementation target remains straightforward: local processing, direct user control, and no unnecessary data dependency.