Privacy Policy

Who we are

FinLens (finlens.in) is a personal finance portal operated by FinLens Financial Technology Private Limited, a company registered in India (CIN U69200BR2026PTC088990) with its registered office at Shankar Sadan Apartment, Flat No. G3, Patliputra, Phulwari, Patna 800013, Bihar, India, for people in India; access to the service is limited to India. It comes with reminders and notices on WhatsApp and by e-mail. It reads your card and bank statements, bills, transactions and investments, and shows them in one place. Access is by invitation: you ask for one on the website, and an administrator decides.

This policy explains what FinLens collects, why, who processes it, how long it is kept and how you control it. It is written to meet India's Digital Personal Data Protection Act, 2023.

Family. A member may create a family. Another member who accepts an invitation shares their name and relationship with it, and nothing else until they switch on an area (accounts, investments, credit, documents, insurance, property, tax, travel) on their own Family page; what they share is shown as figures, never as full numbers, and never as the file itself without their own PIN. A profile a member creates for a person who does not use FinLens is held under that member's responsibility: the member adds that person's statements and papers, sees everything read from them, can delete the profile with everything in it, and the profile becomes the person's own account when they first sign in with that number.

What we collect

• Sign-in details: your mobile number and your e-mail address. At sign-up the address is confirmed by a code sent to it and the number by a message on WhatsApp; after that, each sign-in sends a one-time code to the address and a WhatsApp message with two buttons, It's Me and Not Me, so you can confirm the sign-in with one tap instead of the code, or refuse it. You also choose a 6-digit sign-in PIN. We store the PIN and the codes only as hashes, never as typed; codes expire after 5 minutes. Too many wrong PINs or codes block sign-in until the administrator lifts it.
• An invitation request: the name, mobile number and e-mail address you type on the website's Request an invitation form, confirmed by a code sent to that address and by a tap on Verify Mobile Number in a WhatsApp message (an approved template) sent to that number, together with the time, your IP address, the country our network provider derives from it and your browser's name, so that an administrator can decide and reach you. The administrators see these details until the request is decided and masked afterwards. A request is sent only after both checks; one never sent is deleted after 24 hours, and if the person who uses the number taps It's Not Me, the request is kept for 30 days so that the form does not message that number again; a decided request is kept for 180 days; an accepted request's name, number and address become your account's. The acceptance is sent to that address and, as an approved template, to that number on WhatsApp; a rejection is not sent.
• Profile details you enter: name, address and a profile picture.
• Financial records: the transactions, bills, statement summaries, balances and holdings we read from your mail or from files you upload.
• Uploaded files: statement PDFs and spreadsheets you choose to upload.
• Credit reports (optional): if you upload a credit bureau report, or one arrives attached to the bureau's own mail in a Gmail account you connected, we keep its score, each account's lender, type, dates, limits and balances, and the month-by-month payment history. We read and do not keep the name, addresses, phone numbers, e-mail addresses, date of birth and ID numbers printed on it; of those we keep only how many different ones your lenders hold. Account numbers and the PAN are kept only as one-way codes that let us recognise the same account or person again. Fixed rules read a credit report first; a report they cannot read, or whose reading does not add up, is read once with AI help, as described under How we use your data. A credit score you type in yourself, or one printed in a bureau's own mail to you, is kept as the number, its bureau and its date. The band words, ratings and insights on the Credit Score page are worked out from these figures each time and are not stored.
• Income tax returns (optional): if you upload the acknowledgement of a filed return, we keep the assessment year, the form, the section and dates of filing and verification, and the figures it prints (total income, tax, interest, taxes paid, refund or amount due). We read and do not keep the name, the address, the IP address and the verification code printed on it; the PAN and the acknowledgement number are kept only as blind indexes, and the PAN is compared with the one saved in your vault. Fixed rules read a return first; one they cannot read is read once with AI help, as described under How we use your data.
• Insurance policies (optional): if you add a medical, life or term policy on the Healthcare page, we keep what you enter: the insurer, the product, the dates, the cover, the premiums, and for each insured person and nominee the name, the relationship, the gender and the year of birth. The policy number, a date of birth and a health-card member ID are stored encrypted and shown in full only after you enter your PIN; the page shows the last four characters. A policy file you add there (a PDF or a photo) is stored encrypted; a policy document or a premium statement in a print the application knows is read by fixed rules to fill in the policy. Looking at a file you stored, or saving a copy of it, asks for your PIN first (it confirms you for five minutes), and every look is recorded. A policy document the rules cannot read is read once with AI help, as described under How we use your data.
• Property (optional): if you add land, a house, a shop or a vehicle on the Property page, we keep what you enter: its name, kind, place, area, the public land-record numbers (khata, khesra, thana, jamabandi, survey), what it is worth and what it cost, when and how it was acquired, who owns what share of it (the names and relationships of family members you add), the papers you expect for it and their dates, and the files you upload for it, which are stored encrypted. A sale deed, a vehicle's registration certificate or its insurance paper is read to fill in the property's details: by fixed rules where the application knows the print, otherwise once with AI help, as described under How we use your data. A vehicle's registration, chassis and engine numbers are encrypted the same way, shown in full only after you enter your PIN.
• Personal Repository (optional): documents and records you keep on the Personal Repository page are locked in your browser, with a key made from a passphrase only you know, before they are sent. We keep only the locked copies: we cannot open them, and neither can our hosting provider. We can see that you have a repository, how many items and files it holds, their sizes and when they were added, nothing about what they are. If you forget your passphrase and lose your recovery code, nobody can open these files, including us. If you tick Read it with AI help when adding a document (it is off until you tick it, for every document), the paper's text, with your name, your family's names and every number that identifies you or them (account, PAN, Aadhaar, passport, licence, roll, registration and other numbers) replaced by placeholders, is sent once to our AI provider's model to fill in the details for you; we keep nothing of it, the reading is locked with the document in your browser, and the file itself never leaves locked. A photo or a scan has no text to mask: when you tick it for one, the picture itself (a smaller copy) or the scanned PDF goes once, as it is, to the same model, and we keep nothing of it. Leave it unticked to type the details yourself.
• Identity and account numbers (optional): PAN, PRAN, passport, licence, voter ID, UAN, the Aadhaar VID or its last 4 digits (never the full Aadhaar number), and of bank, card, folio and demat numbers the last 4 digits only, never the full number. We store these unless you withdraw that permission in Profile → Privacy & Security.
• Assistant notes: notes you may have written in Profile → Preferences before 20 September 2026. No model is given them any more; they stay until you delete them there.
• Security records: your IP address (used to check access and to limit requests) and the country our network provider derives from it (the portal can be limited to India), your active sessions, and an audit log of sign-ins, reveals, changes, consents, exports and erasures.

