Your data
Delete your data
Last updated: 27 October 2026 · Value Garage Private Limited · CIN U66190DL2025PTC453505
Companion to Privacy Policy §9 (retention & deletion) and
§12 (your rights).
There is little to delete. FinLens never stores your emails, and each part of the list of them it gives a business — the text of each email in it included — and each delivery of files, can be collected for 3 hours after it is ready and is then destroyed. The one thing kept longer is our access to your Gmail, for as long as your permission lasts — up to six months; a permission given before the date above keeps the twelve months it was given for. To end it and remove what is left: remove FinLens's access at Google, then write to us.
What we hold, in short. Your emails are never stored. The list of the emails our searches found — dates, senders' names, From and To addresses, subject lines, the text of each email, file names — and the delivered files, with the details that go with each, are kept encrypted: each part of the list, and each delivery, can be collected for 3 hours after it is ready, and is then deleted by a scheduled sweep, whether or not the business collected it. We hold no identity details: we never ask for them. Your Gmail access credential, and the key behind the references in the business's lists, are kept encrypted for the term of your permission — at most six months, or twelve months for a permission given before this page's date — and destroyed when the term ends, when you or the business withdraw, or when Google stops accepting the credential, whichever is first; the credential is revoked at Google too. So when you write to us, the lists and files are usually already gone, and what your request ends is the access credential.
1. Remove FinLens's access at Google
Do this first. It does not depend on us.
- Go to myaccount.google.com/permissions.
- Find FinLens in the list of apps with access to your account.
- Select it, then choose Remove access.
This takes effect at Google immediately. From then on Google refuses our copy of the credential, so nothing more can be read. It ends FinLens's access for every business you approved through that Google account. When we learn of it — at the business's next check or request, or when your permission's term ends, whichever is first — we destroy our copy and any list or files we still hold for that permission, and nothing more can be collected.
Removing access changes nothing in your mailbox. FinLens only ever has read-only access, so it cannot send, modify, label or delete your mail.
Or withdraw in the business's app
The business must give you a way to withdraw in its own app, and tell us at once when you use it. We then revoke our access at Google and destroy our copy; any list or files we still hold for that permission are deleted at once, no further check or request runs, and nothing more can be collected. This ends your permission for that business only.
If you have not approved yet
Decline on Google's screen, or leave the Gmail box unticked. Nothing is fetched, and any access Google issued on that link is handed back to Google and our copy destroyed straight away, not left for the scheduled sweep.
If you declined, or never opened the link
Nothing was read. While the link is valid you can try again from the page you were shown; otherwise nothing more happens. There is nothing for you to do.
2. Ask us to delete what we hold
- Email privacy@finlenstech.com.
- Use the subject line Delete my data.
- Tell us the name of the business that asked you for documents.
- Tell us roughly when you approved on Google's screen.
A request to delete also ends your permission: we revoke our access at Google and destroy our copy, any list or files we still hold for it are deleted at once, and no further check or request runs.
We ask for the business, not your email address, because we do not keep your email address: it is kept only in the From and To lines of the lists we give the business, and in the From address that goes with a file fetched from an email you sent — both deleted within three hours — and a request is filed under the business's own reference for you. So we find your permission with the business's help, and a request that names no business may be one we cannot locate. If so, we will tell you, rather than report a deletion we did not perform.
There is no deletion portal or button, no FinLens account and no automated flow: deletion is a request to this address, read by a person. The self-serve step is §1, at Google.
3. What gets deleted
The system does this on a schedule, without being asked. The names in brackets are the ones a deletion receipt uses.
| What | When it goes |
|---|---|
| Your email itself — its Cc and Bcc lines, any other part not in the list, any email our searches did not find — and any file the business did not ask for | Never stored. Each message's headers, text and list of files pass through memory while it is read; what the list carries is written only into the encrypted list, and a file the business did not ask for is never fetched |
| The list of the emails our searches found that we gave the business — dates, senders' names, From and To addresses, subject lines, the text of each email, Gmail's results on each sender, conversation references, file names, types and sizes | At most 3 hours after each part of it is ready, encrypted until then, then hard-deleted — whether or not the business collected it, and at once if your permission ends first |
| The files we delivered, exactly as they were attached, with the details that go with each (artifact) | At most 3 hours after each delivery is ready, encrypted until then, then hard-deleted — whether or not the business collected them, and at once if your permission ends first |
| The key that lets the business's references fetch files | Kept, encrypted, for the term of your permission, and destroyed when it ends, for any reason — a deletion request included. Every reference then stops working |
| Your Gmail access credential (oauth_grant) | Kept, encrypted, for the term of your permission — at most six months, or twelve months for a permission given before this page's date. Revoked at Google and destroyed when the term ends, when you or the business withdraw, when you ask us to delete, or when Google stops accepting it, whichever is first. If a fault stopped us recording your approval, one hour after you approved at Google |
| Your email address | Only where it appears in the From and To lines of a list, gone with the list, and in the From address kept with a file fetched from an email you sent, gone with the file — each at most 3 hours after it is ready, both encrypted until then. Stored nowhere else |
Deletion is verified, not assumed. Every purge writes a receipt naming the request, when it happened, how many files went, and which of artifact, oauth_grant were destroyed. Ask us for it in writing.
4. What we keep, and why
One thing survives deletion for good, and it holds none of your content: an append-only, hash-chained ledger of what was done.
Its entries record that consent was granted or refused (each refusal numbered), that access was sealed and later destroyed, that a check started, finished or failed, that files were delivered and later purged, and that your permission ended, and why. They contain no email or file content. Most hold only event names, timestamps, counts and outcome codes. The entry recording an approval also holds what was agreed — the business that receives the files, how long the permission lasts and the version of the disclosure shown, and, for permission given before the Privacy Policy's current version, the document types and any institution the business named — against a pseudonymous reference, never your name or email address (Privacy Policy §4.5). A field that would carry mail content or a credential is dropped, not stored.
Each entry is chained to the one before it, so removing or editing one breaks the chain at a point an auditor can find. That is why it is kept: it lets someone other than us check that the deletions above really happened.
A purged request also keeps its counts — how many emails were listed and how many files were delivered — so the business can tell "your files expired" from "nothing was there". The counts carry no email or file content.
Nothing kept for everyone. Until the Privacy Policy's current version, we also kept counts of organisation domains found in email, with an AI model's label for each, and counts of password-protected statements by institution. They are deleted (Privacy Policy §4.7), and no backup holds them once the backups made before then are gone, within eight days.
For at most eight days, our nightly backups. Each night we make an encrypted backup of our database, stored in India (Google Cloud, Mumbai), and each is permanently deleted within eight days of being made. Until it is deleted, a backup made before your request may still hold your encrypted Gmail access credential (by then revoked at Google), the key for the business's references, and the records described above. It never holds the list of your emails or a file. A backup is used only to restore the service after a failure, and if we ever restore one, we apply your deletion again before the service runs (Privacy Policy §9.1).
Where a law or a regulator requires us to keep something longer, we will tell you what and why.
5. What we cannot delete for you
Lists and files already delivered to the business you approved are in that business's systems, under its own privacy policy and retention rules. Deleting our copy does not delete theirs, and withdrawing cannot recall a list or a file already delivered — though our terms with the business require it to delete the list when your permission ends. To have their copy deleted, ask that business directly.
- We have no way to notify a business of your deletion request.
- Your mailbox is untouched either way: deleting data at FinLens deletes nothing from Gmail.
6. What does not exist
- No self-serve deletion portal. There is no FinLens account and nothing to log into.
- No delete button and no automated request flow. Deletion is a request to the address in §2.
- No data export and no consent dashboard.
- No endpoint that serves a deletion receipt. Receipts are written to the ledger in §4; ask us for yours.
- No record of you if no business asked. A request exists only because a business created one for you.
- No long-term store of your files or of a list of your email. What is kept longer is our access to your Gmail, for the term of your permission, and §1 and §2 end it.
What we have and have not built is also listed on our Trust page.
7. When each of these happens
| Step | When |
|---|---|
| Access removed at Google | Immediately, and it does not depend on us |
| Withdrawing in the business's app | No further check or request runs; the credential is revoked at Google and destroyed, any list or files not yet collected are deleted at once, and the business's references stop working |
| Declining on Google's screen, or leaving the Gmail box unticked | Nothing is read; any access issued on the link is handed back to Google and destroyed straight away |
| The list of the emails our searches found, with the text of each | Gone at most 3 hours after each part of it is ready, on a scheduled sweep |
| The files, with the details that go with each | Gone at most 3 hours after each delivery is ready, on a scheduled sweep |
| Our access to your Gmail, if nothing ends it sooner | Revoked at Google and destroyed when your permission's term ends — at most six months after you approved, or twelve months for a permission given before this page's date |
| Our encrypted nightly backups | Each deleted within 8 days of being made, so whatever one held of yours is gone at most 8 days after your request (§4) |
| Your written request to us | Acknowledged, then answered within the time the DPDP Act allows |
| Written confirmation of what was held and what was destroyed | Sent when we answer |
8. Grievances & your rights under the DPDP Act
India's Digital Personal Data Protection Act, 2023 lets you:
- ask what we hold about you and what we did with it;
- ask us to correct what we hold about you;
- ask us to destroy what we hold — this page is the route;
- raise a grievance with the officer below;
- nominate someone to exercise these rights for you.
Privacy Policy §12 sets them out in full. If a grievance is not resolved, you can complain to the Data Protection Board of India, whatever we say here.
Grievance officer (DPDP) · Suraj Agarwalla — privacy@finlenstech.com
Privacy questions · privacy@finlenstech.com
Security reports · security@finlenstech.com
Value Garage Private Limited · CIN U66190DL2025PTC453505
Registered office: Flat no. 26, Vandana Apartment, East Delhi, Delhi, India — 110092