EasyBooks · Privacy

Navjewansh EasyBooks — Privacy Policy

A. Scope

This policy covers Navjewansh EasyBooks: the locally installed Windows desktop application, the public hosted EasyBooks demo, optional email and WhatsApp Business connections, and privacy-related support requests. It does not cover third-party websites or services that you choose to use, including Meta, Google, Microsoft, your email host, or any OCR provider you configure.

Local-first operation. EasyBooks stores business records and connected-account information locally on the customer’s computer. Navjewansh does not receive or store these records through normal operation of the local application.

When a customer enables email or WhatsApp integration, information necessary for that function is exchanged with the customer’s selected email provider or Meta. Those providers process information under their own terms and privacy policies.

Information voluntarily supplied to Navjewansh for support, licensing or other direct interactions is handled separately as described in this policy.

B. Information processed

EasyBooks is business software. The records you create may include business and contact details, customer and supplier records, invoices and quotations, payments and receivables, purchase bills, expenses, documents, notes, staff details, and accounting settings. Documents may include PDFs and images that you upload, receive from a phone, or import from email.

If you enable email integration, EasyBooks processes the mailbox address and nickname, provider details, authorization information, selected folder names, message sender, subject, received time, a short provider-supplied preview, attachment names and sizes, and the contents of supported attachments that are downloaded for review. EasyBooks does not store the complete body of every email.

If you enable WhatsApp Business, EasyBooks processes the business name and mobile number, the connected Meta business assets and identifiers, authorization information, message templates, message content you compose or send, recipient numbers, delivery status, and related audit records. Current code processes delivery-status callbacks from Meta. It does not automatically ingest the content of inbound WhatsApp messages through the Meta webhook.

Administrators sign in with credentials configured by the operator, and EasyBooks keeps a server-side session. Support correspondence sent to info@navjewansh.com is processed to answer the request and maintain business records. Technical information such as error messages and access times may be recorded on the installation or by a hosting provider.

Facebook public-profile information: EasyBooks does not request Facebook public-profile fields. During Meta Embedded Signup, Meta returns authorization and business-asset information needed to connect WhatsApp, such as the WhatsApp Business Account ID, phone-number ID, business or verified name, and display phone number. EasyBooks uses this only to establish and manage the connection.

C. Local and online storage

Local installation. EasyBooks stores its database, attached documents, message and WhatsApp records, configuration, and encryption keys in the data directory on the customer’s computer. Accounting records, documents, email content, WhatsApp records, backups, and integration credentials are not sent to Navjewansh through normal operation of the desktop application. The business controls the device, data directory, local accounts, backups, and any copy of the data it creates.

The inspected application does not implement a Navjewansh-hosted message relay, cloud backup, business-content analytics, or remote logging of customer records. Backup files stay on the customer’s system or wherever the customer chooses to store or download them.

Backups and restore. A backup contains the local database and document files, but not the mailbox or device/WhatsApp master-key files. Restoring on the same Windows account with the original key files still present preserves connected accounts. Restoring on another computer, after reinstalling Windows, or after losing the data directory restores accounting records and documents but requires reconnecting email and WhatsApp accounts and re-pairing phones.

Optional online features. Data leaves the computer only when an authorised person enables or uses a feature that requires an external provider. Connecting an email account sends authorization and mailbox requests to the chosen email provider. Importing email attachments downloads them from that provider. Sending email or WhatsApp messages sends the message, recipient, and any attachment to the relevant provider. Configuring an external OCR provider sends the selected document to that provider. The current application does not call an external AI or large-language-model service; its “Ask” feature answers from local records using built-in rules.

Hosted demo. The public demo at easybooks.demos.navjewansh.com is a separate deployment. It is not the desktop application and does not receive local desktop data. Data entered in the demo is stored on the demo server, not on your computer, and is not connected to a local installation. The demo is intended for fictional or test data; do not enter real business or personal information. The deployment inspected runs email, mailbox, and WhatsApp integrations in test mode and does not configure an OCR provider. Demo data remains until the operator resets or removes it; no fixed demo retention period is promised.

D. Purposes

EasyBooks uses information to maintain accounting and business records; create and manage invoices, quotations, purchases, expenses, payments, and reports; import and review documents; connect and manage authorised email and WhatsApp accounts; send communications that an authorised user explicitly requests; show connection and delivery status; provide support; protect the service; and administer the hosted demo and website.