Gmail access

Connecting Gmail is optional. If you connect it, FinLens asks Google for read-only access (gmail.readonly) and reads only messages found by a search for the senders it knows (banks, card issuers, investment platforms, credit bureaus and, for the Travel page, travel providers: airlines, railways, bus, hotel and cab services and the agents that book them) and for transaction words in a subject line, such as debited, credited or statement; anything that is not a transaction, bill, statement or booking is set aside. Fixed rules, not AI, pick out the amount, date, merchant and similar fields. We never store the body of an e-mail. We keep only the fields we extracted, plus the sender address and subject. We never send e-mail content to any other party, and never to an AI model, with one exception you asked for: when a statement PDF attached to a mail is locked and none of the rules we hold opens it, the one or two sentences of that mail that explain the password, with every name and number masked, are shown to an AI model to learn the rule (never the rest of the mail, never the file). FinLens never sends, deletes or changes your mail.

FinLens's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. We use Gmail data only to show you your own finances. We do not use it for advertising, we do not sell it, and people do not read it except when you ask for help, when security or the law requires it, or when the data has been aggregated and anonymised.

You can stop it at any time by removing access at myaccount.google.com/permissions.

How we use your data

• To show your spending, bills, balances and investments in the portal, and your dues and notices on WhatsApp.
• To send the reminders, alerts and codes you set up, by WhatsApp or e-mail. A WhatsApp notice, for example that a card statement was detected with its amount due and due date, may be sent as a message template approved by Meta.
• To answer your questions in Ask FinLens, in the portal, unless you turn off Answer my questions in Profile → Privacy & Security. WhatsApp carries reminders and notices only and answers no typed question. FinLens works out every figure itself; an AI model reads your question to find what to look up, and may add a short note to the answer, shown as the model's own. The model receives amounts, dates, counts, category names, and the names that go with them: banks, lenders, funds, merchants, the people you pay or are paid by, and your employer. It never receives your mobile number, e-mail address or UPI ids, any account, card, folio or demat number (last four digits included), your PAN or PRAN, or the text of any mail or document. Those numbers are removed from your question before it is sent, and a message in which one is found is not sent at all. Your questions are not stored; we record only which kind of answer was given. Answers can be wrong.
• To read a file that the rules cannot read, or whose reading does not add up: a file you upload, or a statement PDF that came attached to a mail (the mail's own text is never sent). The file goes to our AI provider's model, that file alone, once. This is on for every member and every such file. Its text goes with account, card, policy, folio, PAN, PRAN, Aadhaar and mobile numbers, e-mail addresses and your own name replaced by placeholders; the model answers with the placeholders and FinLens puts the values back on its side. A photo, or a scanned PDF that has no text, is sent as it is: its numbers cannot be hidden from the model. FinLens asks the provider not to store the answer; the provider may still keep a request for a limited time to monitor abuse, unless zero data retention applies to our account. The text of a mail is never sent.
• To keep the service secure: access checks, request limits and the audit log.

We do not sell your data, show advertising or profile you for others. The cookies are the one that keeps you signed in, the trust badge's cookies on the public website (the section below) and, while you ask for an invitation, one that keeps your place in the form.

Who processes your data

• Our hosting provider runs the application, its database and file storage, the AI model that answers questions and outgoing e-mail, with everything stored encrypted (AES-256).
• Our AI provider reads an uploaded file the rules cannot read, as described above.
• Meta (WhatsApp Business Platform) delivers the WhatsApp messages you send to us and the ones we send you.
• Google provides Gmail access, only if you connect Gmail.

No one else receives your data. Other FinLens users cannot see it.

How we protect it

All traffic is encrypted, and the portal encrypts every request and reply a second time with AES-256 under a key your browser and the server agree at sign-in. Everything we store (the database, the files, the cache) is encrypted with AES-256, and every file is kept encrypted, never as a plain file. On top of that, uploaded files, identity and account numbers, and the passwords of your locked PDFs (kept so a file is read and opened without asking again) are encrypted with a key that belongs to your account alone. Numbers appear masked (•••• 1234): accounts and cards are saved with the last 4 digits of their numbers only, and a statement file you upload is kept as you sent it, encrypted under your account's key. Showing an identity number or seeing a document asks for your PIN; exporting your data or erasing your account needs a new one-time code. Numbers never appear in transactions, logs or messages.

How long we keep it

• Sign-in codes: 1 day. Sessions: until they expire or you sign out.
• Records of files we could not read (with numbers hidden): 180 days.
• Audit log: 2 years.
• Addresses that tried to open the portal from a network that is not allowed: 30 days.
• Everything else: until you delete it or erase your account.
• The database keeps a point-in-time history of the last 30 days, encrypted like the database itself; a record you delete leaves that history within 30 days. We take no other copies at present.

Your rights and choices

• See and export: download your data from Profile → Privacy & Security.
• Correct: edit your details in Profile.
• Withdraw permission: every permission is on from the day your account is made; turn any of them off in Profile → Privacy & Security. If you withdraw permission to store numbers, we delete the stored numbers.
• Delete: delete any uploaded file at any time, or erase your whole account in Profile → Privacy & Security. Erasing your account removes your records, files, stored numbers and sessions. We keep one audit entry that holds only counts.
• Complain: write to the grievance officer named below. If we do not resolve your complaint, you may contact the Data Protection Board of India.

The trust badge on the public website

The public pages of FinLens (the home page, the feature pages, the guides and these legal pages) carry a Trusted Origin badge, provided by Code Cabin, Inc., which checks the website for malware, its connection security and its e-mail protection and shows the result to visitors. When one of those pages opens, the badge's script, loaded from the provider, sends the provider the page's host name, the site you came from if it was another site, any campaign tags in the address and whether you opened the badge, and sets cookies named to_… on finlens.in so that it does not count you twice in a day. It receives nothing about an account: the badge is not on the sign-in screen or any page of the portal, and no page of the portal loads code from anyone but FinLens. The provider's own policy governs what it does with those counts.

Children

FinLens is not meant for anyone under 18, and we do not knowingly collect their data.

Changes

If we change this policy, we will update the date at the top of this page. If a change affects how we use data you have already given us, we will tell you in the app before it takes effect.

Grievance officer

A complaint about your data or about this policy goes to our grievance officer: by e-mail to privacy@finlens.in with "Grievance" in the subject, or by post to the Grievance Officer, FinLens Financial Technology Private Limited, Shankar Sadan Apartment, Flat No. G3, Patliputra, Phulwari, Patna 800013, Bihar, India. We acknowledge a complaint within 2 working days and answer it within 30 days. If you are not satisfied with the answer, you may approach the Data Protection Board of India under the Digital Personal Data Protection Act, 2023.

Contact

For questions, requests or complaints about your data, e-mail privacy@finlens.in, or write to FinLens Financial Technology Private Limited, Shankar Sadan Apartment, Flat No. G3, Patliputra, Phulwari, Patna 800013, Bihar, India.