HOW IT WORKS UNDERNEATH
Your bank messages are read where they arrive and never leave the device. The engines that decide what you can spend hold no database, no network and no clock of their own — so every figure the app shows can be reproduced from its inputs, and explained back to you.
01
The single most sensitive thing a money app can touch is the stream of bank alerts on your phone. Finscious reads them where they land.
A parser of roughly 1,400 lines runs entirely on the phone, covering fifteen banks and eighty-eight sender headers — and still extracting from issuers it has never seen.
A cheap filter written in Kotlin decides at the broadcast itself whether a message is even financial, tuned for recall rather than precision: a missed transaction cannot be recovered later, a false positive can simply be dismissed.
The raw message and every transaction field derived from it remain in the local encrypted record; they are not transmitted to Finscious.
The permission to read your inbox is deliberately not requested. Finscious sees the alert as it arrives and never queries the message store.
The local-only boundary is enforced at the app API layer so financial routes cannot be sent to the backend in this build.
02
The maths that decides your money is written as pure functions: no database handle, no network call, no reading of the system clock. They take facts and return a decision.
Cadence works out the daily number — weighted to how your week actually runs, capped, and smoothed so it can never lurch between one morning and the next. Underspend is swept forward rather than quietly absorbed.
Unnati decides what this month's savings should do, ranking goals and loan principal on one list by what it costs NOT to fund them. A deadline or an interest rate earns priority; neither realm outranks the other by default.
Vyom scores financial fitness from nine factors — and a factor that does not apply to you has its weight redistributed rather than being scored as a zero.
Cash turns wallet counts into dated spending, because nobody can recall a week of small cash spends but anyone can open their wallet and look.
Insight raises findings on its own, and stays silent rather than reporting a zero — a "₹0" reads as a measurement, and that is exactly what it is not.
The money maths runs locally and can be tested with no network or clock, so the app can tell you why a rupee went where it went without sending your ledger away.
03
Promises are cheap. These are properties of the system, and each one is a mechanism rather than an intention.
Financial records are encrypted at rest in the device-local database; the key is generated on the device and is never sent to Finscious.
Encrypted recovery backups are protected by a 12-word phrase that Finscious never receives, so users must retain both phrase and backup file.
Identity, consent, support and limited technical records remain separate from financial records and are processed in India.
Consent is versioned and withdrawable, and withdrawal disables the message receiver at the operating-system level rather than only in the app.
There is no advertising identifier, no analytics toolkit and no crash-reporting SDK. Those are absent from the build, not switched off in a settings screen.
04
A budgeting app that is subtly wrong is worse than none, because the person trusts it. The defences are part of the product.
Focused tests cover local-only API boundaries, ledger-to-plan reconciliation, historical scheduled payments, backup import and financial calculations.
A wire-contract lock protects the identity and account endpoints that older installed apps still depend on.
A layout audit that renders every screen and sheet at both Android phone widths and fails on any overflow — because an overflow silently clips in a release build and the user simply never sees the end of the number.
A rendered gallery of every screen, so a layout defect is reviewable rather than discovered by a user.
The local database schema and encrypted-backup import paths are exercised as fresh and restored user data.
WHY IT MATTERS BEYOND THE APP
Built for how Indian households are actually paid
A salary that lands on one day of the month, not a little at a time. Bills and EMIs that fall due between paydays. Bank alerts by SMS. UPI for everything small, and far more cash than most apps admit. Finscious was designed around all of that from the start, rather than adapted to it later.
The missing piece is coordination, not more data
Households do not lack financial information — they lack a unified system that understands how every part of their financial life interacts and translates that understanding into practical, coordinated decisions. Finscious is built to be that system.
Aligned to the UN Sustainable Development Goals
Target 1.4, on equal access to economic resources and financial services. Target 8.10, on widening access to financial services for everyone. Target 10.2, on including people in the economy whoever they are. Each of those depends on families being financially steady, and that is the thing Finscious works on.
Built to Indian rules, in India
You are asked for consent in plain language, and we record which version you agreed to. There is a named grievance officer. You can export your data or delete it yourself, without asking us. It is stored in India. All of this follows the Digital Personal Data Protection Act, 2023 — and several parts were true before the law required them.
The current technical detail lives on this page so the privacy and local-first facts stay aligned with the shipping product.
Read the user manual
Product
How It Works
Features
Technology
Why Finscious?
User Manual
Company
About
Philosophy
Trust Centre
Finscious V2
Legal
Privacy Policy
Security
Terms of Service
Delete Your Account
Grievance Officer
Support
Contact
Follow
© 2026 Finscious
support@finscious.com
Data processed in India (Mumbai region)