Privacy Policy.

1. Introduction & Scope

BizSensei Digital (“BizSensei”, “we”, “us”, “our”) is a hybrid growth and performance marketing agency and software engineering studio based in India. We operate the website at bizsensei.co.in (the “Website”), sell WordPress plugins through our WooCommerce-powered store (the “Store”), and provide agency services including performance marketing, web development, search engine optimisation, and retention marketing (the “Services”).

This Privacy Policy explains what personal data we collect, why we collect it, how we use and share it, how long we keep it, and the rights you have over it. It applies to everyone who interacts with BizSensei: Website visitors, Store customers, trial and demo users, agency clients, and anyone who contacts us. It also explains, plugin by plugin, what data our software products handle and where that data goes, so you can make an informed decision before you install or buy anything we make.

This Policy is framed around India’s Digital Personal Data Protection Act, 2023 (the “DPDP Act”) and the language it uses. Under the DPDP Act, we act as a Data Fiduciary — the party that decides why and how personal data is processed — and you are the Data Principal, the individual the data relates to. Where we process data on behalf of someone else (for example, when a restaurant uses BizSensei OMS to take orders from its own customers), the restaurant is the Data Fiduciary for that data and we act only on its instructions, as explained in Section 4.

By using the Website, buying from the Store, installing our plugins, or engaging our Services, you acknowledge this Policy. If you do not agree with it, please do not provide us with your personal data or use the parts of our offerings that require it.

1.1 Who This Policy Covers

This Policy covers personal data relating to:

• Website visitors — anyone who browses bizsensei.co.in, reads our pages, or submits a form.
• Store customers — anyone who creates an account, places an order, or downloads a product from our Store.
• Plugin users and licensees — anyone who installs, activates, or updates BizSensei OMS, BizSensei GST Invoices, BizSensei WhatsApp Connect, or any other software we publish, including the site administrators who enter license keys.
• Agency and Services clients — the individuals we deal with at client organisations, and any personal data a client asks us to handle while delivering the Services.
• Correspondents — anyone who emails, calls, or messages us, including job applicants and business contacts.

If you are the customer of one of our plugin users — for example, a diner ordering food through a restaurant’s website that runs BizSensei OMS — your data is collected by that restaurant, not by us. That restaurant’s own privacy policy governs your data, and any request about it should go to them first. Section 4 explains exactly what we can and cannot see in that situation.

1.2 What “Personal Data” Means

“Personal data” means any data about an individual who is identifiable by or in relation to that data — the same meaning it carries under the DPDP Act. This includes obvious identifiers such as your name, email address, phone number, and billing address, as well as data that becomes identifying in combination, such as an order history tied to your email address or a device identifier linked to your account.

It does not include data that has been genuinely anonymised so that no individual can be identified from it, nor does it include information about companies as such (as opposed to the individuals who work at them). Where this Policy says “data”, it means personal data unless the context clearly indicates otherwise.

We collect personal data in three ways: (a) data you give us directly, such as when you fill in a form or place an order; (b) data generated automatically when you use our Website or when our plugins communicate with our servers, such as log entries and license-check transmissions; and (c) data we receive from third parties you have authorised, such as a payment confirmation from Razorpay after a successful transaction.

2. Who Controls Your Data

For the personal data described in Sections 3 and 8 through 13 of this Policy, the Data Fiduciary is BizSensei Digital, operating the Website at bizsensei.co.in. We determine the purposes and means of processing that data: what is collected, why it is needed, how long it is kept, and who it is shared with. Where the law requires us to name a Data Protection Officer or grievance officer, our published grievance contact in Section 15.5 serves that function.

There are two situations where we are not the Data Fiduciary. First, when a business uses our plugins to process its own customers’ data — for instance, a restaurant taking orders through BizSensei OMS, or a store owner generating GST invoices for their buyers — that business is the Data Fiduciary and we process the data only as its processor, on its instructions. Second, when data passes through a third party’s infrastructure under that party’s own terms — for example, WhatsApp messages routed through Meta’s WhatsApp Cloud API, or card details entered on Razorpay’s checkout — that third party is independently responsible for its own processing, as described in Sections 6 and 8.

2.1 Our Identity as Data Fiduciary

Legal name: BizSensei Digital. Website: https://bizsensei.co.in. Email: info@bizsensei.co.in. Phone: +91 93726 65745. We do not publish a street address; email is the fastest way to reach us about privacy matters, and Section 19 lists every channel.

As Data Fiduciary we are responsible for complying with the DPDP Act’s obligations: collecting data only for a lawful purpose with your consent (or another permitted basis), giving you clear notice of what we collect and why, keeping data accurate and secure, retaining it no longer than needed, honouring your rights as a Data Principal, and maintaining a working grievance redressal mechanism.

2.2 When Someone Else Is the Data Fiduciary

If you gave your personal data to a business that uses our software — a restaurant, a WooCommerce store owner, an agency client — that business decided to collect it and decides what to do with it, which makes it the Data Fiduciary. Our role is limited to providing the software that business runs on its own systems. We do not sell, mine, or reuse that business’s customer data, and we do not contact those end customers for our own purposes.

In practice this means: if you want to access, correct, or delete data you gave to a restaurant or store that uses our plugins, contact that business directly. If they ask us for technical help to carry out your request — for example, locating an order record inside their WordPress database — we will assist them, but we act on their instruction, not on a request sent to us alone. If you are unsure who holds your data, write to us at info@bizsensei.co.in and we will point you to the right party.

3. Information We Collect

We collect only the personal data we actually need for the purposes described in Section 10. What we collect depends on how you interact with us. The categories below describe each interaction type in detail; Sections 4 through 8 then explain what our individual software products handle, because the data a plugin touches on your server is a different matter from the data that reaches our servers.

3.1 Website Visitors

When you browse bizsensei.co.in without buying anything or contacting us, we collect a limited set of technical data automatically: your IP address, browser type and version, operating system, referring page, pages visited, time spent, and approximate location derived from your IP address. Our web server also writes standard access and error log entries recording the date, time, requested URL, and response status. This data is used for security, diagnostics, and understanding aggregate usage — never to build individual profiles for advertising.

