SECURITY
Your data, protected at every layer
LekhaBooks stores your business's financial data. Here's exactly how we protect it.
Report a vulnerabilityEncryption at rest & in transit
Sensitive fields such as PAN, bank account numbers, IFSC and one-time passwords are encrypted at rest using AES-256-GCM. Data in transit is protected with TLS 1.2 or higher (TLS 1.3 is offered). Encryption keys are kept in environment-isolated key material and rotated annually.
Role-based access control
Define exactly who can view or modify your financial data with granular, role-based permissions. Every action is logged with a full audit trail — date, time, user, and change.
Automated daily backups
Full database backups are taken at least daily and kept for 30 days, stored separately from the primary database. Our recovery point objective is 24 hours and our recovery time objective is 8 hours, as set out in our SLA.
Data stored in India — DPDP-aligned
Your primary data store and routine processing stay in India (Mumbai data centre). Limited data leaves India only for: one encrypted off-site backup copy on Google Drive, e-mail delivery routing, error monitoring (personal data removed before sending), Cloudflare edge caching, analytics on our public pages (only with your consent), and the AI, WhatsApp or sign-in features you switch on — see Section 9 of the Privacy Policy.
Payments processed by Razorpay (PCI DSS Level 1)
All payments are processed by Razorpay, a PCI DSS Level 1 certified payment gateway. You enter card, UPI or bank details in Razorpay's checkout, so LekhaBooks never sees or stores your full card number, CVV or banking credentials.
Vulnerability disclosure
Found a security issue? Email security@lekhabooks.in. We respond within 48 hours and follow responsible disclosure practices — we don't take legal action against good-faith researchers.
Questions about our security practices?
Our team is happy to answer detailed security questions for enterprise customers, due diligence reviews, or vendor assessments.