Last updated: 13 September 2026
The short version: Finly collects nothing. It has no accounts, no servers and no network code. Everything you enter stays in a database on your own device, and uninstalling the app deletes it.
This policy covers the Finly Android application published by The C Studio. It describes how the app handles information, and it applies to everyone who installs it.
None, unless you email us. Finly does not collect, transmit, sell or share any personal information, financial information, device identifiers or usage data. The only way anything reaches us is an email you choose to send from your own mail app, described under "Contacting the developer" below.
The app contains no network client, no analytics SDK, no advertising SDK and no crash-reporting service. It does not use the Android Advertising ID. There is no account to create and no server for your information to be sent to, because no server exists.
Everything you enter is written to a local database on your device and never leaves it unless you deliberately export it. That includes:
This data is readable only by Finly, within the app's private storage area that Android isolates from other applications.
Finly offers optional at-rest encryption of its database, which you can turn on in Settings → Security. When you enable it, the app generates a 256-bit key using your device's secure random number generator and stores that key in Android's hardware-backed keystore. The key never leaves your device and is never transmitted or recoverable by us. If you do not enable encryption, the database is stored unencrypted inside the app's private storage.
You can optionally require a fingerprint, face unlock or your device passcode to open Finly. This check is performed entirely by Android. Finly receives only a yes-or-no result. It never receives, processes or stores your fingerprint, face data or passcode, and it holds no copy of any biometric information.
Finly can offer to fill in expenses from the payment alerts your bank, card or UPI app sends you. It is off until you switch it on in Settings → Transaction detection, and it works in one of two ways:
Every detected transaction waits in a review list until you confirm or dismiss it. When you confirm one, the original alert text is saved with the expense so you can see where it came from. Alert text is never uploaded, shared or sent anywhere; Finly still has no network code. Reviewed alerts are deleted after the retention period you choose, and switching the feature off stops all reading and clears anything waiting to be reviewed. You can withdraw notification access at any time in Android's settings.
Finly does not request permission to read your SMS inbox.
If Finly misreads a payment alert, you can teach it the format by tapping the amount, payee and other parts of the message. The format is saved on your device, alongside a copy of the example message with reference numbers, card digits and UPI ids scrambled.
You can choose to send a format, or a misread message, to the developer so a future update reads it for everyone. Finly opens your own mail app with the email already written and addressed; you see all of it, can edit or delete any of it, and nothing is sent unless you send it. If you do, we receive what you sent by email and use it only to improve how Finly reads payment alerts.
Settings has a "Contact the developer" screen, and detection has a "Report a detection problem" button. Both open your own mail app with an email already written and addressed to us. The screen shows everything the email will contain, each part can be switched off, and nothing is sent unless you send it from your mail app. Finly itself sends nothing.
Depending on what you leave switched on, the email can contain:
It never contains your messages, amounts, balances, account or card numbers, payee names, what you spent on, your categories, accounts, budget, or the name you gave Finly, and it carries no device or install identifier.
Finly can export your records as a CSV file and can import records from a CSV file you choose.
Finly is not directed at children and is not intended for anyone under 18. We do not knowingly collect information from children — in fact, we do not knowingly collect information from anyone, as described above.
Finly includes no third-party analytics, advertising, attribution or tracking services. No third party receives information from the app.
Google Play may independently collect information about installs, crashes and device types as part of operating the store. That collection is governed by Google's privacy policy, not by this one, and we receive only aggregate, anonymous statistics through the Play Console.
You can delete individual records inside the app at any time. To remove everything, uninstall Finly — this deletes the database and all of its contents from your device. Because no copy is held anywhere else, there is no server-side deletion request to make and nothing for us to delete on your behalf.
Your data is retained on your device for exactly as long as you keep it there. An email you choose to send us is kept only to reply to you and to improve how Finly reads payment alerts; ask us and we will delete it.
Privacy laws such as the GDPR and CCPA give you rights of access, correction, portability and erasure over personal data held by a company. We hold no personal data about you, so there is nothing for us to disclose, correct or erase. You exercise the practical equivalent directly: view and edit your records in the app, export them as CSV for portability, and uninstall to erase them.
If Finly ever adds a feature that changes how information is handled — for example an optional backup or sync service — this policy will be updated before that feature ships, and the date at the top of this page will change. Material changes will also be noted in the app's release notes on Google Play.
Questions about this policy, or anything else: srekthk1@gmail.com, or Settings → Contact the developer in the app.