Trust
Security is an operating discipline, not a badge
Broker statements contain sensitive financial data. The production design limits network exposure, filesystem access, deployment risk, logging, and retention while preserving the backups needed to recover safely.
What you get: a complete ITR-3 working built from your broker files: your F&O and intraday turnover, worked out the way the tax audit rules ask for; the four Trading Account figures ITR-3 now asks every trader for; a balance sheet and profit-and-loss working, in ITR-3's own layout; whether a tax audit applies to you, with the numbers behind it; every figure showing the sheet, row, and label it came from — with a list of the points that need a decision. You file the return from it yourself, or hand it to your CA. ITR FNO does not e-file, sign, or carry out a tax audit.
Production controls
| Layer | Control |
|---|---|
| Transport | Caddy terminates HTTPS and redirects HTTP; the Node service listens on loopback only. |
| Process | A dedicated unprivileged system user, systemd hardening, private temporary directory, and explicit writable paths. |
| Storage | Durable application data is confined to /var/lib/itrhelper; secrets are supplied from a root-managed environment file, not the repository. |
| Deployment | Immutable timestamped releases, pre-switch build checks, an atomic current symlink, health verification, and rollback to the previous release. |
| Edge | Security headers, request-size limits, compression, and proxying only to the loopback service. |
Data minimisation
Only records needed for the requested workpaper should be uploaded. Logs should contain operational request information, not workbook contents or extracted tax figures. Uploaded material is not used to train public or third-party AI models. Access is limited to personnel and processors needed to prepare or operate the service.
Backups and deletion
Encrypted or access-restricted backups should cover durable case state, use a documented rotation, and be tested through restoration. Deleting an active copy does not instantly remove an item from every backup; it expires as rotated backups age out. Deployment releases are separate from customer data and can be rolled back without restoring uploads.
Payment and credentials
Do not send passwords, OTPs, brokerage login credentials, card details, UPI PINs, or income-tax portal credentials. ITR FNO does not need portal access to prepare a workpaper. Payment credentials are handled by the payment provider; only payment references and status should reach the application.
Reporting a vulnerability
Email security@itrfno.com with the affected URL, reproduction steps, and impact. Do not access another person's data, degrade availability, use social engineering, or publish a vulnerability before a reasonable remediation period. We will acknowledge a credible report and coordinate next steps.
Incidents
Response priorities are containment, preservation of evidence, assessment of affected data, safe recovery, and legally required customer or authority notices. No system is invulnerable, and this page describes intended production controls rather than a warranty or independent certification.
Stop assembling this by hand.
Upload your broker files and get the sourced working back within 8 business hours of complete records.