If you submit our contact form, we collect the details you type in: your name, email address, phone number, and the contents of your message, plus the page you submitted it from and the timestamp. If you subscribe to any newsletter or updates we offer, we collect your email address and your subscription preferences. If you comment on or interact with any interactive element on the site, we collect whatever you choose to publish there.

3.2 Store Customers

When you buy from our Store, we collect the information needed to fulfil your order and issue your license: your name, billing email address, phone number, billing address (street, city, state, PIN code, country), the products you ordered, the amounts paid, the currency (INR), the payment method type, and the transaction references returned by our payment processor. If you create a Store account, we also store your username, an encrypted password hash (never the plain password), and your order and download history.

We issue a software license for each paid product. Issuing it requires us to record the license key, the product and plan it belongs to, the purchase (order) reference, the customer it was issued to, its activation status, and its expiry (our current plans are lifetime, so no expiry is set). When you activate the plugin on your site, the plugin sends our server the license key, your site’s domain, and the plugin version so we can validate it — Section 7 describes that transmission in full.

We do not collect or store your full card number, CVV, UPI PIN, or net-banking credentials. Payment details are entered on Razorpay’s secure checkout and processed by Razorpay; Section 8 explains exactly what payment information reaches us.

3.3 Support Communications

When you contact us for help — by email, phone, WhatsApp, or any support channel — we collect your name, contact details, and the content of your correspondence, including any screenshots, order numbers, license keys, or site URLs you share so we can diagnose the issue. If you grant us temporary access to your WordPress admin area or server to fix a problem, we treat everything we can see during that session as confidential, access only what is needed for the reported issue, and do not copy your site’s customer or business data off your server.

Support conversations are retained so we can follow up on recurring issues and improve our products, as described in Section 12. If a support request reveals a bug that affects other users, we may describe the bug in general terms in release notes, but we never publish your personal data or anything that identifies your business without your explicit permission.

3.4 Agency & Services Clients

When you engage us for agency Services, we collect the business contact details of the people we work with: names, work email addresses, phone numbers, job titles, and billing contacts. To deliver the Services you have asked for, you may also grant us access to systems that contain personal data — for example, your advertising accounts (Meta, Google, LinkedIn), analytics properties, social media accounts, email marketing lists, or customer databases. We access such systems strictly to perform the agreed work, we do not export or retain copies of your customer lists beyond what the work requires, and we never use your ad-account or customer data for any other client or for our own marketing.

Project-related personal data — proposals, contracts, invoices, meeting notes, feedback shared over email or calls — is collected and stored to manage the engagement, bill accurately, and maintain a record of decisions. If your project involves us building or configuring a website or store that will itself collect personal data from your customers, we will implement the collection and consent mechanisms you specify, but the resulting customer data remains yours: you are its Data Fiduciary, and this Policy does not replace the privacy policy you publish to your own customers.

4. Data Handled by BizSensei OMS

BizSensei OMS is our restaurant order management and POS software: QR-code table ordering, a kitchen and staff dashboard, multi-branch management, delivery ordering with live-style order tracking, and a visual menu designer. It is installed on the restaurant’s own WordPress site. Understanding who sees what is essential, so this section describes the data flows precisely.

The restaurant that installs BizSensei OMS is the Data Fiduciary for all data the plugin handles — the menus, orders, customer details, and staff accounts belong to the restaurant’s business. We built the software; we do not operate the restaurant’s site and we do not routinely have access to its database. The plugin does not phone home with order or customer data. The only data that travels from an OMS installation to our servers is the license validation transmission described in Section 7.

4.1 Order & Customer Data

When a diner places an order through a restaurant’s QR ordering page, the plugin records what the checkout asks for: the items ordered, quantities, customisations and add-ons, the order total and tax breakup, the table identifier or branch selected, the order type (dine-in, takeaway, or delivery), and whatever contact details the restaurant’s checkout collects — typically the customer’s name and phone number, and for delivery orders, the delivery address. If the restaurant enables customer accounts, the plugin stores the account credentials the customer creates (passwords are stored as one-way hashes, never in plain text).

All of this lives in the restaurant’s own WordPress database, on the restaurant’s own hosting. It is visible to the restaurant’s staff through the OMS dashboards (kitchen display, order list, reports) because that is the point of the software. It is not transmitted to BizSensei, not visible to us, and not used by us for any purpose. We cannot see who ordered what from which restaurant, and we have no way to look it up.

4.2 Staff & Branch Data

Restaurants use BizSensei OMS to manage their team: staff user accounts (names, usernames, email addresses, roles and permissions), branch details (branch names, addresses, phone numbers, opening hours, delivery settings), table and QR-code configurations, and menu data (items, prices, categories, images, add-on groups). Delivery-agent assignments may include an agent’s name and phone number so customers can tap-to-call during tracking.

Like order data, all of this is stored on the restaurant’s own site and administered by the restaurant. We do not maintain a copy, we do not monitor staffing or branch activity, and we do not contact restaurant staff or customers. If a restaurant asks us for implementation help, we may see staff or branch data while logged into their admin area with their permission, and we treat it as confidential under Section 3.3.

4.3 Delivery Data

Where a restaurant enables delivery ordering, the plugin collects the delivery address the customer types at checkout, the customer’s phone number for order coordination, the delivery fee and minimum-order rules configured per branch, and the order’s tracking timeline (timestamps for placed, preparing, on-the-way, and delivered stages, plus any assigned agent’s name and contact number). Customers can follow this timeline on the restaurant’s tracking page, which refreshes automatically.

BizSensei OMS does not perform live GPS tracking of delivery agents or customers — the timeline reflects status updates entered by restaurant staff, not real-time location. Delivery data stays in the restaurant’s database alongside other order data and is subject to the same non-access commitment: we do not receive it, store a copy, or process it.

4.4 What We Can and Cannot See

To be completely explicit: we cannot see a restaurant’s menus, orders, customer names, phone numbers, addresses, staff accounts, revenue reports, or any other business data held inside its BizSensei OMS installation. The plugin was designed so that none of this leaves the restaurant’s server except in the two cases the restaurant itself initiates: (a) the restaurant configures an integration that sends data somewhere (for example, WhatsApp notifications via its own Meta app — see Section 6), and (b) the restaurant contacts us for support and shares data with us directly.