E. Email integration

EasyBooks supports Google Gmail, Microsoft 365, and IMAP/SMTP mailbox connections. Google and Microsoft connections use the provider’s own sign-in. The incoming permissions requested are read-only Gmail access or Microsoft Mail.Read access for the selected account. A separate gmail.send or Mail.Send permission is requested only if outgoing email is set up. IMAP connections use the server settings and app password supplied by the operator and access the folders selected in EasyBooks.

EasyBooks reads message metadata and supported attachments from the selected folders and can download attachments into the local document review queue. Background checks refresh message metadata; an explicit Sync now action may also download pending supported attachments. Outgoing email is disabled by default. An authorised owner must separately enable sending, and messages are sent only for explicit actions such as a test, an invoice delivery, a payment reminder, or a CA pack requested by the owner.

You can disconnect an email account in EasyBooks. Disconnecting removes that account’s stored credentials, tokens, message metadata, and attachment metadata from EasyBooks and attempts provider-side OAuth revocation where supported. Documents already imported into EasyBooks remain until the business deletes them. You can also revoke access directly in your Google or Microsoft account permissions, or change the password or app password with your email host.

F. WhatsApp and Meta integration

EasyBooks supports the Meta WhatsApp Business Cloud API through a Meta developer app and WhatsApp Business account supplied by the customer. The customer controls those Meta assets and credentials. No shared Navjewansh WhatsApp gateway or message relay is implemented in the inspected EasyBooks source. The credentials are configured for that installation and the WhatsApp records stay in the local data directory.

Message sends, account-verification requests, template calls, and webhook handling are performed by the local EasyBooks backend, not by browser JavaScript. The optional Meta Embedded Signup flow loads Meta’s JavaScript SDK in the browser to complete the authorization window; Meta returns a signup code and business-asset identifiers to EasyBooks, and the local backend exchanges the code and stores the resulting token. The browser code does not send WhatsApp messages directly to Meta.

When a business connects WhatsApp, EasyBooks stores the business name, mobile number, connection status, WhatsApp Business Account and phone-number identifiers (masked in the interface), the access token in encrypted form, message templates, conversation and message records, notification-outbox records, delivery status, and audit entries locally. Meta receives the recipient number, template name and parameters, message content, and related API requests when a message is sent.

Webhook endpoint. EasyBooks exposes a WhatsApp webhook as part of the local EasyBooks server at /api/webhooks/whatsapp. Meta cannot contact a normal localhost installation directly. Receiving webhooks requires a publicly reachable HTTPS endpoint controlled by the customer, such as a reverse proxy or secure tunnel that forwards the webhook path to the local service. The customer must configure that URL and the Meta verify token. This endpoint is part of the installation; Navjewansh does not operate a relay, store these callbacks, or provide a hosted webhook service for the desktop application.

When the webhook is reachable, Meta can send delivery, read, and failure status events. EasyBooks stores an event key, receipt time, delivery status, and error text locally and uses them to update its outbox. Current code does not process inbound message content from Meta. Inbound WhatsApp documents are supported only through a separate inbound bridge endpoint if the customer configures one; EasyBooks does not retrieve Meta media directly.

When the computer is off or disconnected. WhatsApp sending, webhook receipt, and delivery-status updates do not run while the EasyBooks computer or local server is off or offline. Pending local outbox items may be retried when EasyBooks starts again if they are eligible for retry. Webhook events delivered while the endpoint is unreachable may be missed; Meta’s own retry behaviour is governed by Meta. Navjewansh does not queue or hold those events.

Owning a Meta developer app does not by itself enable coexistence with the WhatsApp Business phone app. Coexistence and number eligibility must be confirmed by Meta, and EasyBooks does not change or re-register a number before Meta confirms. Do not configure the integration unless the business owns or is authorised to use the number. The business must obtain any required recipient permission, honour opt-outs, and comply with Meta’s terms and applicable messaging rules. Provider terms apply to Meta’s processing.

Disconnecting WhatsApp clears the stored account connection and access token from EasyBooks and disables WhatsApp automation. Conversation, message, outbox, template, and webhook-event records already stored locally remain until the business deletes the local data.

G. Sharing and providers

EasyBooks does not sell business data. In normal desktop operation, local records and credentials are not sent to Navjewansh. Information is exchanged only with the providers needed for features an authorised person enables, with recipients they choose, or as required for support that the customer requests. Depending on configuration, the following providers may receive data:

