Data protection policy
The privacy policy tells you what Fincraft stores about you and why. This policy describes the rules [not set] follows to protect it — who is responsible, which safeguards are in place, and what happens if something goes wrong.
Last updated 1 November 2026
LEGAL_OPERATOR, LEGAL_ADDRESS, LEGAL_GOVERNING_LAW, LEGAL_JURISDICTION, LEGAL_CONTACT_EMAIL.
Set them in .env and the wording below completes itself.
See config/legal.php.
1. Scope and responsibility
[not set] is the controller — under India's Digital Personal Data Protection Act, 2023 the data fiduciary — for personal data held in Fincraft. This policy applies to everyone who operates the service and to every system that holds its data: the application, its database, its file storage and its backups.
Questions and requests: [not set].
2. Principles
- Purpose: data is used only to run Fincraft for the household it belongs to — never for advertising, profiling, selling or training anything.
- Minimum: we ask only for what a feature needs. Statements are read for their transactions; you choose whether to keep the file.
- Accuracy: you can correct every record on the screen where it appears.
- Retention: nothing is kept longer than the periods below.
- Security: safeguards proportionate to financial data, described below.
- Accountability: changes and access are logged, and this policy is reviewed at least once a year.
These follow the Indian DPDP Act, the UAE and Saudi Personal Data Protection Laws, the EU and UK GDPR, South Africa's POPIA and the data protection laws of Kenya, Nigeria, the Philippines, Sri Lanka and Nepal, and we apply them to every user wherever they live.
3. Financial data is treated as sensitive
Account numbers, nominee details, identity numbers (such as PAN, Aadhaar or Emirates ID if you enter them) and your own notes are encrypted in the database with a data key that is held separately from the application's signing key and from the database itself. A copy of the database alone cannot be read. Balances and transactions are protected by the household boundary and by access controls rather than being visible to anyone else.
4. Safeguards
- HTTPS for every connection; a Content-Security-Policy that blocks content from any other origin.
- Passwords hashed with bcrypt; two-factor authentication free on every plan; rate limits on sign-in, registration and password reset; sessions that expire after inactivity.
- Every household's data scoped at the query level, with automated tests on that boundary on every change; roles inside a household, with nominees and documents behind their own permissions.
- An audit trail of changes within a household.
- Fincraft runs on its own database, separate from any other service on the same servers. Production access is limited to named operators with individual credentials, and is used only to fix a fault or when you ask.
- A backup is taken before every update and every night, and encrypted at rest. One is kept for each of the last 14 nights, each of the last twelve months and each of the last 5 years, and each is checked to be restorable.
- What each role in a household may change is checked by the server on every request, and access given with an end date stops on that date.
- The secure vault is encrypted throughout, and items marked end-to-end are encrypted in the user's browser with a passphrase we never receive.
- Uploaded statements and documents are stored privately, never at a public address.
- Software and server packages are kept up to date.
5. Processors and transfers
Companies that host, back up, email or take payments for Fincraft act only on our instructions, under a written contract that requires the same protection. They are named in the privacy policy. Where data is held outside the country you live in, it is done under contractual safeguards recognised by law. No processor receives your financial records to use for its own purposes.
6. Retention and deletion
- Records are kept while the account is open.
- When a household's owner erases its data, it leaves the live service at once. It remains inside older encrypted backups until they age out on the schedule above — at most 5 years — and they are used only to recover the whole service after a disaster; anything erased since a restored backup was taken is erased again.
- A lapsed subscription's records are kept for 90 days, then deleted.
- Invoices and payment records are kept as long as tax law requires in the country of billing; they contain none of your financial records.
7. Your rights
You can export everything as JSON, correct anything on screen, read your own activity log and — as a household's owner — erase the household's data yourself, at any time. Any other request — access, correction, erasure, withdrawal of consent, or naming someone to act for you — is answered within 30 days, free of charge, once we have confirmed it is you. You may also complain to the data protection authority where you live, such as the Data Protection Board of India, the UAE Data Office or the UK Information Commissioner's Office.
8. Breaches
If personal data is lost, exposed or accessed without authority, we contain it immediately, assess the risk to the people affected and record what happened. We notify the relevant authority and the people affected without undue delay — within 72 hours of becoming aware of it where the law requires — with what we know, what we are doing and what they should do.
9. New features
Before a feature stores a new kind of personal data or uses data in a new way, its risk is assessed and protection is designed in from the start. The result is reflected in the risk assessment and, where it changes what is stored, in the privacy policy before it goes live.