Privacy & retention
What happens to your statement
Bank statements are among the most sensitive documents people have. This page describes exactly what the converter does with yours — not what we hope it does.
Where your file goes
| Stage | What is kept | Where | For how long |
|---|---|---|---|
| Upload & reading | Your file, a decrypted copy if it was password-protected, and page images used for OCR | A private, randomly named folder on the server (owner-only permissions) | Deleted the moment reading finishes — after success, failure, timeout or crash |
| Review | The extracted rows and small images of the lines the converter changed | Server memory only (never written to disk or a database) | Until you press Delete now, or automatically after the result expiry period shown on the results screen (30 minutes by default) |
| Download | The Excel/CSV file is built on request and sent to your browser | Not stored on the server | — |
| Password | The PDF password you type | Memory of the job only | Discarded when reading ends; never logged |
Free PDF tools
The PDF tools (merge, split, compress, rotate, JPG↔PDF, page numbers, watermark) run entirely inside your browser. Your files are never uploaded to our server or anyone else's, and we keep no record of what you process.
Your account (needed for the statement converter)
To convert bank statements, you sign in with Google or a one-time email code (handled by Amazon Cognito; this site never sees a password). We then keep, in an encrypted database in AWS Mumbai (Amazon DynamoDB):
| Data | Why | Kept until |
|---|---|---|
| Email address and name (from Google or your email sign-in) | To identify your account and page balance | You ask us to delete your account |
| Page balance and a history of credit changes (date, number of pages, type: free / purchase / conversion / refund) | So you can see what you used and paid for | Account deletion, or longer where tax law requires purchase records |
| Payment orders (order ID, pack, amount, status, PayU's payment ID) | Invoicing, refunds, GST records | As required by Indian tax law (normally 8 years) |
The history never contains a file name, bank name, account number, narration or amount from your statement. Card, UPI and bank details are entered on PayU's pages and never reach us.
What is never done
- Your statement is not sent to any third-party OCR, AI or cloud document service. All reading happens on the converter's own server.
- File names, account numbers, narrations and amounts are not written to server logs. Logs record only a random job reference, file size, page count, number of rows, duration and success or error type.
- Uploads are not stored in public storage, and results are reachable only from the browser session that created them, through an unguessable link.
- No account is needed to convert and preview. We keep no history of your documents — only the page-count history described above.
What the converter changes — and how you can tell
The converter never silently changes a figure. Each row is checked against the bank's running balance. If a figure was misread (common on scans) and the arithmetic proves what it should be, the row is marked Adjusted, the note shows what was printed and what it became, and you can see an image of the printed line. Rows that cannot be proven are marked Review. Lines the converter decided were not transactions (for example page totals) are listed on the Removed Rows sheet with the reason. Your own edits are recorded as Edited.
A running-balance tie proves amounts, Debit/Credit sides and order. It does not prove that a date or narration belongs to the right row, so please review rows marked Adjusted or Review before relying on the output.
Layout fingerprints
If a layout isn't read correctly, you can download a layout fingerprint: a file in which every letter is replaced by “a” and every digit by “9”, keeping only positions on the page. It contains no names, account numbers or amounts. It is only created when you click the link, and is downloaded to your own device — nothing is sent anywhere automatically.
Security
- Connections use HTTPS.
- Each conversion runs in its own isolated process, with time and memory limits, so one file can never see another.
- Upload size, page count and the number of conversions per hour are limited to prevent abuse.
Accuracy
The converter is rule-based and works best on statements downloaded directly from the bank. Scans and phone photos are read with OCR and may need more review. It has not been certified against every bank's format; always review the results before filing or audit use.
Operator: Accohub Technologies. Questions about this page or your data can be sent through the contact details on accohub.in.