1. Who we are
Dharma Poshanam Inc ("we", "our") operates Vitta Fin. Vitta Fin keeps account books, ledgers and statutory records for organisations — trusts, societies, companies and small businesses in India and the United States.
Vitta Fin is used by an organisation, not by a consumer. Most of the data in it belongs to that organisation rather than to you personally, and your rights over it are described in section 8.
2. What we collect
Account information
- Email address — used to sign in and to reach you about your account
- Phone number — only if you choose to sign in by one-time password
- Your name, and which organisation you belong to
The organisation's records
- Accounts, transactions, vouchers and ledgers you enter
- Invoices, quotations, payment advices and the customers they name
- Donors and donation receipts, where the organisation records them
- Registration details the organisation supplies — PAN, TAN, GSTIN, 12A and 80G numbers in India; EIN and 501(c)(3) details in the United States
- Documents the organisation uploads, such as audit reports and returns
Technical information
- Device type and operating system version
- Error reports when something fails, so we can fix it
- The app version and platform you were on, when you report an issue to us
Cheque images
- Photographs of cheques you scan — taken with the camera, chosen from your gallery, or imported as a PDF
- The details on them — payee or payer name, amount, date, cheque number, bank and branch
Nothing is recorded from a scan until you confirm it. Whatever is read is shown to you as a draft: you check every field, correct anything misread, and link the cheque to a payer or payee yourself. Fields that could not be read are left empty rather than guessed at.
The image goes to our own reading service and nowhere else. It is not sent to any third party or to any AI vendor. The model that reads it runs on a machine we own and operate, not on anyone's API, and it is never used to train anything.
The images of financial instruments and records are
processed by our systems in India and other parts of the
world; after ingesting the data, the images are
discarded. However, the images can be stored on
Google Cloud, on our Mumbai server, if the customer wishes.
That choice is the "keep the cheque photo" switch: with it
on, the image is saved in Google Cloud Storage in Mumbai —
in India — against your transaction. The machine that reads
it keeps no copy either way.
You decide whether the photo is kept. The scan screen carries a "keep the cheque photo with this entry" switch. With it on, the image is stored with the transaction as its supporting document, in Google Cloud Storage in Mumbai. With it off, the image is discarded once the details are recorded and only the figures you confirmed remain.
Automatic reading is a setting we control, and it is not switched on everywhere. Where it is off, the scan screen says so plainly and you enter the details yourself — the photo and the "keep" choice work the same either way.
| Permission | Why |
|---|---|
INTERNET, ACCESS_NETWORK_STATE | To reach the service at all |
CAMERA | To photograph a cheque, only when you open the scanner |
| Photo library access | To let you pick a cheque image or PDF you already have |
RECORD_AUDIO (microphone), speech recognition | To let you speak a question to Jalpa, the in-app assistant, only when you tap its mic. Your phone's own speech service turns the words into text; no sound is recorded or sent to us, only the text you then send. |
It asks for nothing else — no contacts, no calendar, no location — and it reads nothing from your device beyond the image you choose, the words you speak to Jalpa and the figures you type.
A previous version of this policy said the app did not use the camera at all. That was written while cheque scanning was out of scope, and it is corrected here rather than quietly amended.
3. Why we hold it
| Purpose | What it covers |
|---|---|
| Signing you in | Verifying who you are and keeping your session |
| Running the product | Keeping the books, producing reports, issuing invoices and receipts |
| Statutory obligation | Books of account must be retained; see section 6 |
| Support | Answering what you report, and telling you when it is fixed |
| Billing | Taking and recording subscription payments |
We do not sell your data. We do not share it with anyone for advertising, and we do not use it to profile you.
4. Who else processes it
| Service | What it does |
|---|---|
| Firebase (Google) | Sign-in. Your password is held by Google and never by us. |
| Google Cloud SQL (Mumbai) | The PostgreSQL database holding the organisation's records |
| Google Cloud | Runs the service, and stores uploaded documents and backups |
| Razorpay (India) | Takes subscription payments. Card details go to Razorpay and never reach us. |
| Stripe (United States) | Takes subscription payments. Card details go to Stripe and never reach us. |
5. How it is protected
- Everything travels over HTTPS
- Each organisation's records are isolated in the database itself, by row-level security, so one organisation's queries cannot reach another's rows
- Sign-in tokens are kept in the device's secure storage — Keychain on iOS, encrypted storage on Android
- Access within an organisation is limited by the role it gives you
6. How long we keep it
- Books of account and statutory records: kept for at least the period the law requires of the organisation — in India, the Income-tax Act and the Companies Act generally require books to be preserved for several years after the relevant assessment year. We retain them for ten years.
- Account information: kept while the account is open
- Error reports: kept up to twelve months
If a subscription lapses, the organisation's records are suspended rather than deleted, so nothing is lost while billing is sorted out.
7. Where it is held
The service, the database that holds the organisation's books, uploaded documents and backups all run in Google Cloud's Mumbai region (asia-south1), in India. Data belonging to United States organisations is kept separate from Indian organisations' data throughout the product; an organisation belongs to one jurisdiction and its records never mix with the other's.
Images of cheques and records. The images of financial instruments and records are processed by our systems in India and other parts of the world; after ingesting the data, the images are discarded. However, the images can be stored on Google Cloud, on our Mumbai server, if the customer wishes — that is the "keep the cheque photo" switch.
8. Your rights
- See it — ask for a copy of the personal data we hold about you
- Correct it — ask us to fix anything wrong
- Export it — the organisation's records can be exported to Excel from within the product at any time
- Delete it — ask for your account to be closed. Records the organisation is legally required to keep will be retained for the period in section 6, and the request should come from the organisation rather than from an individual user where the data is the organisation's.
Write to the address in section 11 and we will respond within 30 days.
9. Children
Vitta Fin is a product for organisations and is not intended for anyone under 18. We do not knowingly collect information from children.
10. Changes
When this policy changes materially we will update the date at the top and tell you in the app. This version withdrew a statement about camera and photo-library access that no longer described the software.
11. Contact
Privacy questions, or to exercise any right above:
Email: tech@dharmaposhanam.in
Company: Dharma Poshanam Inc
You can also report an issue from inside the app, without signing in, at vittabooks.in/vitta-issue.