We can see only the license validation data described in Section 7 (license key, domain, plugin version) when the plugin checks in with our server, plus whatever a restaurant voluntarily sends us in a support conversation. If you are a diner or customer of a restaurant using BizSensei OMS and you want to know what data the restaurant holds about you, or you want it corrected or deleted, please contact the restaurant directly — they are the Data Fiduciary and the only party able to act on your request.

5. Data Handled by BizSensei GST Invoices

BizSensei GST Invoices generates GST-compliant tax invoices, credit notes, HSN summaries, and GSTR-1 exports for WooCommerce stores in India. It runs entirely inside the store owner’s own WordPress installation and works with data the store already holds. This section explains what it touches and — just as importantly — what never leaves the store owner’s server.

5.1 Invoice & GSTIN Data

To produce a GST-compliant invoice, the plugin reads the WooCommerce order it is attached to: the buyer’s billing name, billing address, and contact details as entered at checkout; the line items purchased with quantities, prices, discounts, and tax rates; and the computed tax breakup (CGST, SGST, or IGST amounts as applicable). It combines this with the seller’s business details configured by the store owner in the plugin settings: business name and address, GSTIN, invoice numbering series and prefixes, HSN/SAC codes per product, and any footer notes, terms, or bank/UPI details the seller wants printed on the invoice.

Credit notes reference the original invoice and the adjusted amounts; HSN summaries aggregate taxable values and tax amounts by HSN code across a date range; GSTR-1 exports compile outward-supply data (invoice numbers, dates, taxable values, tax amounts, place of supply) into the format the seller needs for filing. All of these artefacts are generated on demand from data already present in the store’s database — the plugin does not ask buyers for any additional personal data beyond what WooCommerce checkout already collected.

5.2 Where It Lives

Everything the plugin reads, generates, and stores lives in the store owner’s own WordPress database and file system, on the store owner’s own hosting account. Generated invoice PDFs are stored on the store’s server (or generated on the fly per request, depending on the store’s settings) and are served to the store owner, their staff, and — where the store is configured to do so — to the buyer who placed the order, typically as an email attachment or a download link in their account area.

The plugin makes no outbound network calls carrying invoice, buyer, or GSTIN data to BizSensei or to any third party. It does not validate GSTINs against a government database, does not file GSTR-1 on the seller’s behalf, and does not upload invoice data anywhere. The GSTR-1 export is a file the seller downloads and files themselves through the GST portal. If the store owner configures their own email delivery, invoice emails travel through the store’s own mail setup, not through our infrastructure.

5.3 Our Non-Access Commitment

Because all invoice data stays on the store owner’s server, we do not receive, see, or store any buyer’s billing details, any seller’s GSTIN, or any invoice, credit note, HSN summary, or GSTR-1 content generated by the plugin. We have no dashboard, log, or back door through which we could view it. The store owner is the Data Fiduciary for the personal data in their invoices (their buyers’ billing details); we are not a party to that processing at all, except as described in the next paragraph.

The sole exception is support: if a store owner contacts us about an invoice formatting or tax-calculation issue and voluntarily shares an invoice PDF, a screenshot, or admin access, we will see whatever they share for the duration of the support session, treat it as confidential under Section 3.3, and not retain copies of buyer personal data after the issue is resolved. The only routine transmission from a GST Invoices installation to our servers is the license validation described in Section 7.

6. Data Handled by BizSensei WhatsApp Connect

BizSensei WhatsApp Connect sends WooCommerce order notifications over WhatsApp. Critically, it does this through the store owner’s own Meta WhatsApp Cloud API app: the store owner creates the app in their Meta developer account, connects their own WhatsApp Business phone number, and pastes the credentials into the plugin’s settings on their own site. Messages are then sent from the store’s number, through Meta’s infrastructure, to the buyer’s number. This section explains the resulting data flow honestly, because a third party — Meta — is necessarily involved.

6.1 How the Meta Cloud API Flow Works

When an order event the store owner has enabled occurs — for example, a new order, a status change to processing or completed, or a refund — the plugin composes a message from a template the store owner configured, filling in order details such as the order number, items, totals, and the buyer’s name. It then calls the WhatsApp Cloud API using the store owner’s own access token, asking Meta to deliver that message from the store’s WhatsApp Business number to the buyer’s phone number as recorded in the WooCommerce order.

The plugin stores the store owner’s Meta credentials (app access token, phone number ID, business account ID) in the store’s own WordPress database so it can authenticate these API calls. Message templates, send triggers, and a log of sent messages (recipient number, template used, timestamp, delivery status returned by Meta) are likewise stored on the store’s server. None of these settings or logs are transmitted to BizSensei.

6.2 Phone Numbers & Message Content

The personal data involved in each notification is: the buyer’s phone number (the destination), the buyer’s name and order details included in the message text, and the store’s WhatsApp Business number (the sender). The buyer’s phone number comes from the WooCommerce order — it is data the buyer gave the store at checkout, and the store is the Data Fiduciary for it. By enabling WhatsApp notifications, the store owner instructs the plugin to use that number for order updates; stores are responsible for ensuring their checkout notice or terms tell buyers that order updates may arrive on WhatsApp.

Message content passes through Meta’s servers because Meta operates the WhatsApp network — there is no way to send a WhatsApp message without it. The plugin does not add tracking pixels, does not read the buyer’s replies (incoming messages are a separate feature the store owner would configure in their Meta app, outside this plugin’s scope), and does not retain message content on our servers. The send log kept on the store’s server records that a message was sent and what Meta reported back; it exists so the store owner can audit notifications and troubleshoot failures.

6.3 Meta as a Separate Data Fiduciary

Once a message enters Meta’s infrastructure, Meta Platforms, Inc. and its affiliates process it under Meta’s own terms and privacy policy, not under this Policy. Meta acts as an independent Data Fiduciary (or equivalent under applicable law) for its operation of the WhatsApp Business Platform: message routing, delivery, spam and abuse prevention, and any logging Meta performs on its side. We do not control what Meta retains, how long it keeps it, or how it uses it, and we cannot delete data from Meta’s systems on your behalf.

