Your books are sensitive. We treat them that way.
ERPSense is built for businesses whose ledger is the whole story. Below is exactly where your data lives, who can see it, and what we do with it.
Six practices, plain-language.
Encryption
TLS 1.3 in transit. AES-256 at rest in PostgreSQL and Google Cloud Storage. Sensitive credentials (ERP API keys, OAuth tokens) are encrypted with Fernet using keys stored in Google Secret Manager.
Hosting region
All tenant data and backups live in Google Cloud asia-south1 (Mumbai). No replication outside India. Disaster-recovery snapshots stay within the same region.
Tenant isolation
Each tenant gets a logically isolated PostgreSQL schema and an isolated ERP site. Queries are scoped by tenant ID at the API gateway and re-enforced at the database layer.
Access control
Role-based access — Admin, Manager, Accountant, Operator, Viewer — with a separate Chartered Accountant role for cross-tenant advisors. All sensitive actions are logged with actor, timestamp and source IP.
Audit trail
Every ledger document change is recorded with the original value, the new value, the user who changed it, and the timestamp. Bank reconciliation sessions and Tally sync resolutions are immutable once closed.
DPDP readiness
India’s DPDP Act of 2023 compliance work is in progress. Data minimisation, retention windows, and a Subject Access Request workflow are documented in our privacy policy and operational runbooks.
Found something? Tell us.
Email security@erpsense.ai with reproduction steps. We acknowledge within 48 hours and aim to remediate critical issues within 7 days. We don’t pursue good-faith researchers.
Ready to put your books in one place?
Book a 20-minute demo. We’ll walk through your invoicing, GST and Tally setup live — no slides, no sales script.