Privacy Policy
Effective 20 June 2026 · Last updated 15 November 2026 · See changelog
This Privacy Policy ("Policy") describes how Lekha Logic Consulting Private Limited (CIN U69200DL2026PTC465960), the company that operates the "LekhaBooks" product and brand ("LekhaBooks", "we", "us", or "our"), collects, uses, discloses, retains, and protects personal data when you visit our website at lekhabooks.in, sign up for an account, or use the LekhaBooks web application, mobile applications, APIs, browser extensions, partner panels, or any related service we operate (collectively, the "Service").
This Policy is published in compliance with the Digital Personal Data Protection Act, 2023 ("DPDP Act"), the Digital Personal Data Protection Rules, 2025 ("DPDP Rules"), the Information Technology Act, 2000 ("IT Act"), the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 ("SPDI Rules"), and other applicable Indian laws. Most duties under the DPDP Act and the DPDP Rules apply from the dates the Central Government has notified (for most of them, 18 months after the Rules were published in November 2025); we follow them already, and until then the SPDI Rules also apply to us. Under the DPDP Act, we are the Data Fiduciary for personal data we collect directly from you (as a user of the Service). For business data that you upload about your customers, vendors, or employees, we act as a Data Processor on your behalf, and you are the Data Fiduciary for that data.
This Policy explains how we handle personal data. Using the Service does not by itself mean you consent to optional processing: we ask separately, in clear choices, for optional things such as marketing e-mail, AI features and analytics cookies, and you can withdraw consent at any time.
- Who we are & how to reach us
- Scope & definitions
- Information we collect
- How we use your data
- Legal basis for processing
- When we share data
- Third-party processors
- AI features & opt-in consent
- Cross-border data transfers
- Data retention
- Your rights as a Data Principal
- How to exercise your rights
- Security & safeguards
- Cookies & similar technologies
- Children & minors
- Breach notification
- Grievance Officer & DPB
- Changes to this Policy
- Contact
1. Who we are & how to reach us
Lekha Logic Consulting Private Limited (CIN U69200DL2026PTC465960) is a private limited company incorporated under the Companies Act, 2013, with its registered office at Rzd-1/101, Gali No. 5, Mahavir Enclave, Palam Village, New Delhi 110045, India. "LekhaBooks" is a product and trademark of Lekha Logic Consulting Private Limited. We offer cloud-based bookkeeping, GST compliance, TDS, payroll, inventory, and management-information software to micro, small, and medium businesses in India.
General contact
Email: support@lekhabooks.in
Privacy questions: privacy@lekhabooks.in
Grievance Officer: grievance@lekhabooks.in, +91 77107 71301
Postal: Rzd-1/101, Gali No. 5, Mahavir Enclave, Palam Village, New Delhi 110045, India.
2. Scope & definitions
This Policy applies to all personal data we collect through the Service, including from website visitors, free-tier users, paying subscribers, partner accounting practices, employees of our customers using sub-user logins, and individuals whose personal data is uploaded by our subscribers as part of their books of account (such as customers, vendors, or employees of the subscribing business).
2.1 Terms used in this Policy
- Data Principal means the natural person to whom personal data relates (you).
- Data Fiduciary means the entity that determines the purpose and means of processing of personal data. We are the Data Fiduciary for your account data; you are the Data Fiduciary for the books-of-account data you upload about third parties.
- Data Processor means an entity that processes personal data on behalf of a Data Fiduciary. We act as Processor for your tenant data.
- Personal data means any data about an individual who is identifiable by or in relation to such data.
- Processing means any operation performed on personal data, including collection, recording, organisation, storage, retrieval, use, disclosure, or erasure.
- Service means all software, websites, APIs, and applications operated by Lekha Logic Consulting Private Limited under the LekhaBooks brand.
3. Information we collect
3.1 Information you provide directly
Account & business profile. Full name, email address, mobile number, password (stored as a one-way bcrypt hash; we cannot read it). Business legal name, trade name, GSTIN, PAN, business type, date of incorporation, place of business, state, PIN code. Authorised signatory name and designation, signatory contact details, photograph or digital signature image (if you upload one). Industry / sector classification you select during onboarding.
Customer, vendor, and employee master data you upload. Customer or vendor names, addresses, GSTIN, PAN, mobile numbers, email addresses, contact persons, place of supply, opening balance. Bank account number, IFSC, UPI ID — only where you choose to record these. Employee names, employee codes, PAN, Aadhaar (last 4 digits only, where law permits), salary structure, UAN, ESIC, date of joining, if you use the optional Payroll module.
Transactional & books-of-account data. Sales/purchase invoices, credit/debit notes, payments, receipts, journal vouchers, contra entries; inventory items, batches, serial numbers; bank statements, payment-gateway settlements, e-way bills, e-invoice IRNs, GSTR returns drafts; documents you attach to vouchers.
Billing & payment data for our subscription. Billing name, billing GSTIN, billing address; the Razorpay order ID and payment ID of each payment (we do not store a saved payment method or a payment mandate). We do not store full card numbers, CVV, UPI PIN, or net-banking credentials — these are handled and tokenised entirely by Razorpay in their PCI-DSS environment. Invoice number, plan name, billing cycle, amount paid, GST charged, transaction id.
Communications & support. Support tickets, chat transcripts, screenshots you share, voice recordings if you opt into a call-back; survey responses, NPS ratings, feature requests; email content when you write to us.
GST portal credentials. Where you use GST fetch, e-invoice, e-way bill or direct filing, we ask for your GST portal username and the one-time password (OTP) needed to act for you. The portal username is stored so you do not have to type it again; the session tokens we receive from the GST portal are stored encrypted and expire with the portal session; we do not store your GST portal password or the OTP. We use them only to run the action you start.
Sensitive personal data. Under the SPDI Rules, passwords and financial information (such as bank account details you record, and payment details) are "sensitive personal data or information". We collect them only for the purposes in Section 4, with the consent you give when you sign up or when you enter them; we keep passwords only as one-way hashes, and card, UPI and net-banking details are handled by Razorpay, not by us. You may choose not to give optional information.
3.2 Information collected automatically
Device, network, & usage data. IP address (kept in our security and access logs; our own product analytics does not store it), approximate city-level location derived from IP; browser user-agent, OS, device type, screen size, language; pages visited, features clicked, time spent, error events, crash reports, request latency; referrer URL.
Cookies & local storage. An LL_SESS session cookie (HttpOnly, Secure, SameSite=Lax); a dpdp_csrf anti-CSRF token cookie on the privacy and consent screens; a short-lived lb_so cookie that tells the sign-in page why you were signed out; an lb_consent cookie and browser storage entry that remember your cookie choice; Google Analytics cookies (_ga, _ga_Z6VNW411SW, and possibly _gid) on our public web pages only after you accept optional analytics; browser localStorage / sessionStorage entries holding UI preferences; no third-party advertising cookies; no cross-site retargeting pixels. See Section 14.
3.3 Information from third parties
If you sign in via OAuth (Google), we receive your verified email, name, and Google profile picture — only the minimum scopes required to authenticate. If you connect a bank account via an aggregator API, we receive transaction lines (date, amount, narration, balance) but not your net-banking credentials.
3.4 Information about your customers, vendors, and employees
Important. When you upload data about third parties, you are the Data Fiduciary under the DPDP Act with respect to that data. You represent and warrant that you have obtained any consents required by law to share that data with us and to have us process it on your behalf for the purposes of running your books of account. We process that data only as instructed by you in your use of the Service.
4. How we use your data
We use personal data for the following specified, lawful purposes:
| Purpose | Examples | Categories used |
|---|---|---|
| Provide the Service | Authenticate logins; render dashboards; create invoices; compute GST/TDS; generate reports; back-up and restore your data. | Account profile, books data, device data. |
| Compliance & tax | Generate GSTR-1/3B/9, TDS Forms 26Q/24Q, AOC-4, MGT-7 templates; maintain audit trail under Companies Act Rule 3. | Books data, account profile. |
| Billing & collections | Charge subscription fees; raise GST tax invoices; manage renewals, dunning, refunds. | Billing data, account profile. |
| Customer support | Reply to tickets; debug your issue; train support staff (with PII redacted). | Communications, account profile, limited books data. |
| Service improvement | Identify slow pages; prioritise features; A/B test UI; produce aggregated, anonymised analytics. | Usage data, device data. |
| Security & fraud prevention | Detect brute-force logins; rate-limit abusive IPs; investigate suspicious activity. | Device data, audit logs. |
| Legal & regulatory | Respond to lawful requests; preserve evidence under court order; meet tax-record retention. | All categories as required. |
| Marketing (with consent) | Send product-update emails; invite to webinars. You can unsubscribe at any time. | Email, name, plan tier. |
We do not engage in automated decision-making that produces legal or similarly significant effects about you without human review.
5. Legal basis for processing
The DPDP Act allows personal data to be processed on two grounds only: your consent (Section 6) or a legitimate use (Section 7). We rely on them as follows:
- Consent to run your account (Section 6) — when you sign up and accept this Policy, you consent to the processing needed to provide the Service you asked for: creating your account, sign-in, invoicing and accounting, support, billing and keeping the Service secure (the purposes in Section 4 other than marketing and the optional features below). We keep a record of this consent. You can withdraw it by closing your account; records the law requires us to keep are then handled as described in Section 10.
- Separate, optional consent (Section 6) — for marketing e-mail, AI features and analytics cookies. Each one is asked for separately, stays off until you switch it on, can be withdrawn at any time as easily as it was given, and withdrawal does not affect processing already done.
- Legitimate uses (Section 7) — where you give us personal data voluntarily for a specific purpose and have not told us you do not consent to its use (Section 7(a)), for example when you write to support or book a demo; and where we must process or disclose data to meet a legal duty to disclose information to the State, or to comply with a judgment, decree or order (Section 7(d) and 7(e)).
- Records the law requires us to keep — we keep data that a law requires us to keep (such as tax records) even after consent is withdrawn, as Section 8(7) of the DPDP Act allows, and only for as long as that law requires (Section 10).
- Your business data — for books data about your customers, vendors and employees we are your Data Processor and process it only on your instructions; you, as Data Fiduciary, are responsible for having a lawful ground for that data.
Keeping the Service secure, including keeping security logs, is part of providing the Service you asked for and is also our duty under Section 8(5) of the DPDP Act and Rule 6 of the DPDP Rules, 2025.
6. When we share data
We do not sell, rent, or trade your personal data. We disclose personal data only in the limited circumstances below:
- Service providers ("Sub-processors") — trusted vendors who process data on our written instructions under a Data Processing Agreement, listed in Section 7.
- Your authorised users — sub-user accounts you invite, partner accountants you grant access to, or integrations you enable. You control these access grants.
- Legal & regulatory — when required by law, regulation, court order, or a valid request from a government authority acting within its jurisdiction. We resist over-broad requests and notify affected users where lawfully permitted.
- Corporate transactions — in connection with a merger, acquisition, financing, or sale of assets, subject to confidentiality and continuity of this Policy.
- Aggregated or de-identified data — data that cannot reasonably be linked back to you.
- With your consent — in any other case, only with your explicit consent.
7. Third-party processors
The current list of sub-processors who may receive personal data on our behalf:
| Sub-processor | Purpose | Data shared | Location |
|---|---|---|---|
| MilesWeb (Mumbai data centre, India) | Hosting & storage | All Service data at rest | India (Mumbai) |
| Google LLC (Google Drive) - off-site backup copy | Disaster recovery: one encrypted copy of the daily backup | The whole daily backup, encrypted with our own key (GPG) on our server before it is sent, so Google cannot read it | Google data centres (may be outside India) |
| Razorpay Software Pvt Ltd | Payment processing for our subscription fees | Billing name, email, amount, and the order ID and payment ID of each payment | India (Bengaluru) |
| LekhaBooks own mail server (mail.lekhabooks.in, on our MilesWeb hosting) | Transactional email delivery | Recipient email, message content | India (Mumbai); then the recipient's own mail provider |
| MSG91 (SMS) and Gupshup (WhatsApp), only if you connect them with your own account | SMS and WhatsApp messages you choose to send (for example invoices and payment reminders) | Recipient mobile number, message content, delivery status | India |
| Meta Platforms (WhatsApp Business Platform), directly through the WhatsApp Cloud API or through Gupshup, only if you connect it; and when you chat with our support on WhatsApp | WhatsApp messages and chat support | Mobile number, message content, delivery status | USA / global |
| Cloudflare | CDN, WAF, DDoS protection; cookie-less Web Analytics on our public website | HTTP request metadata, IP address | Global edge (India POPs preferred) |
| Sentry (Functional Software, Inc.) | Application-error monitoring | Error details and stack traces only (no request data, no user or business IDs); e-mail addresses, mobile numbers, PAN, GSTIN and long numbers are removed on our server before sending | USA |
| Anthropic, OpenAI, Google (Gemini) or xAI (Grok) - only the one provider LekhaBooks has switched on, and only for tenants whose Owner has given AI consent | AI features (opt-in only) — see Section 8 | Only the specific text or document content you submit to AI features after granting consent | USA |
| Sarvam AI - only for tenants whose Owner has given AI consent | Voice input (speech to text), opt-in only — see Section 8 | The audio clip you record for voice input | India |
| DeepSeek - blocked by default in our code; used only under the conditions in Section 8 | AI features (opt-in only) — see Section 8 | Only the specific text you submit to AI features after granting a separate consent | China (People's Republic of China) |
| Google LLC (Sign in with Google), only if you choose it | Signing in with your Google account | Google sends us your verified email, name and profile picture; we send Google only the sign-in request | USA / global |
| Razorpay Route / RazorpayX | Payouts (Partner Panel commissions) | Bank account, IFSC, payee name | India |
| Google LLC (Google Meet) | Product demos by video call, when you book one | Name, email, call audio, video and shared screen | USA / global |
| RBI-licensed Account Aggregator (Finvu, OneMoney or Anumati) and, where used, the technology service provider that connects us to it (such as Setu), only when you connect a bank | Import of bank transactions with your consent | Transaction lines (date, amount, narration, balance); never net-banking credentials | India |
| Outside CAs and professionals engaged by us | Performing Professional Services you buy | Only the documents and books data needed for the work | India |
| WhiteBooks (GST Suvidha Provider) | E-invoice (IRN) and e-way bill generation, only when e-invoicing / e-way bills are switched on for your business | Invoice and e-way bill details: seller and buyer GSTIN, names and addresses, item, quantity, tax and value details, transport details; for GST fetch, return preparation and filing actions you start, the GSTIN, portal username and session token | India |
| Google Analytics (Google LLC) | Website usage statistics on our public web pages, only after you accept optional analytics | Pages visited, referrer, device and browser data, approximate location derived from IP address, cookie identifiers (_ga, _ga_Z6VNW411SW, _gid) | USA / global |
| Google Fonts (Google LLC) | Web fonts on our website and app | IP address and browser details when a font file is fetched | USA / global |
| jsDelivr and cdnjs (public CDNs) | Delivery of open-source JavaScript libraries used by the app | IP address and browser details when a file is fetched | Global edge |
| Cloudflare Web Analytics | Cookie-free page-load and performance measurement, where enabled | Page URL, load timings, browser details | Global edge |
An up-to-date list is available on request at privacy@lekhabooks.in. We provide reasonable notice of material additions through our changelog and in-product banner. Receipt and document text recognition (OCR) runs in your browser with files served from our own servers; the document is not sent to any third party for OCR.
Integrations you switch on yourself. Services you connect on your own account — for example your own mail server or Gmail account for sending invoices, your own payment gateway for payment links (such as Razorpay or Cashfree), Amazon or Flipkart seller accounts, or Tally — receive data on your instruction under your own agreement with them. They are not our sub-processors, and you can disconnect them at any time.
8. AI features & opt-in consent
LekhaBooks offers optional artificial-intelligence features such as receipt OCR auto-fill, vendor-invoice extraction, narration suggestions, ledger-mapping suggestions, natural-language reporting and voice input. These features call one external Large Language Model ("LLM") provider that LekhaBooks chooses and switches on for the Service: one of Anthropic, OpenAI, Google (Gemini) or xAI (Grok), all of which process data in the USA. Voice input uses Sarvam AI (India) to turn speech into text. Before we switch on any AI provider that is not named in Section 7, we will add it there first. The AI consent screen always shows the name of the provider in use and the country where it processes data.
AI processing is OFF by default for every tenant. To enable AI features, a tenant Owner must visit Settings → Privacy & AI and explicitly toggle the flag on. By doing so the Owner represents that the tenant has obtained any consents required from third-party data subjects whose data may be transmitted through AI features.
When AI features are enabled: only the specific text, document content or voice clip you submit is sent to the AI provider (your full books are not sent); LekhaBooks does not train AI models on your data, and we use the providers' API terms under which inputs are not used to train their general-purpose models (zero-retention mode where available); you may revoke consent at any time from the same setting. We never use your data to train any model, ours or anyone else's.
DeepSeek (China): DeepSeek's servers are in China (People's Republic of China). Our code blocks DeepSeek, and any other China-hosted AI service, by default. We would use DeepSeek only after signing a data-processing agreement with it, updating this Policy, and showing the Owner a separate notice that submitted text will be processed on servers in China and may be retained there under DeepSeek's own terms; that consent would be separate from the general AI consent and could be withdrawn at any time by switching AI off. We have no such agreement today, so no text is sent to DeepSeek. If you do not want any data to leave India for AI processing, keep AI features switched off (the default).
9. Cross-border data transfers
Your primary data store, our own backups, and all routine processing remain in India, hosted in our hosting provider MilesWeb's Mumbai (India) data centre. Limited transfers outside India may occur for: one off-site copy of the daily backup, encrypted with our own key on our server before it leaves India and stored in Google Drive (Google LLC) for 30 days, so that the Service can be restored if the Mumbai data centre is lost; AI features (opt-in; Anthropic, OpenAI, Google (Gemini) or xAI (Grok), USA; DeepSeek, China, only under the conditions in Section 8); WhatsApp messages through Meta, if you connect WhatsApp; Sign in with Google and Google Meet demos, if you use them; Google Analytics on our public web pages, only with your consent; email delivery routing; error monitoring (Sentry, USA; personal data removed on our server before sending); and Cloudflare edge caching of request metadata. For each cross-border transfer we send only what is necessary, we check that the destination country is not restricted by the Central Government under Section 16 of the DPDP Act, and we use each provider under its written terms of service and data-processing terms, which form our contract with it. We have not negotiated a separate, custom agreement with every provider, and we have none with DeepSeek, which is why DeepSeek stays blocked.
10. Data retention
| Category | Retention period | Basis |
|---|---|---|
| Active books of account, invoices, vouchers | While the account is active; after you delete the account, kept on your instruction (access-restricted) until the end of the 8th financial year after the financial year of the latest entry, or longer under a legal hold, then permanently deleted | Section 36 CGST Act and Rules 56-57, Section 128 Companies Act 2013, Income-tax Act (see Account deletion and legal record retention) |
| Tax-invoice records issued to you for our subscription | 8 financial years | Section 36 CGST Act and Rule 56 (72 months from the due date of the annual return) and Section 128(5) Companies Act, 2013 (8 financial years) |
| Account profile, login credentials | While active; deleted within 30 days of account closure or verified erasure request | Account administration; subject to the deletion schedule below |
| Support tickets, chat transcripts | 3 years from closure | Quality assurance, dispute resolution |
| Marketing emails & consent records | Until consent withdrawn + 1 year (proof of consent) | DPDP Section 6 |
| Security log (sign-ins, access and administrator actions) | At least 12 months; currently kept for 2 years online, then moved to an access-restricted archive and deleted 8 years after the entry | Rules 6(1)(e) and 8(3), DPDP Rules 2025 — detection, investigation & remediation of unauthorised access; CERT-In Directions 2022 (at least 180 days, in India) |
| Server access logs | At least 12 months, kept in India | Rule 6(1)(e), DPDP Rules 2025; CERT-In Directions 2022 (at least 180 days, in India) |
| Audit trail of changes to your books (who changed what, and when) | 8 years, like the books themselves | Rule 3(1), Companies (Accounts) Rules, 2014 and Section 128(5), Companies Act, 2013 |
| Failed-login / authentication-event logs | 12 months (1 year) | Rule 6(1)(e), DPDP Rules 2025 — brute-force detection & investigation |
| Transient IP rate-limit counters | 30 days | Operational throttling only (not a breach-detection log) |
| Daily backups | Up to 30 days rolling (our own daily database backup is kept for 14 days; the encrypted off-site copy in Google Drive for 30 days); erased or anonymised profile, login and contact details drop out of backups as they rotate (within 30 days); books kept on your instruction stay in backups only while they are retained | Disaster recovery |
| Anonymised product analytics | Indefinite | Product improvement, no re-identification possible |
Account deletion and legal record retention. When you delete your account we immediately end all sessions, disable sign-in, and erase or anonymise your profile, login and contact details (within 30 days, including from active backups as they rotate out). Your books of account, invoices and vouchers are records that you, as the registered person, must keep under law (for example Section 36 of the CGST Act and Rules 56-57, Section 128 of the Companies Act, 2013 and the Income-tax Act). Unless you instruct us otherwise after exporting your data, we keep these records on your behalf, access-restricted and not used for any other purpose, until the end of the eighth financial year after the financial year of your latest entry (this covers 72 months from the due date of the annual GST return for that year and the 8 financial years required of companies), or longer if a legal hold, assessment, appeal or investigation is pending, and then permanently delete them. We issue a deletion certificate. Security logs are kept for at least one year (DPDP Rules 6(1)(e) and 8(3)), and in India for at least 180 days as CERT-In requires; the audit trail of changes to your books is kept as long as the books. You remain responsible for producing your records to tax authorities; please download a full export before deleting.
11. Your rights as a Data Principal
Under Sections 11 to 14 of the DPDP Act you have the following rights:
- Right to access information about personal data (Sec. 11) — a summary of the personal data being processed, the activities of processing, and the identities of all sub-processors with whom your data has been shared.
- Right to correction & erasure (Sec. 12) — correction of inaccurate or misleading data; completion of incomplete data; updating; and erasure unless retention is required by law or contract performance.
- Right of grievance redressal (Sec. 13) — a readily-available means to raise grievances, with response within the period stated in Section 12 below.
- Right to nominate (Sec. 14) — nominate another individual to exercise your rights in the event of your death or incapacity.
- Right to data portability — export your books in JSON, CSV, Excel, or Tally XML formats from Settings → Data & Backup, at any time, without charge.
- Right to withdraw consent — for any processing based on consent (marketing, AI features, optional analytics). Withdrawal is as easy as giving consent and does not affect lawfulness of processing already done. If you withdraw the consent needed to run your account, we may not be able to keep providing the Service.
12. How to exercise your rights
The fastest path is to use the in-app tools at Settings:
- Access & portability — use "Download Backup (export all my data)" in Settings → Data & Backup.
- Correction — edit your profile and master records directly.
- Erasure — use "Delete my account" in Settings → Data & Backup. We delete on the schedule described in Section 10.
- Consent management — AI features are managed at Settings → Privacy & AI; marketing and analytics consent at Settings → Privacy & Data Rights.
- Nomination — name a person to exercise your rights if you die or become unable to act, at Settings → Privacy & Data Rights → Nominee (nominee page), or by writing to us.
If you cannot or do not wish to use the in-app tools, write to privacy@lekhabooks.in from the email address registered with your account. We respond within 30 days. There is no fee for exercising your rights. If we cannot identify you, we may ask for additional verifying information before acting, to prevent unauthorised disclosure.
13. Security & safeguards
We follow reasonable security practices and procedures as required under Section 8(5) of the DPDP Act, Rule 6 of the DPDP Rules 2025, and Rule 8 of the SPDI Rules. Our technical and organisational measures include:
- Transport-layer encryption (TLS 1.2 or higher) for all data in transit; HSTS enabled.
- Passwords stored only as bcrypt hashes with per-user salts; we cannot read your password.
- AES-256-GCM encryption at rest for sensitive PII fields including PAN, bank account number and IFSC; one-time passwords are stored only as one-way hashes. Encryption keys are kept outside the database, with a procedure to rotate them.
- Optional two-factor authentication for all accounts, including partner users; mandatory for our internal administrators.
- Role-based access control with least-privilege defaults; granular voucher-level permissions.
- Application-layer logging of all create/update/delete operations with user attribution, IP, and timestamp (audit trail per Companies Act Rule 3).
- Security and access logs are retained for at least 12 months (the audit trail of your books for 8 years), in line with Rule 6(1)(e) of the DPDP Rules 2025, to support detection, investigation and remediation of unauthorised access.
- Rate-limiting and brute-force protections on login, password-reset, and OTP endpoints.
- Web Application Firewall and DDoS protection at the edge.
- Regular dependency scanning and internal security reviews and testing.
- Daily database backups, stored separately from the live database and kept on a rolling basis (see Section 10); one copy is encrypted (GPG) on our server and kept off-site in Google Drive, with a size and checksum check after each upload.
- Access to live systems limited to authorised staff bound by confidentiality; written incident-response steps.
No security regime is perfect. We do not warrant absolute security; we commit to operating in line with industry best practices and to transparent breach disclosure (Section 16).
14. Cookies & similar technologies
We use the cookies necessary to operate the Service and, only with your consent, analytics cookies on our website. We do not use third-party advertising cookies, retargeting pixels, or cross-site behavioural tracking. The cookies and browser-storage entries we use are:
| Cookie | Purpose | Duration | Category |
|---|---|---|---|
LL_SESS | Sign-in session (HttpOnly, Secure, SameSite=Lax) | Until you close the browser, or up to 7 days if you tick "Stay signed in"; cleared on logout | Strictly necessary |
dpdp_csrf | Anti-CSRF token for privacy and consent requests | Session | Strictly necessary |
lb_so | Tells the sign-in page why you were signed out | 15 minutes | Strictly necessary |
lb_consent (cookie and localStorage) | Remembers your cookie / analytics choice | 180 days | Strictly necessary |
_ga | Google Analytics: distinguishes website visitors (set only after you accept analytics) | Up to 2 years | Analytics — optional |
_ga_Z6VNW411SW | Google Analytics 4: keeps session state (set only after you accept analytics) | Up to 2 years | Analytics — optional |
_gid | Google Analytics: distinguishes website visitors (set only after you accept analytics) | 24 hours | Analytics — optional |
lb_aid (sessionStorage, not a cookie) | Anonymous analytics session identifier (no PII), used only after you accept analytics | Until the browser tab is closed | Analytics — optional |
Strictly-necessary cookies do not require consent. Optional analytics cookies and storage are used only with your consent; you can withdraw it at any time from the cookie banner link on our website or at Settings → Privacy & AI in the app, and the Google Analytics cookies are then deleted.
Cloudflare Web Analytics (public website). Our public pages on lekhabooks.in load Cloudflare's Web Analytics script (static.cloudflareinsights.com/beacon.min.js), including before you make a cookie choice. It sets no cookies, uses no local storage or fingerprinting, and does not identify or track you across sites; it reports only aggregate page-load performance and visit counts (page URL, referrer, browser type and country derived from the request). We treat it as strictly necessary for keeping the website fast and available. It is not used inside the signed-in app. Cloudflare may also set a strictly necessary security cookie (such as __cf_bm) when it checks traffic for bots.
15. Children & minors
The Service is intended for use by individuals aged 18 years or above acting in connection with a registered business. We do not knowingly collect personal data from children (defined in Section 2(f) of the DPDP Act as individuals below 18 years; Section 9 governs processing of children's data). If we become aware that we have collected personal data from a child without verifiable parental consent, we will delete that data as soon as practicable. In the same way, we do not knowingly process personal data of a person with a disability who has a lawful guardian without that guardian's verifiable consent (Section 9 of the DPDP Act and Rule 11 of the DPDP Rules). If you are a parent or guardian and believe your child has provided us personal data, contact privacy@lekhabooks.in.
16. Breach notification
Your account and our own data. For personal data we hold as Data Fiduciary (account, billing, support), in the event of a personal-data breach we will, in accordance with Rule 7 of the DPDP Rules 2025: (a) intimate each affected Data Principal without delay, through your user account or registered mode of communication, describing the nature of the breach, its likely consequences, the measures we have taken, and the safety measures you should take; and (b) intimate the Data Protection Board of India without delay of the nature, extent, timing and location of the breach, followed by a detailed report to the Board within 72 hours of becoming aware of the breach, covering the facts, mitigation steps, findings as to the cause, remedial measures, and a report on the intimations sent to Data Principals.
Business data you upload. For books data you upload (including about your customers, vendors and employees) we are your Data Processor. If a breach affects it, we will notify you, the business, within 48 hours of becoming aware, with what you need to meet your own duties to the Data Protection Board and affected people. We do not contact your customers, vendors or employees directly unless you ask or the law requires. See our Data Processing Addendum.
We report cyber security incidents to CERT-In within six hours of noticing them, as required by its Directions of 28 April 2022, and notify affected users and the Data Protection Board of India as required by the DPDP Act and Rules. We retain system logs in India for at least 180 days (and one year where DPDP Rule 8(3) applies).
17. Grievance Officer & Data Protection Board
Grievance Officer
Name: Uday Bisht
Designation: Grievance Officer & Data Protection Officer
Email: grievance@lekhabooks.in
Phone: +91 77107 71301
Postal: Lekha Logic Consulting Private Limited, Rzd-1/101, Gali No. 5, Mahavir Enclave, Palam Village, New Delhi 110045, India.
Response time: we acknowledge every complaint within 24 hours. Complaints about your personal data (the DPDP Act, 2023) we aim to resolve within 30 days; this is our own commitment and is shorter than the maximum of ninety days that the Digital Personal Data Protection Rules, 2025 allow for responding to a grievance. Complaints under the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, for example about content on the Service, are resolved within 7 days, as stated in Terms. The two timeframes apply to different kinds of complaint.
If you remain dissatisfied after the Grievance Officer's response (the DPDP Act, Section 13(3), asks you to use our grievance process first), you may complain to the Data Protection Board of India established under the DPDP Act. The Board works as a digital office: complaints are filed online, in the manner the Board publishes on its official website.
18. Changes to this Policy
15 November 2026: Sections 7, 9, 10 and 13: the encrypted off-site backup copy in Google Drive (Google LLC) is disclosed; Section 5 now uses only the grounds the DPDP Act allows (consent and legitimate uses); Sections 7, 8 and 9: AI providers are chosen by LekhaBooks (not by the tenant Owner), xAI (Grok) and Sarvam AI (voice input) added, DeepSeek described as blocked unless a data-processing agreement is signed, SMS / WhatsApp providers described as ones you connect with your own account, Sign in with Google and the Account Aggregator technology provider added, the unused OCR language-data host removed, and integrations you switch on yourself explained; Sections 3.2 and 14: cookie list corrected to the cookies the Service actually sets; Section 10: audit-trail, security-log and backup periods corrected; Section 12: how to nominate; Section 13: security list limited to measures in place (two-factor sign-in is mandatory for our administrators, optional for partner users); Sections 15 and 17: persons with disability, and how to reach the Data Protection Board; a change that needs your consent is no longer treated as accepted by continued use; the DPDP commencement dates are explained.
9 November 2026: Added the Data Processing Addendum and a business-data breach-notice period; clarified that use of the Service is not consent to optional processing; removed the fee for rights requests; corrected legal citations; revised the cross-border safeguards wording; listed WhatsApp (Meta), Google Meet, the bank-feed Account Aggregators and outside professionals as recipients; described GST portal credentials; removed payment-method tokens wording and an unconfirmed backup claim.
1 November 2026: Disclosed Cloudflare's cookie-less Web Analytics on the public website (Sections 7 and 14).
12 October 2026 (later): DeepSeek (China) reinstated as an optional AI provider; opt-in only, with a notice shown before it is enabled.
12 October 2026 (deletion and incidents): Sections 10 and 16: one account-deletion and record-retention wording (books kept on your instruction until the end of the 8th financial year after the latest entry, then deleted), and CERT-In six-hour incident reporting with 180-day log retention in India. Sections 7, 8 and 9: DeepSeek (China) removed in this change (reinstated as an optional, opt-in provider later the same day - see the entry above); AI providers were then limited to Anthropic, OpenAI and Google (Gemini), used only when the tenant Owner configures one, and no AI text is sent to China-hosted providers.
12 October 2026: Added WhiteBooks (GST Suvidha Provider), Google Analytics, Google Fonts, jsDelivr / cdnjs, Cloudflare Web Analytics and the Tesseract OCR language-data host to Section 7, and the lb_consent, _ga and _gid cookies (and the lb_aid session entry, which replaces the earlier ll_anon_id entry) to Sections 3.2 and 14.
7 October 2026: Added DeepSeek (AI features, opt-in only; processing in China) to the sub-processor list in Section 7, and to the AI-features and cross-border-transfer sections (8 and 9).
11 September 2026: Account closure and verified erasure use a single deletion deadline of 30 days for active systems and backups, subject to legal-retention exceptions.
Entries above are listed newest first; where several entries share a date, the latest change is listed first, so a later entry replaces an earlier one on the same date. We may revise this Policy from time to time. The "Effective" and "Last updated" dates at the top will always reflect the current version, and we maintain a public changelog of substantive revisions. For material changes (such as new categories of personal data collected, new sub-processors with cross-border implications, or change of legal basis), we will notify you by email and via in-product banner at least 30 days before the change takes effect. If a change needs your consent (for example a new purpose or a new optional feature), we will ask for it, and we will not treat continued use of the Service alone as consent.
19. Contact
General & product: support@lekhabooks.in
Privacy questions: privacy@lekhabooks.in
Grievance Officer: grievance@lekhabooks.in, +91 77107 71301
Legal: legal@lekhabooks.in
Postal: Lekha Logic Consulting Private Limited, Rzd-1/101, Gali No. 5, Mahavir Enclave, Palam Village, New Delhi 110045, India.
© 2026 Lekha Logic Consulting Private Limited. All rights reserved. This Policy is governed by the laws of India. Disputes are subject to the exclusive jurisdiction of the courts at New Delhi. "LekhaBooks" is a trademark of Lekha Logic Consulting Private Limited.