What this means in practice: (a) store owners should review the WhatsApp Business Terms of Service and Meta’s privacy commitments before connecting the plugin, and reflect WhatsApp notifications in their own customer-facing privacy notice; (b) buyers with questions about how Meta handles their WhatsApp data should consult Meta’s policies or contact Meta; (c) our responsibility is limited to the plugin’s behaviour on the store’s server — composing the message locally, transmitting it to Meta’s API over an encrypted connection, and logging the outcome locally. As with our other plugins, the only data a WhatsApp Connect installation sends to our servers is the license validation described in Section 7.

7. License Validation Telemetry

Our paid plugins — BizSensei OMS, BizSensei GST Invoices, and BizSensei WhatsApp Connect — are licensed software. Each licensed copy includes a small licensing client that periodically contacts our license server at bizsensei.co.in to validate the license key and to check for updates. This section documents exactly what is transmitted during those check-ins, because we believe telemetry should be auditable, not mysterious.

License checks happen at predictable moments: when you first activate a license key in the plugin’s settings, when WordPress runs its routine update checks (roughly twice daily), when you click “check for updates”, and when the plugin’s license screen is viewed. Each check is a short HTTPS request to our server’s licensing API endpoint. No license check reads your site’s posts, orders, customers, or settings beyond the three fields listed in Section 7.1.

7.1 What a License Check Transmits

Each license validation request contains exactly three pieces of information: (1) the license key you entered when activating the plugin — a random string that identifies your purchase, not you; (2) the site URL (domain) the plugin is installed on, for example example.com — used to enforce the per-plan domain limit (our current plans allow one site per license) and to detect key sharing; and (3) the installed plugin version, for example 1.0.0 — used to determine whether an update is available and to diagnose version-specific issues.

Our server logs these check-ins alongside a timestamp and the requesting IP address (as any web server log does) so we can detect abuse — for example, one key validating from fifty unrelated domains — and so we can answer support questions like “why is my key showing as invalid?”. We use this data solely for license administration, piracy prevention, and support. The lawful basis is the license contract with you and our legitimate interest in protecting our software from misuse.

7.2 What a License Check Never Transmits

To remove any doubt, a license check does not transmit: your name, email address, or any account details; your site’s admin usernames or passwords; your customers’, diners’, or buyers’ personal data; order, invoice, or revenue data; your site’s content, settings, or database; or any browsing or behavioural analytics. The licensing client has no access to that information and makes no attempt to collect it.

In particular: activating BizSensei OMS does not send us your restaurant’s orders; activating GST Invoices does not send us invoices or GSTINs; activating WhatsApp Connect does not send us phone numbers or message logs. Sections 4, 5, and 6 describe those plugins’ data handling in full — the license check is a separate, minimal transmission, and conflating the two would be a misunderstanding we want to prevent.

7.3 Update Checks & Downloads

When a license check determines that a newer version of the plugin is available, WordPress shows the update in the site’s Dashboard → Updates screen, and the plugin’s license screen may show the current version and update status. If you choose to update, WordPress downloads the new plugin package from our server. The download request carries the same three fields (key, domain, version) so we can confirm the site is entitled to the update.

Deactivating a license (from the plugin’s license screen) sends a final request asking our server to release the domain from the key, so the key can be reused on another site within the plan’s domain limit. Uninstalling or deleting the plugin does not automatically deactivate the license on our server; if you remove a plugin without deactivating first and later need the domain slot freed, contact us at info@bizsensei.co.in and we will release it after verifying your purchase.

8. Payment Information

Payments in our Store are processed in Indian Rupees (INR) through Razorpay, our payment processing partner. We deliberately structured checkout so that sensitive payment credentials never touch our servers. This section explains Razorpay’s role, what payment-related information we do receive, and what we never see.

8.1 Razorpay’s Role

When you click through to pay, the card number, expiry, CVV, UPI ID or VPA, UPI PIN, net-banking credentials, and wallet authentication details are entered on Razorpay’s secure checkout interface and transmitted directly to Razorpay’s systems over an encrypted connection. Razorpay processes the transaction with your bank or payment network and returns the result to our Store. Razorpay acts as an independent Data Fiduciary for the payment credentials it collects, and its handling of that data is governed by Razorpay’s own privacy policy and terms, which we encourage you to read before paying.

We chose this arrangement precisely so that we do not become a custodian of your payment credentials. Our servers never receive, log, or proxy the raw card or UPI data; there is no field, log file, or database table on our side that holds it. If you contact our support about a payment, we will never ask you for your full card number, CVV, or UPI PIN — and you should not volunteer them. Anyone asking for those details while claiming to be us is not us; please report it to info@bizsensei.co.in immediately.

8.2 What We Receive

After Razorpay completes (or fails) a transaction, it notifies our Store with a limited set of non-sensitive data: the payment status (success, failure, or pending), the Razorpay payment ID and order reference, the amount and currency (INR), the payment method type (for example, “card”, “UPI”, or “netbanking” — without the underlying credentials), the last four digits of a card where the network provides them for receipt purposes, the billing name, email, phone number, and address you entered, and timestamps. We store this with your WooCommerce order so we can fulfil it, issue your license, send your receipt, reconcile our accounts, and help you if a payment goes wrong.

Failed or abandoned payments are also recorded (status, amount, timestamp, and the contact details entered) so we can distinguish a genuine failure from an incomplete checkout and assist you in retrying. We do not use failed-payment data for marketing.

8.3 What We Never See or Store

We never receive or store: full card numbers, CVVs, card PINs, UPI PINs, net-banking passwords or OTPs, or wallet credentials. We cannot retrieve them, we cannot look them up for you, and a data request to us under Section 15 will not return them because they were never in our possession.

Because payment credentials live only with Razorpay (and your bank), questions about how Razorpay stores, retains, or protects those credentials — including deletion requests directed at the credentials themselves — should be addressed to Razorpay under its own policy. What you can ask us about is everything listed in Section 8.2: your order records, receipts, and the billing contact details held in our Store, which we will provide, correct, or erase in line with your rights and our retention duties.

9. Cookies & Similar Technologies