Provider privacy information is available from Google, Microsoft, Meta, Resend, and AWS. The operator should provide the privacy notice of any OCR provider it configures. Information may also be disclosed when required by law, to protect rights or safety, to investigate misuse, or to respond to a support request the customer initiates. The inspected application has no built-in remote-support access; support information is supplied only through a channel the customer chooses.

H. Security

EasyBooks stores mailbox credentials and OAuth tokens encrypted with AES-256-GCM using a key kept separately from the database. WhatsApp access tokens are also stored encrypted. The owner password is supplied through local application configuration and is not written into the database. Authenticated sessions use an HttpOnly, SameSite cookie; session lifetime is 12 hours, or 30 days when “remember” is selected. The local backend applies rate limits to sign-in and upload endpoints and sets browser security headers.

Windows credential protection. On Windows, the mailbox and device/WhatsApp master keys are wrapped with Windows DPAPI using the CurrentUser scope. The AES-256-GCM encrypted records remain decryptable by the same Windows user, while a different Windows user or a copy moved to another computer will not normally be able to unwrap the key. Existing plaintext key files are migrated in place on first use; the underlying AES key does not change, so existing mailbox and WhatsApp records continue to work. If DPAPI migration fails, the original key file is left unchanged and the integration shows an actionable key error. Non-Windows development builds may use application-managed key files with restrictive permissions.

These safeguards reduce risk but do not make any system absolutely secure. The business is responsible for the security of the computer, the Windows account, the data directory, backups, network access, and who can use an authorised session. Do not expose a local installation directly to the internet unless it is properly secured, and keep backups in a protected location.

The EasyBooks application does not include third-party advertising trackers or external business-data analytics, and no third-party remote error-reporting service is configured in the inspected code. The corporate website uses first-party visitor analytics stored on the website’s own server; its browser script uses local and session storage identifiers rather than advertising cookies.

I. Retention

EasyBooks does not automatically expire local accounting records. Retention is controlled by the business that operates the installation, subject to its own legal and accounting obligations.

J. Rights and deletion

To ask about access, correction, or deletion, email info@navjewansh.com with the subject EasyBooks Privacy / Data Deletion Request. Include your name, business name, the email address or WhatsApp number connected to the relevant EasyBooks installation, and what you want deleted or corrected. Do not send passwords, access tokens, one-time passwords, or other credentials.

We may need to verify your identity or authority to act for the business before changing or deleting data. Some records may be retained where required by law, for accounting or dispute purposes, for security, or to protect the rights of others. Data held independently by Meta, Google, Microsoft, an email host, an OCR provider, or a message recipient is not controlled by Navjewansh and must be handled through that provider.

For a local installation, the business operating EasyBooks controls its own records and can delete documents and records in the application, remove the data directory, and delete local backups. The inspected application has no built-in remote-access channel to the customer’s computer. Navjewansh cannot remotely access or delete a local installation; any support file or access the business chooses to share is a separate voluntary interaction. Individuals whose data is held by a business using EasyBooks should contact that business first. More detail is on the EasyBooks data deletion instructions page.

K. International processing

The corporate website and hosted demo use Amazon Web Services and CloudFront, which may process data in locations outside India. Email, WhatsApp, and OCR providers may also process data in other countries under their own terms and safeguards. EasyBooks does not guarantee that data will remain in a particular country. The business should consider its own legal and contractual requirements before enabling an external provider.

L. Children, updates and contact

EasyBooks is intended for business use and is not directed to children. Do not create accounts for, or enter personal information about, children except as necessary for a legitimate business record and with the required authority.

We may update this policy when the product or applicable requirements change. The revised page will show a new “Last updated” date. Material changes should be reviewed by the operator before they are relied on.

Licensing and update requests. The inspected EasyBooks build does not contain a licence-activation server or an automatic update check that contacts Navjewansh. It does not transmit business records, email or WhatsApp content, or credentials for licensing. If a future Windows build adds a licensing or update request, this policy will be updated before the feature is enabled to identify the endpoint and the exact information transmitted. Such a request should be limited to the information needed to check the product version, installation or licence status, and the result; it should not require accounting records or integration content.

NAVJEWANSH PRIVATE LIMITED
Plot No. 28-A, Kh. No. 127, 2nd Floor,
Rajpur Khurd Extension, South Delhi,
Delhi 110068, India
Email: info@navjewansh.com