The safest way to protect banking information is to never ask for it.
ChequeKo has no field, no form, and no database column for your credentials, your signature, or your account number.
Never asked for
- Bank usernames or passwords
- PINs or one-time passwords
- Full bank account numbers
- Signatures, stored or printed
- Payment card details
- Access to online banking
- A ChequeKo password of its own
Always done
- Enforce every permission on the server
- Keep cheque details out of logs and analytics
- Isolate your records from every other account
- Rate-limit sign-in and other abuse-prone endpoints
- Export or delete all your data on request
- End every session everywhere, on demand
The four questions people ask
Why is there no ChequeKo password?
Sign-in is delegated to Google. A password we never hold cannot leak from us.
Why can it not print my signature?
A signature is what makes a cheque yours. Storing one would make this a place worth attacking, so you sign in ink.
Why does it not print the MICR line?
Your bank pre-printed it. ChequeKo never reads it, alters it, or prints over it.
Where do calibration photos go?
Nowhere. The overlay runs in your browser, and there is no upload endpoint to send one to.
What administrators can see
Counts and dates. Never a payee, an amount or a memo. The admin queries cannot reach cheque contents, so this is structural.
Your data is yours
Export as JSON or CSV, or delete your account, from Account settings.
What we cannot promise
That your printer aligns first time. Printers vary, which is why the calibration tools exist. Test on paper first.
Your responsibility
ChequeKo is a formatting and printing tool. Users remain responsible for verifying cheque details, maintaining sufficient funds, protecting physical cheque leaves, manually signing the cheque, and following the requirements of their issuing bank.