A cookie is a small text file a website asks your browser to store so the site can remember you between visits. We also use functionally similar technologies: local storage (data a site stores in your browser), session identifiers (temporary tokens that keep you logged in or keep your cart intact while you browse), and server logs (described in Section 3.1). We do not use fingerprinting techniques designed to identify you without a cookie.

We keep our cookie footprint deliberately small. The table below lists every category we use, what each one does, and how long it typically lasts. Where consent is required, we ask for it before setting anything beyond the strictly necessary category.

9.1 Strictly Necessary Cookies

These are essential for the Website and Store to function and are set without asking, because the service you requested cannot work without them. They include: WordPress session cookies that keep you logged in to your Store account or to wp-admin; WooCommerce cart and checkout cookies that remember what is in your cart and preserve checkout state between pages; security cookies used to validate forms and prevent cross-site request forgery (including the nonces on our settings and checkout forms); and a cookie-consent record itself, which remembers the choices you made in our consent banner so we do not ask you on every visit.

Strictly necessary cookies are first-party (set by bizsensei.co.in), contain no advertising identifiers, and typically expire when you close your browser (session cookies) or within days to weeks for persistent login sessions. Blocking them in your browser will break core functions such as logging in, checking out, and completing a purchase.

9.2 Functional Cookies

Functional cookies remember choices you make so the site is more convenient on your next visit — for example, your preferred currency display or the dismissal state of non-essential notices. We use very few of these, all first-party, and none of them track you across other websites. They are set only after you accept them in our consent banner (or if your browser signals acceptance through its own settings).

Because these cookies exist purely for your convenience, you can decline them with no loss of core functionality; the site simply will not remember those preferences next time. You can change your mind at any time through the cookie settings link in the Website footer or your browser’s own controls, as described in Section 9.4.

9.3 Analytics & Performance Cookies

If you consent, we use privacy-respecting analytics to understand aggregate usage of the Website: which pages are visited, how visitors arrive, and where they drop off, so we can fix broken pages and improve content. Where we use a third-party analytics service, it sets its own cookies and processes the resulting data under its own terms; we configure such services to anonymise or truncate IP addresses where the option exists and we do not combine analytics data with your Store account or order history to build individual profiles.

Analytics cookies are never used for advertising, never shared with ad networks, and never used to make automated decisions about you. Declining them has no effect on your ability to use the Website or Store — you simply will not be counted in our aggregate statistics. If you have previously consented and want to withdraw, Section 9.4 explains how; withdrawal stops future collection but does not retroactively delete already-aggregated statistics, which contain no personal data.

9.4 Managing Your Cookie Choices

You control cookies in three ways. First, our consent banner: on your first visit we ask you to accept or decline non-essential cookies, and a “Cookie Settings” link in the footer lets you revisit that choice at any time. Second, your browser: every major browser lets you block, delete, or restrict cookies site-by-site through its settings or preferences menu — consult your browser’s help pages for the exact steps. Third, “Do Not Track” and Global Privacy Control signals: where we can detect them, we treat them as a refusal of non-essential cookies.

Please note that cookie preferences are stored per browser and per device, so a choice made on your phone does not carry over to your laptop. Clearing your browser’s cookies will also clear the record of your consent choice, and the banner will appear again on your next visit. If you block strictly necessary cookies, parts of the Website — including login, cart, and checkout — will not work, and that is a technical consequence, not a penalty.

10. How We Use Information

We use personal data only for the specific purposes listed below. Under the DPDP Act, each purpose rests on a lawful basis — primarily your consent (given when you submit a form, place an order, or accept a notice), and in some cases a legitimate use recognised by law (such as complying with a legal obligation or protecting our systems). We never repurpose your data for an unrelated use without first obtaining fresh consent or confirming another lawful basis.

10.1 Operating the Website & Store

We use technical and account data to keep the Website and Store running: serving pages, maintaining login sessions, preserving cart contents through checkout, processing search queries, and remembering your cookie preferences. Lawful basis: consent given by using the service, and our legitimate interest in operating a functional website.

10.2 Processing Orders & Delivering Products

We use your order details to create your Store account (if any), process your payment via Razorpay, generate your invoice and receipt, attach the correct downloadable product files to your order, and issue your software license key. Without this data we cannot sell or deliver anything. Lawful basis: your consent at checkout and the performance of the sales contract.

10.3 License Validation, Updates & Support Entitlements

We use the license telemetry described in Section 7 to validate activations, enforce per-plan domain limits, detect key abuse, offer the correct updates to entitled sites, and confirm support eligibility when you contact us. Lawful basis: the license agreement with you and our legitimate interest in preventing piracy of our software.

10.4 Responding to Enquiries & Providing Support

We use your contact details and correspondence to answer your questions, diagnose and fix reported issues, follow up on open tickets, and — where you have asked us to — log into your site temporarily to resolve a problem. Lawful basis: your consent when you contact us, and the performance of our support obligations for paying customers.

10.5 Delivering Agency Services

For agency clients, we use the access and data you provide to execute the agreed scope: managing ad campaigns, building or maintaining websites, running SEO and analytics, and operating retention campaigns. We use project communications to coordinate work, track decisions, and bill accurately. Lawful basis: your consent and the performance of the services contract.

10.6 Security, Fraud Prevention & Diagnostics

We use server logs, license check records, and payment status data to detect and block attacks, abuse, and fraud (for example, brute-force login attempts, stolen-card testing, or license key sharing rings), to diagnose errors, and to keep audit trails of administrative actions. Lawful basis: our legitimate interest in protecting our systems, our customers, and our business, and compliance with legal duties to maintain reasonable security safeguards.

10.7 Legal, Tax & Compliance Obligations

We use order, invoice, and payment records to maintain books of account, file tax returns, respond to lawful requests from authorities, and enforce or defend our legal rights. Lawful basis: legitimate use — compliance with obligations under applicable Indian law, including taxation and record-keeping statutes.

10.8 Service Communications (Non-Marketing)

We send transactional messages you need as a customer: order confirmations, payment receipts, license keys and activation instructions, security alerts (such as password resets), critical product notices (for example, a mandatory security update), and responses to your support tickets. These are part of the service, not marketing, and are sent on the basis of your purchase or enquiry. You cannot opt out of genuinely transactional messages while you remain a customer, because without them we cannot deliver what you paid for. Marketing messages are handled separately in Section 17 and always offer an opt-out.

