Security
We are not going to tell you this software is unbreakable. What we can tell you is exactly what it does, what it refuses to do, and why the design keeps the dangerous things out of reach in the first place.
Local-first, because the safest data is data you never hold
There is no database, no user account and no server-side copy of anything you enter. Each tool is a set of static files. Your figures are computed in your browser and stay there.
This is a design decision with teeth: a product with no customer database cannot leak one. It also means we cannot recover your work for you — closing the tab really does lose it.
Things these tools will never do
- Ask for a password, an OTP or a CAPTCHA.
- Log in to any government portal, or anything else, as you.
- Submit a form or authorise a payment on your behalf.
- Ask for a card number, UPI PIN or net-banking detail.
- Upload what you type to a Maytrika server. There is no server.
- Show you an advertisement, or set a tracking cookie.
Clearing what is stored on your device
Some tools keep a draft in your browser’s own storage so a refresh does not lose your work. It never leaves the device, and you can remove all of it at any time from the privacy page.
If you find something
Tell us. A tool that handles someone’s financial details and gets it wrong is worth fixing quickly, and a quiet report is far more useful to the people who use this than a quiet exploit.