11. How We Share Information

We share personal data only when there is a concrete reason to do so, only the minimum necessary for that reason, and only with parties bound to protect it. This section lists every sharing scenario. If a situation is not listed here, we do not share your data in that situation.

11.1 Service Providers (Data Processors)

We engage a small number of service providers who process data on our behalf and on our instructions: (a) Web hosting — our Website, Store, and license server run on hosting infrastructure (currently Hostinger), which necessarily stores the databases and files containing the data described in this Policy; (b) Razorpay — processes payments as described in Section 8 and acts independently for payment credentials; (c) Email delivery — transactional emails (order confirmations, license keys, password resets) are sent through our hosting mail infrastructure or a reputable email delivery service, which processes recipient addresses and message content solely to deliver the mail; (d) Meta — only in the WhatsApp Connect flow described in Section 6, where Meta acts independently rather than as our processor.

Every processor we engage is required by contract to process data only on our documented instructions, to keep it confidential, to apply appropriate security measures, and to delete or return it when the engagement ends. We do not engage processors for advertising, data brokerage, or profiling, and we review our provider list whenever we change infrastructure.

11.2 Legal Requirements & Protection of Rights

We disclose personal data where we are legally required to do so: in response to a court order, a binding direction from a competent authority, or a valid legal process under Indian law; to comply with tax, accounting, and record-keeping obligations; and to the Data Protection Board of India or other regulators where the DPDP Act or another statute requires notification or cooperation.

We may also disclose data where reasonably necessary to protect our rights and the safety of others: to investigate and prevent fraud, abuse, or attacks on our systems; to enforce our Terms & Conditions and license agreements; and in an emergency where disclosure is needed to prevent harm. Where the law permits, we will notify you of such a disclosure unless we are prohibited from doing so or notification would prejudice an investigation.

11.3 Business Transfers

If BizSensei Digital is ever involved in a merger, acquisition, asset sale, or similar business transfer, the personal data we hold may be transferred to the acquiring party as part of the business assets. Should that happen, we will notify affected customers in advance (by email and a Website notice) and the acquiring party will be required to honour this Policy or obtain your fresh consent for any materially different use. There are no such transactions planned or underway as of the last update date of this Policy.

11.4 What We Never Do

For the avoidance of doubt: we do not sell your personal data to anyone, for any price, under any label — not to advertisers, not to data brokers, not to “partners”. We do not rent your contact lists, we do not trade license-holder data, and we do not share your data with third parties for their independent marketing. We do not use your data to train machine-learning models for third parties. Analytics, where used, is aggregate and never sold or shared in identifiable form. If our business model ever changed to include any form of data sale — which we have no intention of doing — we would seek your explicit opt-in consent first, as the DPDP Act requires for any new purpose.

12. Data Retention

We keep personal data only as long as necessary for the purpose it was collected, and then we delete it or anonymise it so it can no longer identify you — unless a law requires us to keep it longer, or you ask us to keep it (for example, to preserve your license record). The schedules below are our standard practice; individual circumstances, such as an ongoing dispute, may extend retention, and we will tell you if that happens.

12.1 Store Orders, Invoices & Licenses

Order records, invoices, payment references, and license records are retained for 8 years from the financial year of the transaction, in line with Indian tax and accounting record-keeping requirements. License keys remain associated with your customer record for as long as the license is active (our current plans are lifetime) plus the accounting retention period, so we can reissue keys, verify entitlements, and provide support. Download logs (which file version you downloaded and when) are kept for 2 years for abuse investigation and then deleted.

12.2 Support Tickets & Communications

Support correspondence, including emails, chat transcripts, and call notes, is retained for 3 years after a ticket is closed, so we can recognise recurring issues and maintain continuity if you contact us again. Any temporary admin or server access credentials you share for a support session are deleted immediately after the session ends, and we do not retain copies of your site’s customer or business data viewed during support.

12.3 Website Logs & Analytics

Web server access and error logs are rotated and deleted after 90 days, unless a specific log range must be preserved as evidence of an attack or abuse incident (in which case it is kept until the investigation closes). Aggregated analytics contain no personal data and may be kept indefinitely. Cookie-consent records are kept for 2 years as proof of the choice you made.

12.4 Agency Client Records

Contracts, proposals, invoices, and project correspondence are retained for 8 years for tax and legal purposes. Working files containing personal data accessed during an engagement (such as exported reports) are deleted or returned to you within 90 days of project completion unless you ask us to keep them. Access credentials you granted us (ad accounts, analytics, social logins) are revoked or handed back at project end, and any OAuth tokens are invalidated.

12.5 Marketing Data

Newsletter subscriber details are kept until you unsubscribe, plus a 30-day suppression record afterwards so we honour the opt-out. Contact-form enquiries that do not convert into a business relationship are deleted after 2 years. If you withdraw consent for marketing, we stop processing your data for marketing immediately and delete it within 30 days, keeping only the suppression record described above.

12.6 When Consent Is Withdrawn or Purpose Ends

When you withdraw consent or the purpose of processing is fulfilled and no legal duty requires retention, we delete the relevant personal data within 30 days and instruct our processors to do the same. Deletion means removing the data from live systems; residual copies in encrypted backups age out on the backup rotation cycle (maximum 90 days) and are not restored except for disaster recovery. Where complete erasure is technically impossible — for example, data embedded in a signed financial record we must retain — we isolate and minimise it instead, and explain this to you in our response.

13. Data Security

We apply reasonable security safeguards appropriate to the sensitivity of the data we hold, as the DPDP Act requires. No system is perfectly secure, and we will not claim otherwise — but the measures below describe concretely what we do to protect your data, and what we do when something goes wrong.

13.1 Encryption in Transit & at Rest

All traffic between your browser and our Website, Store, and license server travels over TLS (HTTPS) — look for the padlock in your browser’s address bar. License validation requests from our plugins use HTTPS exclusively; the licensing client will not fall back to plain HTTP. Passwords for Store accounts and WordPress admin access are stored as one-way cryptographic hashes, never in plain text, so even we cannot read them. Database backups are encrypted, and access to backup storage requires separate credentials from day-to-day admin access.

13.2 Access Controls

Access to systems holding personal data is limited to the people who need it for their work, and each person has an individual account — there are no shared admin passwords. Administrative access requires strong, unique passwords and, where supported, two-factor authentication. We review who has access whenever team responsibilities change and remove access promptly when it is no longer needed. Support staff accessing a customer’s site do so with temporary credentials the customer provides, for the reported issue only, and those credentials are discarded afterwards.

13.3 Software Updates & Maintenance

We keep our server operating system, web server, PHP runtime, WordPress core, WooCommerce, and all plugins updated with security patches, and we monitor vendor security announcements for the software we depend on. Our own plugins are built with standard WordPress security practices: capability checks on admin actions, nonces on forms, prepared statements for database queries, and output escaping. When we discover a security issue in our own code, we ship a fix and, where the issue could have exposed customer data, we notify affected customers directly.

13.4 Backups & Recovery

We maintain regular encrypted backups of the Website, Store database, and license server so we can recover from hardware failure, corruption, or attack. Backups are stored separately from live systems with restricted access, retained on a rolling cycle (maximum 90 days), and tested periodically to confirm they actually restore. Backup media is wiped or destroyed when retired.

13.5 Breach Notification

If we discover a personal data breach — unauthorised access to, loss of, or disclosure of personal data we hold — we will assess its scope, contain it, and notify the Data Protection Board of India and each affected Data Principal in the manner and within the timelines the DPDP Act and its rules prescribe. Our notification to you will describe what happened, what data was involved, what we have done about it, and the steps you can take to protect yourself. We will not hide breaches, delay notification to manage appearances, or ask you to keep a breach confidential where the law requires disclosure.

14. International Data Transfers

Our servers, our team, and our primary operations are in India, and the personal data we hold as Data Fiduciary is stored in India. However, some processing necessarily involves parties or infrastructure outside India, and this section explains when that happens and what protects your data when it does.

14.1 When Transfers Occur

Cross-border transfers in our setup are limited and specific: (a) WhatsApp notifications sent through the store owner’s Meta WhatsApp Cloud API app are routed through Meta’s global infrastructure, which operates outside India — see Section 6; (b) payment processing through Razorpay may involve card networks and banks with systems outside India, under Razorpay’s own arrangements — see Section 8; (c) if we use an email delivery or analytics provider whose infrastructure spans regions, message or analytics data may transit or be stored outside India under that provider’s terms; (d) our own hosting and license server are India-based, so license telemetry and Store data stay in India.

We do not transfer personal data to any country or territory that the Central Government has specifically restricted by notification under the DPDP Act. If such a restriction is notified in future, we will adjust our providers and flows to comply before the restriction takes effect.

14.2 Safeguards for Transfers

Where a transfer outside India occurs, it is protected by one or more of the following: the transfer is necessary to perform your contract with us (for example, delivering a WhatsApp order notification you asked the store to send); it happens under the third party’s own published terms and certifications, which we review before engaging them; or it is covered by contractual clauses requiring the recipient to protect the data to a standard consistent with the DPDP Act. We keep transfers to the minimum the service requires — for instance, we do not mirror our customer database to servers abroad for convenience.

If you have questions about a specific transfer — for example, which provider handles a particular data flow and where they process it — write to info@bizsensei.co.in and we will give you a straight answer.

15. Your Rights as a Data Principal

Under the DPDP Act, you — the Data Principal — have specific rights over your personal data. We honour all of them, and exercising them is free. This section explains each right, how to exercise it, and what to expect from us. To exercise any right, email info@bizsensei.co.in from the email address associated with your account or enquiry, tell us which right you are exercising and what you want, and we will verify your identity before acting (usually by confirming control of that email address, and occasionally by asking for an order number or license key).

We respond to rights requests within the timelines the DPDP Act’s rules prescribe. If we need more time because a request is complex, we will tell you why and when to expect a complete response. If we must refuse or limit a request — for example, because a law requires us to retain the data — we will explain the reason and the legal basis in plain language, not in jargon.

15.1 Right to Access Information

You have the right to know what personal data we hold about you. On request, we will provide a summary of the personal data we are processing, the purposes for which we process it, and the categories of third parties with whom we have shared it. For Store customers this typically means your account details, order history, license records, and support correspondence. We provide this in a clear, readable format — not a raw database dump — and we will explain any field that is not self-evident.

15.2 Right to Correction

If any personal data we hold about you is inaccurate, incomplete, or out of date, you have the right to have it corrected, completed, or updated. You can correct most account and billing details yourself from your Store account page; for anything you cannot change yourself — for example, a misspelled name on an issued invoice — email us and we will fix it promptly and confirm once done. Where we have shared the incorrect data with a processor, we will pass the correction on.

15.3 Right to Erasure

You have the right to ask us to erase your personal data. When you do, we delete it in line with Section 12.6, unless we must retain specific records under a legal obligation (such as tax invoices) — in which case we delete everything we are permitted to delete, isolate what we must keep, and explain exactly what was kept and why. Erasure of your Store account does not erase records the law requires us to keep, and it does not affect data held by independent third parties such as Razorpay or Meta, whom you must contact separately for their own records.

Please note the practical consequence: if you ask us to erase the data tied to an active license, we will no longer be able to reissue your key, verify your entitlement to updates, or provide support for that purchase, because we will have no record that it was yours. We will warn you of this before completing an erasure request linked to an active license.

15.4 Right to Nominate

Under the DPDP Act you may nominate another individual to exercise your rights in the event of your death or incapacity. To register a nominee with us, email info@bizsensei.co.in with your account details and the nominee’s full name and contact information. We will record the nomination against your customer record. A nominee exercising rights on your behalf will need to provide proof of identity and of the event triggering the nomination before we act.

15.5 Right to Grievance Redressal

If you have any complaint about how we handle your personal data — including a complaint that we have not responded to a rights request, or that our response was inadequate — you have the right to a working grievance redressal mechanism, and this is it. Contact our grievance officer at info@bizsensei.co.in (phone: +91 93726 65745) with the subject line “Privacy Grievance” and a description of the issue, including any earlier correspondence so we can trace it.

We acknowledge every grievance within 48 hours and resolve it within the timelines prescribed under the DPDP Act’s rules, keeping you informed of progress. If you remain dissatisfied after our final response, you may approach the Data Protection Board of India under the DPDP Act’s appeal process. We will cooperate with the Board fully and will never penalise you for raising a grievance or approaching the Board.

15.6 Withdrawing Consent

Where our processing is based on your consent, you may withdraw that consent at any time — as easily as it was given. For marketing consent, use the unsubscribe link in any message or the method in Section 17. For other consent-based processing, email info@bizsensei.co.in stating what you are withdrawing consent for. Withdrawal takes effect prospectively: processing that already happened while consent was valid remains lawful, but we stop the relevant processing going forward and delete or anonymise the data within 30 days unless another lawful basis (such as a legal retention duty) applies.

Withdrawing consent for processing that is essential to a service — for example, withdrawing consent for us to hold your billing details while you hold an active license — may mean we can no longer provide that service, and we will tell you so honestly before you confirm. We will never make a service conditional on consent for unrelated processing.

16. Children’s Privacy

Our Website, Store, plugins, and Services are intended for adults conducting business — restaurant owners, store operators, and marketing decision-makers — not for children. We do not knowingly collect personal data from children, we do not offer child-directed content, and we do not engage in behavioural monitoring or targeted advertising directed at children.

16.1 Under-18 Data

Under the DPDP Act, a child is an individual below 18 years of age, and processing a child’s personal data requires the verifiable consent of a parent or lawful guardian, with additional prohibitions on tracking, behavioural monitoring, and targeted advertising. Because our offerings are business tools, we do not design any flow that would collect a child’s data, and our checkout and account creation are presented as adult transactions.

If you are under 18, please do not create a Store account, make a purchase, or submit personal data through our forms; ask a parent or guardian to act on your behalf. If you are a parent or guardian and believe your child has provided us with personal data, contact us immediately at info@bizsensei.co.in and we will delete it promptly after verifying the relationship.

16.2 Data We May Encounter Indirectly

There is one indirect path by which children’s data could reach systems we touch: a business using our plugins might collect data relating to children in the course of its own operations (for example, a restaurant’s delivery order placed for a family). That data belongs to the business as Data Fiduciary, lives on the business’s own servers, and is never transmitted to us — see Sections 4 and 5. We have no visibility into it and no ability to screen it, which is why each plugin’s non-access commitment matters. If a support session ever exposes such data to us, we treat it with the same confidentiality as all support data and delete any copies once the session ends.

17. Marketing Communications & Opt-Out

We send marketing communications only with your consent or where you are an existing customer and the message concerns similar products or services — and every marketing message gives you a simple way to stop receiving more. We do not buy email lists, we do not harvest addresses from the web, and we do not add support correspondents to marketing lists without asking.

17.1 What Marketing We Send

Our marketing consists of: occasional newsletters about BizSensei products, features, and offers; announcements of new plugin releases or major updates; and, rarely, information about agency Services that may interest Store customers. We do not send marketing by automated calling, we do not use your data for third-party advertising, and we do not share your contact details with anyone for their marketing — ever. Marketing messages are distinguishable from the transactional service messages described in Section 10.8, which are not marketing and do not contain an opt-out.

17.2 Opting Out

Every marketing email contains a one-click unsubscribe link that takes effect immediately for future sends; you do not need to log in or give a reason. You can also opt out at any time by emailing info@bizsensei.co.in with the subject “Unsubscribe” from the address you want removed. We process opt-outs within 48 hours and keep a suppression record (your address plus the date of the opt-out) for 30 days to a maximum of one year solely to ensure we do not contact you again — the suppression record itself is never used for marketing.

Opting out of marketing does not opt you out of transactional messages about your orders, licenses, or support tickets, because those are necessary to deliver what you paid for. If you want no contact from us at all, that is effectively a request to close your customer relationship, which we will handle as an erasure request under Section 15.3 with the consequences explained there.

18. Changes to This Policy

Privacy law, our products, and our providers evolve, so this Policy will change from time to time. When it does, we update the “Last updated” date at the top of the page and publish the revised Policy on this page. We will never reduce your rights or expand our use of your data without telling you first.

18.1 How We Notify You

For material changes — for example, a new purpose of processing, a new category of data shared, or a change in retention that affects you — we notify Store customers and subscribers by email at least 15 days before the change takes effect, and we show a notice on the Website. The notice explains what changed and why, in plain language, with a link to the previous version on request. For non-material changes — clarifications, typo fixes, updated contact details, or reflecting a provider swap with equivalent protections — we update this page and note the new date without separate email.

If you do not agree with a material change, you may close your account and exercise your erasure rights under Section 15.3 before the change takes effect. Continuing to use the Website, Store, or our plugins after a notified change takes effect constitutes acknowledgement of the revised Policy for future processing; it does not retroactively authorise new uses of data collected earlier.

18.2 Reviewing Past Versions

We maintain an internal version history of this Policy. If you need to know what the Policy said on a particular date — for example, in connection with a dispute about processing that occurred then — email info@bizsensei.co.in and we will provide the relevant version. The current version is always the one published at bizsensei.co.in/privacy/.

19. Contact Us

If you have any question about this Policy, about your personal data, or about how to exercise your rights, please contact us — a real person reads these messages. Email is the fastest channel; phone is available during Indian business hours.

19.1 General Privacy Questions

Email: info@bizsensei.co.in

Phone: +91 93726 65745

Website: https://bizsensei.co.in

We aim to acknowledge privacy queries within 2 business days and to give a substantive response within 7 business days. If your query is complex, we will tell you and keep you updated. Please do not send sensitive credentials (passwords, full card numbers, API secrets) by email; if we need them for support, we will arrange a secure way to receive them.

19.2 Grievance Officer

For grievances under the DPDP Act — including complaints about our response to a rights request — contact: info@bizsensei.co.in with the subject line “Privacy Grievance”, or call +91 93726 65745. This is the same channel described in Section 15.5. We acknowledge grievances within 48 hours and resolve them within the statutory timelines. If our final response does not satisfy you, you may escalate to the Data Protection Board of India, and we will cooperate with the Board fully.