Privacy Policy
Version 2026-10-23Last updated: 23 October 202622,975 words
Welcome to the Privacy Policy of BizSensei Digital. This policy explains, in plain and complete terms, what personal data BizSensei Digital collects, why it collects that data, how it uses, stores, shares and protects that data, how long it keeps that data, and what rights you have in relation to that data. It applies across the BizSensei ecosystem of websites, portals, applications and services, and it is organised so that a general part states the rules that apply everywhere, followed by a dedicated part for each property that adds the details specific to that property. Where a property specific part and the general part both speak to the same matter, both should be read together, and the more specific statement should be understood as adding detail rather than removing a protection stated in the general part.
BizSensei Digital is the data fiduciary for personal data collected through its own properties, which means BizSensei Digital determines the purpose and means of processing that data and is responsible for processing it lawfully, fairly and in accordance with this policy and applicable law. The laws of India govern this policy. BizSensei Digital can be contacted by email at info@bizsensei.co.in and by phone at +91 93726 65745. BizSensei Digital does not publish a physical address and communicates with data principals, customers, clients and visitors by email, phone and through its websites and portals. Version 2026-10-23. Last updated: 23 October 2026. This version replaces all earlier versions of this Privacy Policy from the date stated, and the closing provisions at the end of this document explain how future changes will be notified and when they will take effect.
Please read this policy fully before you provide personal data to BizSensei Digital, create an account, place an order, subscribe to a newsletter, post a comment, use a free tool, submit a form, or use any application or portal operated by BizSensei Digital. By understanding this policy you will know what to expect when BizSensei Digital handles your personal data, how to exercise your rights, how to raise a grievance, and which business is responsible for your data when BizSensei Digital acts only as a processor for a restaurant, pharmacy, clinic or other client business. Nothing in this policy limits a data principal's statutory rights under the Digital Personal Data Protection Act, 2023, and if any statement in this policy is ever read in a way that conflicts with a statutory right, the statutory right prevails.
Part A: General
Applies to: All BizSensei Digital properties
1. Who we are and the role we play
BizSensei Digital is a digital services and software business operating websites, a store, an agency services practice, a blog, restaurant software known as BizSensei OMS, and a healthcare product known as Qiaomed that is currently in pre-launch. In this policy, the words we, us and our refer to BizSensei Digital. The words you and your refer to the individual whose personal data is being processed, who may be a visitor, a customer, a client contact, a newsletter subscriber, a blog commenter, a restaurant owner or staff member, a food ordering customer, a rider, a patient, a practitioner, or any other person interacting with a BizSensei property.
For personal data collected directly through BizSensei Digital's own properties, including contact forms, checkout flows, account registration on BizSensei owned portals, newsletter subscriptions, support conversations and free tool submissions, BizSensei Digital acts as data fiduciary under the Digital Personal Data Protection Act, 2023. That means BizSensei Digital decides why the data is needed, what data is needed, and how it will be handled, and BizSensei Digital is accountable for that handling.
In some situations BizSensei Digital acts only as a data processor. This happens most clearly inside BizSensei OMS and Qiaomed, where a restaurant, cafe, pharmacy, clinic or other business uses BizSensei software to serve its own customers or patients. In those situations the business that collected the end customer's or patient's data is the data fiduciary for that data, and BizSensei Digital processes the data only on that business's instructions, for the purpose of providing the software and related services. Part F and Part G of this policy explain that division of responsibility in detail, including how end customers and patients can exercise their rights through the business they dealt with directly, with assistance from BizSensei Digital where needed.
A third role arises in agency work. When a client engages BizSensei Digital to run marketing, retention, email or WhatsApp campaigns, the client supplies or approves the contact lists and campaign content, and BizSensei Digital processes that contact data on the client's instructions as processor for campaign delivery, while remaining fiduciary for its own client relationship data such as the client's own contact persons, billing contacts and project communications. Part D explains this arrangement and the warranty each client gives that its lists were lawfully collected.
2. Legal framework
This policy is written to comply with the Digital Personal Data Protection Act, 2023, referred to in this policy as the DPDP Act, together with the rules made under that Act as and when they are in force. It also takes account of the Information Technology Act, 2000 and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011, referred to as the SPDI Rules, insofar as they remain applicable, and of the Consumer Protection (E-Commerce) Rules, 2020 for grievance handling in relation to the BizSensei store. Where other Indian laws impose specific duties, for example tax and accounting laws that require order records to be kept, or medical laws and professional obligations that apply to healthcare practitioners using Qiaomed, those laws apply alongside this policy and are noted in the relevant part.
BizSensei Digital does not claim the status of a significant data fiduciary. If the Government of India notifies a class of fiduciaries as significant data fiduciaries and BizSensei Digital were ever brought within such a notification, BizSensei Digital would comply with the additional obligations that follow from that status and would update this policy accordingly. Until any such notification applies, references in this policy to the obligations of a data fiduciary should be read as the general obligations under the DPDP Act.
Certain words used in this policy carry the meanings given by the DPDP Act. Personal data means any data about an individual who is identifiable by or in relation to such data. A data principal is the individual to whom the personal data relates, and where that individual is a child, the term includes the parent or lawful guardian of the child for the purposes stated in the Act. A data fiduciary is a person who determines the purpose and means of processing personal data. A data processor is a person who processes personal data on behalf of a data fiduciary. Processing includes collection, recording, organisation, structuring, storage, adaptation, retrieval, use, alignment, disclosure, erasure and destruction, whether by automated means or otherwise. Consent means a free, specific, informed, unconditional and unambiguous indication of agreement by clear affirmative action, signifying agreement to processing for a specified purpose and limited to such personal data as is necessary for that purpose.
3. Basis for processing: notice and consent, and legitimate uses
The primary basis on which BizSensei Digital processes personal data is notice and consent. Before or at the time personal data is collected through BizSensei Digital properties, you are given notice of the personal data proposed to be collected, the purpose for which it is proposed to be processed, the manner in which you may exercise your rights, and the manner in which you may make a complaint to the Data Protection Board of India. This Privacy Policy, together with the specific notice shown at each collection point, together constitutes that notice. A consent gate used across BizSensei websites requires you to review and accept the applicable legal documents before information is taken, and the system records the documents and versions you accepted, as described further in the consent records clause below.
Where consent is the basis for processing, BizSensei Digital will request consent in clear and plain language, limited to the personal data necessary for the specified purpose. You may give, manage, review or withdraw consent through the Consent Manager or contact mechanism made available for the relevant property, or by writing to info@bizsensei.co.in. The ease with which consent may be withdrawn will be comparable to the ease with which it was given. Withdrawal of consent does not affect the lawfulness of processing done before withdrawal, and does not affect processing that is required by law to continue, for example the retention of tax records after a purchase consent is withdrawn.
The DPDP Act also recognises certain legitimate uses for which personal data may be processed without consent. BizSensei Digital acknowledges those legitimate uses and relies on them only where they genuinely apply. They include processing for a purpose for which the data principal has voluntarily provided personal data and has not indicated that she or he does not consent to its use for that purpose, processing by the State for sovereignty, security and public order functions which do not apply to BizSensei Digital as a private business, processing to respond to a medical emergency involving a threat to life or health, processing to provide safeguards or services during an epidemic, outbreak of disease or other threat to public health, processing to ensure safety of or prevent damage to property during a disaster or breakdown of public order, and processing for purposes related to employment or safeguarding an employer from loss or liability. Where BizSensei Digital provides data you voluntarily submitted in order to answer your own enquiry, fulfil your own order, or deliver a service you requested, that processing is understood as necessary to give effect to your voluntary act and, in parallel, is covered by the consent and notice given at the collection point.
BizSensei Digital will not process personal data for a purpose that is incompatible with the purpose stated in the notice given at collection, unless a fresh notice is given and, where consent is the basis, fresh consent is obtained, or another lawful basis clearly applies and is recorded. If a new product feature would require a materially new use of existing personal data, the feature will not be applied to existing data until the required notice and consent steps have been completed.
4. What we collect when you contact us, chat or order
When someone contacts BizSensei Digital, chats with the Sensei assistant, submits an enquiry form, requests a callback, asks for a quotation, or places an order, we collect name, email, phone and order details, together with the content of the message or conversation and any further details the person chooses to provide in order to explain the enquiry or complete the order. This harvested commitment is a core part of our practice: those four categories, name, email, phone and order details, form the standard dataset for direct contact and ordering, and we do not require unrelated personal data as a condition of answering an enquiry or accepting an order.
The purposes for which that contact and order data is used are fulfilling orders, delivering licence keys, providing support, and sending product updates only on opt-in. An order cannot be fulfilled without a name and contact channel for delivery and communication, a payment cannot be reconciled without order details, a licence key cannot be delivered without an email address or account, and support cannot be provided without knowing what was ordered and what problem arose. Product updates, newsletters and promotional messages are separate from those necessary purposes and are sent only where you have opted in, as explained in the marketing clause below.
We do not sell personal data. That commitment is absolute across all BizSensei properties. Personal data is not sold to advertisers, data brokers, list traders or any other third party, and it is not rented or exchanged for consideration as a commercial list. Sharing, where it happens, is limited to processors needed to operate the service, as described in the sharing clause, and to disclosures required by law, as described in the government and legal requests clause.
5. Data minimisation and purpose limitation
BizSensei Digital practises data minimisation. Only personal data that is necessary for the stated purpose is collected, only persons and systems that need access for that purpose are given access, and data is not retained in identifiable form for longer than the retention rules in this policy allow. Forms are designed to request the fields needed for the transaction in question. Optional fields are marked or presented as optional where the interface allows, and leaving an optional field blank will not prevent you from completing the core transaction.
Purpose limitation applies in parallel. Data collected to fulfil an order will not be repurposed as a general marketing list unless you have opted in to marketing. Data collected to provide support will not be used to profile you for unrelated advertising. Data collected through a free tool for the purpose of delivering the tool result will not be silently added to a sales list beyond the follow up described at the tool collection point. Data that a food ordering customer writes voluntarily in order notes, which may on occasion contain sensitive information such as an allergy note or a health related instruction, is used only for that order, is visible only to those who need it to prepare and deliver that order, and is not extracted for any other purpose.
6. Master data inventory schedule
The table below is the master data inventory schedule for the BizSensei ecosystem. It lists each major category of personal data, examples within the category, the usual source of the data, and the main purposes for which the category is processed. Each property specific part adds the inventory details that belong only to that property. If a category does not apply to a particular property, the property part will not list it, and its absence there means BizSensei Digital does not collect that category through that property in the ordinary course.
| Category | Examples | Usual source | Main purposes |
|---|---|---|---|
| Account data | Name, account identifier, username, account type, account status, registration date, role within a business account, hashed password or authentication token state | You, when you register; the business that invites you to its account | Creating and operating accounts, authentication, authorisation, account security, account administration |
| Contact data | Email address, mobile number, alternative phone number, preferred contact channel, communication language preference where you state it | You; a client or business that engages us to contact you on its behalf | Order communication, delivery communication, support, account notices, opted in updates |
| Transactional data | Order details, items purchased, licence keys issued, subscription or plan details, invoices, transaction references, payment status, amount and method type, refund status | You and the payment gateway during a transaction; the ordering system | Fulfilling orders, delivering licences, accounting, tax compliance, dispute handling, refund processing |
| Device and log data | Device type, operating system, browser type, application version, internet protocol address, timestamps, pages visited, features used, error and crash logs, session identifiers | Your device and our systems automatically during use | Operating the service, security, fraud prevention, troubleshooting, performance improvement, audit trails |
| Support conversations | Messages to support, chat transcripts including conversations with the Sensei assistant, call notes, attachments you send, ticket status and resolution notes | You during the conversation; our support team notes | Answering enquiries, resolving problems, training internal quality checks, evidencing advice given |
| Marketing preferences | Opt in status, opt out status, channel preferences, campaign engagement records such as delivery, open or click records where the channel provides them, unsubscribe records | You when you opt in or out; campaign delivery systems | Sending only communications you have agreed to receive, respecting opt outs, measuring campaign delivery |
| Consent records | Documents accepted, document versions, date and time of acceptance, internet protocol address and forwarded address where present, user agent, context of collection, identifier linked to the acceptance | Our consent system automatically at the time of acceptance | Proving that notice was given and consent was obtained, auditing compliance, responding to rights requests |
| Location data | Approximate or precise device location only where a feature requires it and device permission is granted, delivery address, outlet or branch location selected by you | Your device with permission; addresses you type or save | Finding nearby outlets, assigning delivery, live order tracking where the feature is active |
| Business contact data | Name, job title, business name, business email, business phone, role in a project or account | The individual; the business that employs or engages the individual; public business listings where the contact is published for business enquiries | Client relationship management, project delivery, B2B communication, account administration |
| End customer data processed for clients | Food order details, delivery addresses, patient appointment details and other data a business's own customers provide to that business through BizSensei software | The end customer through the business's account; the business itself | Providing the software service to the business as processor, on the business's instructions only |
The inventory above is intended to be exhaustive for ordinary operations. If BizSensei Digital begins collecting a materially new category of personal data through any property, this schedule and the relevant property part will be updated before or at the time the new collection begins, and notice will be given at the new collection point. Experimental or test features that involve personal data are subject to the same rule and will not be launched on live personal data without an updated notice.
7. Sensitive personal data
Certain kinds of information require heightened care. Under the SPDI Rules, sensitive personal data or information includes passwords, financial information such as bank account, credit card, debit card or other payment instrument details, physical, physiological and mental health condition, sexual orientation, medical records and history, and biometric information. The DPDP Act does not create a separate category in the same form, but BizSensei Digital continues to treat passwords, financial information and health data as requiring the highest level of protection in this policy, regardless of the label applied by a particular statute.
Passwords are never stored in readable plain text. Account passwords are stored using hashing, and authentication tokens are handled as secrets. BizSensei Digital staff do not ask you for your password in email, chat or phone support, and you should never share your full password with anyone claiming to act for BizSensei Digital. If you believe your password has been compromised, change it immediately through the account interface and notify us at info@bizsensei.co.in so that sessions can be reviewed.
Financial information in card form stays with the payment gateway. Full card numbers, card verification values, UPI PINs and banking passwords never touch BizSensei servers, as restated in detail in Part C for the store and Part F for food ordering. Gateways handle the sensitive payment instrument data under their own security programmes, and BizSensei Digital retains only transaction references, status, amount and method type, which are sufficient to reconcile payments, issue refunds and answer payment queries, without exposing BizSensei systems to cardholder data.
Health data arises principally in Qiaomed and, incidentally, when a food ordering customer volunteers a health related note with an order. Health data in Qiaomed is handled with consent, purpose limitation, and access restricted to the treating practice and the patient, as set out in Part G. Health related notes volunteered with a food order are handled under the minimisation rule already stated: they are used only for that order. BizSensei Digital does not build health profiles from incidental notes, does not use health data for advertising, and does not sell health data under any circumstances.
BizSensei Digital follows reasonable security practices and procedures for sensitive personal data, of the kind contemplated by the SPDI Rules, including documented information security controls, access management, encryption in transit, and periodic review of those controls. This policy describes those practices generically as an information security programme aligned in spirit with ISO style controls for confidentiality, integrity and availability. BizSensei Digital does not claim ISO certification or any other external certification in this policy, and no statement in this policy should be read as a claim of certification that has not been granted.
8. Sharing and processors
Sharing is limited to what is needed to operate. BizSensei Digital shares personal data only with processors needed to operate, including payment processing, email delivery and hosting, and with other recipients only where a clause in this policy or a legal duty requires it. Every processor that handles personal data on behalf of BizSensei Digital is expected to process it only on documented instructions, to protect it with appropriate security, and to assist BizSensei Digital in meeting its obligations to data principals. Where a processor provides its services under its own terms as an independent provider for part of the processing, for example a payment gateway determining fraud checks on a transaction, that provider's own privacy policy also applies to that part, and you may review it on the provider's website.
The processor schedule below lists the types of processors used across the ecosystem and the data each type ordinarily receives. Individual provider names may change as infrastructure changes, and a change of provider within the same type, on materially equivalent protections, does not change the purposes for which your data is used. If a wholly new type of processor were introduced for a new purpose, the notice for that purpose would be updated before the sharing began.
| Processor type | What it does | Data it ordinarily receives | Why it is needed |
|---|---|---|---|
| Hosting and infrastructure | Provides servers, storage, databases, backups and content delivery for websites, portals and applications | All data stored in the hosted system, encrypted in transit, accessed by the provider only as needed for infrastructure operation | Without hosting, no website, portal or application can operate |
| Payment processing | Processes card, UPI and other payments, confirms payment status, enables refunds | Name, contact details needed for the transaction, amount, transaction reference, payment instrument data entered directly with the gateway | To accept payment securely without BizSensei servers handling card data |
| Email delivery | Sends transactional email, order confirmations, licence delivery, support replies and opted in updates | Email address, name where used in the message, message content | To deliver email reliably and record delivery status |
| SMS and one time password delivery | Delivers verification messages and transactional alerts by SMS or equivalent channel | Mobile number, short message content, delivery status | To verify mobile numbers and deliver time sensitive alerts |
| WhatsApp communication delivery | Delivers order communications and, for agency clients, campaign messages through WhatsApp business messaging channels | Mobile number, message content, delivery and read status where the platform provides it | To send communications on the channel the customer or client has chosen |
| Maps and location services | Provides map tiles, geocoding or distance functions for outlet discovery and delivery features | Location coordinates or address queries needed for the map function, device technical data seen by the tile or map server | To show maps, estimate distance and support delivery assignment |
| Analytics and error reporting within our own systems | Records usage counts, feature performance and crash or error logs for debugging | Device and log data, feature usage events, crash traces without unnecessary personal content | To keep services stable, fix defects and plan capacity |
Beyond processors, BizSensei Digital may disclose personal data to professional advisers, auditors, insurers and legal counsel where reasonably necessary for advice, audit or the establishment, exercise or defence of legal claims, under duties of confidentiality. It may disclose data to a prospective buyer or successor in a business transfer, as described in the business transfer clause. It will disclose data in response to government and legal requests only as described in that clause. In every other case, disclosure requires your consent or another clear lawful basis that is recorded before disclosure.
Third party processors and other recipients have their own policies. BizSensei Digital selects processors with care, but it does not control the internal operations of an independent gateway, network operator or platform. Where a link or integration takes you to a third party service, that service's privacy policy governs data you provide directly to it, and you should review it before proceeding. BizSensei Digital is not responsible for the privacy practices of a third party that you choose to interact with outside BizSensei properties, although it will consider credible reports about a processor's practices when deciding whether to continue using that processor.
9. Consent records and proof of acceptance
This ecosystem logs consent with document versions, internet protocol addresses and timestamps before collecting information. The consent system used across BizSensei websites presents an agreement control that opens the applicable legal documents, requires each document to be accepted, and enables continuation only when all required documents have been ticked. On submission, the server validates the accepted document versions and writes a consent log entry recording the context of collection, the identifier supplied in that context, the documents and versions accepted, the timestamp, the direct internet protocol address and any forwarded address, and the user agent. That log is the evidentiary record that notice was given and consent was obtained for that transaction.
Consent logs are retained as described in the retention schedule. They are used to prove compliance, to investigate a claim that consent was not given, to respond to a data principal who asks what she or he accepted and when, and to ensure that a person who accepted an earlier version of a document is given notice when a materially changed version takes effect for future transactions. Consent logs are not used for marketing profiling and are not sold or shared except with advisers, auditors or a competent authority where disclosure is required for compliance or legal purposes.
Where an older application version or an offline flow cannot present the full consent gate, the transaction may be accepted under the grandfathering approach described at the relevant collection point, but the absence of a consent log entry in such a case does not create a right to process data for new purposes. New purposes always require the full notice and consent steps. If you believe a consent record attributed to you is incorrect, write to info@bizsensei.co.in and the record will be investigated as a grievance and, where appropriate, as a correction request.
10. Cookies and similar technologies
BizSensei properties use cookies and similar technologies for purposes that are explained in the Cookie Policy for the ecosystem, which should be read together with this Privacy Policy. In summary, strictly necessary cookies and session mechanisms keep you signed in, keep a cart or form state, record consent, and protect sessions from misuse. Functional and preference mechanisms remember choices you have made. Where analytics or similar measurement is used on a property, the Cookie Policy and the property part of this policy will say so. The blog part of this policy gives a concrete example: the blog uses a session cookie for administrators and a consent record, and uses no advertising trackers. If you disable cookies in your browser, some features that depend on a session, including sign in and checkout, may not work, although public information pages will ordinarily remain readable.
For full details of cookie names, purposes and lifetimes on each property, please read the Cookie Policy. This Privacy Policy governs the personal data that cookies and similar technologies may collect, store or transmit, and the rights and choices in this policy apply to that data.
11. WhatsApp and email communication data
BizSensei Digital communicates by email and, for certain services, by WhatsApp. The OMS sends order communications by available channels, which may include email, SMS and WhatsApp messages about order confirmation, preparation, dispatch, delivery, cancellation and support follow up for an order you placed or an order your business received. Those transactional communications are generated from order data and communication data, including your name, phone number or email address, order identifier, outlet name, delivery status and message delivery status. Message content and delivery records are retained for the period stated in the retention schedule so that a disputed communication can be checked.
Agency retention work uses email and WhatsApp with client supplied lists, as described in Part D. The same communication data principles apply there: the list is used only for the client's campaign, delivery status is recorded to evidence sending and to honour opt outs, and the list is not added to any BizSensei owned marketing list and is not reused for another client. Where you receive a marketing message through an agency campaign, the business on whose behalf the message was sent is responsible for the lawfulness of the list that included you, and BizSensei Digital will pass any opt out or complaint you send to us on to that business promptly and will suppress your contact from further sends for that campaign once notified.
Communication data also includes the content of emails and messages you send to BizSensei Digital. Those messages may contain any personal data you choose to include. Please avoid sending passwords, full card details, UPI PINs, banking passwords or unnecessary health details in ordinary email or chat, because those channels are not designed to receive such secrets and BizSensei Digital does not need them. If such a secret is sent unsolicited, it will be deleted from the support record where reasonably possible and you will be advised to rotate the secret with the relevant provider.
12. B2B contact data
BizSensei Digital processes business to business contact data for clients, restaurants, pharmacies, clinics, suppliers, partners and prospective business customers. This includes the name, job title, business name, business email and business phone of individuals who act for their organisations in sales discussions, project delivery, support escalation, billing and account management. The purpose is the ordinary conduct of a business relationship: discussing requirements, sending proposals, delivering projects, providing support, issuing invoices and maintaining the relationship.
B2B contact data is obtained directly from the individual, from the individual's organisation, from business cards, proposals and correspondence exchanged in the relationship, and occasionally from a public business listing where the contact is published for business enquiries. It is not obtained by scraping private profiles or by purchasing personal lists. A business contact who no longer wishes to receive business development messages may opt out at any time by replying to the message or writing to info@bizsensei.co.in, and transactional or contractual messages to an active client organisation, such as a billing notice to its nominated billing contact, will continue for as long as the contract requires them.
13. Data of clients' customers where we act as processor
Data of clients' customers in OMS and Qiaomed is governed by a processor relationship. BizSensei acts as a processor on the business's instructions, the restaurant or practice is the responsible fiduciary, end customers exercise rights through that business and BizSensei assists. This means BizSensei Digital will not use a restaurant's customer list to market BizSensei products to those customers, will not use a clinic's patient list for any BizSensei purpose, and will not disclose such data to any other client. Access by BizSensei support staff to a business's end customer data is permitted only where needed to provide support requested by that business, to maintain the system, or to comply with law, and such access is logged and limited in scope and duration.
If you are an end customer or patient and you contact BizSensei Digital directly with a rights request about data held inside a business's account, BizSensei Digital will explain that the business is the fiduciary for that data, will forward your request to that business without undue delay where we can identify it, and will assist the business in responding. In cases where the business has ceased trading, cannot be contacted, or has directed you to us in writing, BizSensei Digital will handle the request directly to the extent it holds the data and is able to act on it lawfully. Nothing in this arrangement is intended to delay or defeat a statutory right, and the grievance route in this policy remains open to you if a forwarded request is not answered.
14. Retention schedule
BizSensei Digital keeps personal data only for as long as it is needed for the purpose for which it was collected, or for a longer period where a law, contract or legitimate compliance need requires it. The retention schedule below states the rule for each major category. A rule expressed as a period after an event, such as account closure or order completion, means the data is deleted or anonymised when that period expires, unless an active dispute, legal hold, tax requirement or unresolved grievance requires it to be kept for a further defined period, in which case it is kept only for that reason and is restricted from ordinary use.
| Category | Retention rule |
|---|---|
| Active account data | Kept while the account is active and for 12 months after account closure or last login, whichever is later, to allow reactivation, dispute handling and account audit, then deleted or anonymised |
| Orders and tax records | Order records kept as required for accounting and tax under applicable Indian law, ordinarily for 8 years from the end of the relevant financial year, limited to the fields needed for accounting, tax and audit |
| Consent logs | Kept for the life of the related account or transaction record and for 3 years thereafter, to prove notice and consent for the transactions they evidence |
| Support tickets and conversations | Kept for 3 years after ticket closure, then reviewed and deleted or anonymised unless the ticket evidences advice, a refund or a dispute that must be kept with the order record |
| Marketing lists and preferences | Kept while you remain opted in; on opt out, your contact is suppressed immediately from future sends and the preference record is kept for 3 years to prove the opt out was honoured |
| Tool leads | Contact details submitted through a free tool are kept for 12 months after submission for the follow up described at submission, then deleted if no account, order or opt in followed |
| Blog comments | Comments kept while the article is published, as stated in Part E; on article removal, comments are deleted with the article unless a moderation dispute requires a short further retention |
| OMS operational data | Order and operational data inside a restaurant account is kept while the restaurant account is active and for the period the restaurant instructs or the contract provides after termination, subject to tax records that must be kept by the restaurant and by BizSensei as processor records |
| Qiaomed records | Clinical records retention is the practitioner's duty under applicable law, as stated in Part G; BizSensei as processor keeps platform copies only on the practice's instructions and the contract, and waitlist data is kept only until launch communication is complete or 12 months after collection, whichever is earlier, if no account follows |
| Device, log and security data | Routine logs kept for 12 months, security and audit logs kept for 24 months, crash logs kept for 6 months after the defect is resolved, unless a security incident requires longer retention for investigation |
| Payment reconciliation data | Transaction references, status, amount and method type kept with the order record for the tax retention period; no card numbers, verification values or PINs are ever retained by BizSensei |
| Agency campaign lists | Client supplied lists kept only for the campaign and for 90 days after campaign completion for delivery reporting and opt out suppression, then deleted and confirmed to the client on request |
When a retention period expires, data is deleted from live systems and will fall out of backups in the ordinary backup cycle, which is designed so that deleted data does not remain in backups indefinitely. Where deletion of a single record from a backup is not technically feasible without corrupting the backup, the backup is protected, access is restricted, and the data is not restored to live use except for disaster recovery, after which the deletion is reapplied. Anonymised data that can no longer identify any individual is not personal data and may be kept for statistical purposes without the limits above.
15. Anonymisation and aggregation
BizSensei Digital may anonymise and aggregate personal data to produce statistics about usage, ordering patterns, service performance and product improvement, for example the number of orders processed in a month, average delivery times across outlets without identifying any customer, or feature adoption counts across accounts without identifying any business's confidential figures to another business. Anonymisation means removing or transforming identifiers so that the resulting data can no longer reasonably be linked to an identified or identifiable individual, taking account of the means reasonably likely to be used for re-identification.
Aggregated and anonymised outputs will not be published in a form that identifies an individual, a household, or a single small business where the aggregation pool is so small that the business would be identifiable. Where a case study or testimonial would identify a client business or an individual, it will be published only with that business's or individual's permission, on the terms agreed with them. You cannot opt out of anonymised aggregation that no longer contains your personal data, because such data is no longer your personal data, but you can exercise your rights over the underlying identifiable data in the ordinary way before anonymisation occurs.
16. Security programme
BizSensei Digital operates an information security programme designed to protect personal data against unauthorised access, disclosure, alteration, loss and destruction. The programme includes access control based on least privilege, meaning each staff account and each system account is given only the access needed for its function, and access to production personal data is restricted to authorised persons with a work need. It includes unique user accounts, strong authentication for administrative access, and prompt removal of access when a person's role changes or ends.
Encryption in transit is applied to connections between your browser or application and BizSensei servers, and between BizSensei systems and processors where the channel supports it, using transport layer security. Hashed passwords, as already described, protect account credentials at rest. Backups are taken on a regular cycle, stored with access controls, and tested for restoration. Logging is applied to administrative actions, authentication events and material system changes, so that unauthorised activity can be detected and investigated. Systems are patched, dependencies are updated, and known vulnerabilities are addressed in order of risk.
Organisational measures support the technical measures. Staff who handle personal data are instructed on confidentiality and on this policy. Support procedures prohibit asking for full passwords or payment secrets. Development and testing should use synthetic or anonymised data rather than live personal data wherever reasonably possible. New features that process personal data are reviewed for data minimisation, access control and retention before launch. Incident response procedures, described in the breach clause, assign responsibility for containment, assessment, notification and remediation when something goes wrong.
Industry standard security is applied, and no method is 100 percent secure. That honest limitation applies to every online service. Transmission over the internet and storage in electronic systems cannot be guaranteed to be completely secure against every possible attack, hardware failure or human error. BizSensei Digital works to reduce those risks to a reasonable and proportionate level for the data it holds, and it will inform affected data principals of a notifiable breach as required by law and by the breach clause below. You also play a part in security: use a strong and unique password, keep your device updated, sign out on shared devices, and report suspicious activity promptly.
17. Personal data breach
A personal data breach means an unauthorised acquisition, access, use, disclosure, alteration, loss or destruction of personal data, or any other unauthorised processing, whether accidental or deliberate. If BizSensei Digital becomes aware of a personal data breach affecting data for which it is fiduciary, it will act without delay. It will contain the breach where possible, assess the data, individuals and risks involved, preserve evidence for investigation, and remediate the cause.
In accordance with the DPDP Act, BizSensei Digital will give intimation of a personal data breach to the Data Protection Board of India and to each affected data principal, without delay, in the form and manner prescribed under the Act and its rules. The intimation to an affected data principal will describe, in clear and plain language, the nature of the breach, the data likely to be affected, the likely consequences, the measures taken or proposed to mitigate risk, and the steps the individual can take to protect herself or himself, together with contact details for further information. Where contact details for an affected individual are not available despite reasonable efforts, BizSensei Digital will use the best available channel, such as an account notice or a prominent website notice, as permitted by the applicable rules.
Where BizSensei Digital acts as processor and a breach affects a client business's end customer or patient data, BizSensei Digital will notify the affected business without undue delay after becoming aware of the breach, will provide the information the business needs to meet its own notification duties, and will assist the business in containing and investigating the breach. The business, as fiduciary, is responsible for intimating the Board and its affected data principals for that data, unless the contract or a lawful direction provides otherwise. Internally, every breach and every near miss that reveals a systemic weakness is recorded, reviewed, and used to improve controls, whether or not it was notifiable.
18. Your rights as a data principal
As a data principal you have the right to obtain from BizSensei Digital, on request, a summary of the personal data of yours that is being processed, the processing activities undertaken with respect to that personal data, and the identities of data fiduciaries and processors with whom your personal data has been shared, together with a description of the personal data shared, subject to the exceptions in the DPDP Act, including where sharing was with another fiduciary authorised by law to require disclosure. This is your right of access to information about your personal data.
You have the right to correction and erasure. You may request correction of inaccurate or misleading personal data, completion of incomplete personal data, updating of personal data that is out of date, and erasure of personal data that is no longer necessary for the purpose for which it was processed, subject to retention required by law. Where BizSensei Digital has disclosed your personal data to another fiduciary or processor, it will communicate a correction, completion, update or erasure to that recipient where the Act requires it and where it is technically feasible to do so. If erasure cannot be granted because a tax, accounting or other legal duty requires the record to be kept, BizSensei Digital will explain that reason, restrict the record to the legally required use, and erase it when the duty expires.
You have the right of grievance redressal, described fully in the grievance clause. You have the right to nominate another individual who will exercise your rights in the event of your death or incapacity, in the manner prescribed under the DPDP Act. A nomination may be recorded through the account mechanism where one is provided for the relevant property, or by a written request to info@bizsensei.co.in that identifies the nominee and is capable of verification. You may alter or cancel a nomination by the same route, and the most recent verified nomination will be the one acted upon.
You have the right to withdraw consent, as described in the basis clause, with the consequence that BizSensei Digital will cease the processing based on that consent within a reasonable time after withdrawal, and will instruct processors engaged for that processing to cease as well, unless another lawful basis requires the processing to continue. Withdrawal may mean that a service that depends on the withdrawn data can no longer be provided, for example a newsletter cannot be sent without an email address and delivery cannot be arranged without a delivery address, and BizSensei Digital will explain any such consequence when withdrawal is requested for data that is essential to an active service or order.
To exercise any right, write to info@bizsensei.co.in from the email address associated with your account or transaction where possible, state the right you wish to exercise, identify the property and, where relevant, the order, account or business involved, and provide the information reasonably needed to locate your data. Identity verification will be carried out in a proportionate manner before personal data is disclosed or altered, to prevent a third party from using a rights request to obtain or change your data fraudulently. Verification will not require more data than is needed to confirm identity, and any data supplied only for verification will be used only for that purpose. BizSensei Digital will respond within a reasonable period, will keep you informed if a request is complex or part of a large number of requests, and will not charge a fee for a rights request except where the DPDP Act or its rules permit a fee for a manifestly excessive or repetitive request, in which case the fee basis will be explained before it is applied.
19. Duties of data principals
The DPDP Act also states duties for data principals, and they are summarised here in brief so that you are aware of them. A data principal should comply with applicable law when exercising rights under the Act, should not impersonate another person while providing personal data, should not suppress any material information while providing personal data for a specified purpose, should not register a false or frivolous grievance or complaint, and should furnish only such information as is verifiably authentic where authentication is required for a subsidy, benefit, service, licence or similar entitlement under law. BizSensei Digital mentions these duties for completeness and will not use them to refuse a genuine request; where information supplied in a request appears to be false in a material respect, BizSensei Digital will ask for clarification before acting.
20. Children
Personal data of a child, meaning an individual below the age of eighteen years, is processed only with verifiable consent of a parent or lawful guardian, obtained before processing, in accordance with the DPDP Act. BizSensei Digital will take reasonable steps, proportionate to the property and the risk, to verify that the person giving consent for a child is the parent or lawful guardian and is identifiable and above eighteen years of age. Where a property or service is not intended for children, its terms will say so, and an account should not be created for a child through such a property.
BizSensei Digital will not undertake tracking or behavioural monitoring of children and will not direct targeted advertising at children. No BizSensei property will build an advertising profile of a child, follow a child's activity across services for marketing purposes, or serve an advertisement selected because of a child's behaviour or personal data. Where a child is an end customer of a business using BizSensei software, for example a parent ordering food for a family, the order data is the parent's or ordering adult's data for the purposes of the order, and any data that does relate to a child, such as a name given for a delivery instruction, is handled with the same heightened care and minimisation.
If BizSensei Digital learns that personal data of a child was collected without the required verifiable parental or guardian consent, it will stop the processing that depended on that consent, seek proper consent where the processing is otherwise lawful and desired by the parent or guardian, and erase the data where consent is not obtained or where the processing should not have occurred. A parent or lawful guardian may exercise the child's rights, withdraw consent, and raise grievances through the channels in this policy, subject to verification of identity and guardianship.
21. Grievance redressal and escalation order
BizSensei Digital provides grievance redressal first, before any complaint to the Data Protection Board. If you have a grievance about the processing of your personal data, about a rights request, about a communication you received, or about any matter under this policy, please contact the Grievance Officer for BizSensei Digital by email at info@bizsensei.co.in. The Grievance Officer is a role within BizSensei Digital, and grievances sent to that email address with the subject line Grievance will be routed to the person currently performing that role. Please include your name, contact details, the property involved, and a clear description of the grievance so that it can be investigated without avoidable delay.
Grievances will be acknowledged within 48 hours of receipt, and will be resolved within one month of receipt, in accordance with the timelines BizSensei Digital follows generally and, for store grievances, in alignment with the Consumer Protection (E-Commerce) Rules, 2020. If a grievance is complex and requires more time within the outer limit permitted by applicable law or rules, BizSensei Digital will inform you of the reason and the expected resolution date before the one month period expires. Acknowledgement will include a reference or tracking indication where the support system provides one, so that follow up correspondence can be linked to the same grievance.
- Step one: write to the Grievance Officer at info@bizsensei.co.in and allow the acknowledgement and resolution periods above to run.
- Step two: if the grievance is not resolved, or you are not satisfied with the resolution, write again to the same address marking the message as an escalation, referring to the original grievance and explaining what remains unresolved, so that it can be reviewed at a senior level within BizSensei Digital.
- Step three: only after exhausting grievance redressal with BizSensei Digital may a complaint go to the Data Protection Board of India, in the manner provided under the DPDP Act. BizSensei Digital states that escalation order expressly, as required by the Act's scheme, which expects the data principal to first approach the fiduciary's grievance mechanism.
Nothing in the escalation order prevents you from approaching a court or another competent authority where a law gives you a direct right to do so, or from contacting BizSensei Digital at any time for information about the status of a grievance. BizSensei Digital will not retaliate against any person for raising a grievance or exercising a statutory right, and grievance records are kept for compliance review and to identify recurring problems that should be fixed at source.
22. Government and legal requests
BizSensei Digital discloses personal data in response to government and legal requests only when legally required. A request from a court, tribunal, regulator, law enforcement agency or other public authority will be examined for its legal basis, scope and validity before any data is disclosed. Disclosure will be limited to the data that the valid legal requirement compels, and bulk or speculative requests that do not identify a lawful basis will not be complied with voluntarily.
Where it is lawful and reasonably possible to do so, BizSensei Digital will challenge an overbroad, unlawful or procedurally defective request through the available legal channels, or will seek to narrow it to what the law actually requires. Where it is permitted to notify the affected data principal, BizSensei Digital will notify that person before or promptly after disclosure, so that the person may seek legal advice or challenge the request herself or himself. Where notification is prohibited by law or by a binding order, BizSensei Digital will record the prohibition and will notify the person when the prohibition expires, if notification is then permitted and still meaningful.
BizSensei Digital also discloses personal data where necessary to establish, exercise or defend its own legal claims, to prevent or investigate fraud or a security incident, or to protect the rights, property or safety of BizSensei Digital, its users or the public, in each case only to the extent proportionate to that need and only where a lawful basis exists. Requests received and disclosures made are logged for internal accountability, subject to any legal prohibition on recording or revealing the existence of a particular request.
23. Cross border processing
Hosting and processors may process personal data in or outside India with contractual safeguards. Modern hosting, email delivery, payment and communication infrastructure may involve servers, support teams and network facilities located in more than one country. BizSensei Digital does not claim an India data centre or data localisation that is not a fact, and you should not assume that all personal data remains within India at all times. Where a transfer is restricted by a notification under the DPDP Act that prohibits transfer to a particular country or territory, BizSensei Digital will comply with that restriction for the data it controls.
Safeguards for cross border processing include selecting processors that offer contractual commitments on confidentiality, security, purpose limitation and assistance with data principal rights, using encryption in transit for transfers, limiting transferred data to what the processor needs, and retaining the ability to audit, suspend or terminate a processor that fails to honour its commitments. If you require a service configuration in which data for your business account is hosted only in a particular location, please raise that requirement before entering into the relevant contract, because the standard service is provided on the shared infrastructure described in this policy.
24. Business transfer
If BizSensei Digital sells, merges, reorganises or transfers all or part of its business or assets, personal data held in connection with the transferred part may transfer with the business to the successor, on the condition that the successor processes it in accordance with this policy or a policy that provides materially equivalent protection, and complies with the DPDP Act in relation to the transfer. Notice will be given before or promptly after a transfer that affects your personal data, through email to affected account holders where contact details are held, and through a prominent notice on the relevant property. The notice will identify the successor in general terms permitted by the transaction, the categories of data transferred, and any material change in how data will be processed, together with your rights in relation to the change, including withdrawal of consent for future processing where consent is the basis.
25. Do not track signals
Some browsers and devices send a do not track signal. There is no universally settled technical or legal standard for how every service must respond to such a signal, and BizSensei Digital's properties do not currently change their behaviour solely in response to a do not track header. That statement should not be mistaken for a practice of cross site advertising tracking. BizSensei Digital does not sell personal data, does not operate advertising trackers on the blog, and limits tracking technologies to the purposes described in the Cookie Policy. Your effective choices are the consent controls at collection, the cookie controls described in the Cookie Policy, the marketing opt outs described below, and the rights in this policy, all of which BizSensei Digital honours regardless of a browser signal.
26. Marketing and opt outs
Marketing messages are sent only on opt in, save for messages to an existing business contact about similar services where a lawful basis and a clear opt out are present, and save in all cases for transactional messages that are not marketing. Every marketing email contains an unsubscribe link or instruction, and using it will opt you out of that marketing list without affecting transactional messages. On WhatsApp, where the platform and message type support it, you may opt out by sending STOP or by following the instruction in the message, and BizSensei Digital and, for agency campaigns, the client business on whose behalf the message was sent, will suppress your number from further marketing sends on that programme once the opt out is received and processed.
Opt out does not stop transactional messages. Order confirmations, delivery updates, licence delivery, account security alerts, billing notices, support replies and other messages needed to perform a contract or comply with law will continue while the underlying transaction, account or legal duty is active. If you believe you have received marketing after opting out, please forward the message to info@bizsensei.co.in as a grievance, and the suppression records will be checked and corrected, and the cause will be investigated so that a system error is not repeated.
Preferences may be given per property or per programme. Opting out of the blog newsletter does not automatically opt you out of product updates for an OMS account, because those are separate lists for separate purposes, but a request sent to info@bizsensei.co.in asking to be removed from all BizSensei marketing will be applied across all BizSensei owned marketing lists, and confirmation will be sent when it has been applied. Suppression data, meaning the minimum contact detail needed to remember an opt out, is retained as stated in the retention schedule and is used only to honour the opt out.
27. Accuracy and your responsibility for your data
Accuracy depends partly on users keeping their data current. BizSensei Digital takes reasonable steps to keep personal data accurate for the purpose for which it is used, including using the most recent version you have provided in an account profile or a later transaction in preference to an older version. However, BizSensei Digital cannot know that your phone number, email address, delivery address or business details have changed unless you update them. Please review and update your account details when they change, correct any invoice or order detail that appears wrong as soon as you notice it, and use your correction right for any record you believe is inaccurate, incomplete or out of date.
Where a decision that affects you significantly is made by a business using BizSensei software on the basis of data inside its own account, the accuracy of that data is primarily the responsibility of that business and of the individual who supplied it to that business. BizSensei Digital will assist the business in correcting processor held data when instructed or when a forwarded rights request establishes that correction is needed. Automated decisions with legal or similarly significant effect are not made by BizSensei Digital about individuals solely on the basis of their personal data through the properties covered by this policy; if such a feature were ever introduced, notice of its logic, significance and recourse would be given before it was applied.
28. Responsibility for a business's own staff and accounts
BizSensei is not responsible for data a business's own staff mishandle inside their own accounts. Each business account holder is responsible for choosing who on its team receives access, for the roles and permissions it assigns, for training its staff on lawful handling of customer and patient data, for revoking access when staff leave, and for any misuse of the account by persons the business authorised or failed to remove. BizSensei Digital provides access controls, role based permissions where the product supports them, and audit logs to help a business manage that responsibility, but the provision of those tools does not transfer the business's fiduciary duties to BizSensei Digital.
If BizSensei Digital becomes aware of a credible report that a business is using its BizSensei account to process personal data unlawfully, it may investigate, may require the business to explain and remediate, and may suspend the offending use where the contract and the law permit, in order to protect data principals. Such action protects individuals and does not make BizSensei Digital the fiduciary for the business's data. Individuals affected by a business's mishandling should raise their grievance with that business as fiduciary in the first instance, and may also inform BizSensei Digital so that the processor side assistance and investigation described here can be offered.
Part B: BizSensei Showcase Website
Applies to: bizsensei.co.in
1. Scope of this part
This part applies to the BizSensei showcase website at bizsensei.co.in, which presents BizSensei Digital's software and services, publishes product information, offers free tools, provides contact and enquiry routes, and hosts the Sensei assistant chat. It supplements Part A. Every rule in Part A applies to this website, including the master data inventory, the processor schedule, the retention schedule, the security programme, the breach procedure, the rights process and the grievance escalation order. This part adds the collection points and purposes that are specific to the showcase website so that a visitor can see exactly what happens on this property without having to infer it from other properties.
2. Enquiry and contact forms on this website
When you submit an enquiry or contact form on bizsensei.co.in, we collect your name, email address, phone number where you provide it or where the form for a callback or a software demonstration requires it, the subject or service you select, and the message you write. The consent gate described in Part A operates before the information is taken: you review and accept the applicable documents, and a consent record is created with versions, internet protocol address and timestamp. The data is used to answer your enquiry, to arrange a demonstration or callback if you asked for one, to send a proposal if you requested one, and to keep a record of the conversation so that a later message from you can be answered in context.
If your enquiry becomes a client relationship, a store order or an OMS account, the relevant data moves into the systems for that relationship and the part of this policy for that property then also applies. If your enquiry does not proceed, the enquiry record is retained under the support and enquiry retention approach in Part A and is then deleted or anonymised. Your enquiry contact details are not added to a marketing list unless you separately opt in to product updates or a newsletter, and the enquiry form itself distinguishes between the response you requested and any optional opt in presented alongside it.
3. The Sensei assistant
The Sensei assistant is an automated chat assistant provided on BizSensei properties to answer questions about products and services, to guide visitors to the right page or form, and to help a visitor frame an enquiry. When you chat with the Sensei assistant, we collect the text you type, any name, email or phone number you provide in the chat in order to be contacted, the pages or topics the conversation relates to, and technical data needed to operate the chat session. Chat transcripts are support conversations for the purposes of Part A and are retained on the same basis.
Please do not enter passwords, full payment card details, UPI PINs, banking passwords, government identity numbers or detailed health information into the Sensei assistant. The assistant does not need such information to answer product questions or to arrange a contact, and entering it creates a risk that BizSensei Digital does not ask you to take. If the assistant cannot answer a question, it will offer a route to human support by email at info@bizsensei.co.in or by phone at +91 93726 65745. Answers given by an automated assistant are general information about BizSensei products and services and are not professional advice about your particular legal, tax or medical position.
4. Free tools on this website
BizSensei.co.in offers free tools that perform calculations, checks, generators or similar functions for visitors. Some tools operate entirely on the values you enter for the immediate calculation and do not require you to identify yourself in order to see a result. Other tools, or optional features of a tool such as emailing a result, saving a report or requesting a follow up, ask for name, email or phone number. Where identifying details are requested, the tool page states the purpose at the collection point, the consent gate applies where the flow takes information for follow up, and the resulting record is a tool lead for retention purposes.
Values entered into a free tool may reveal information about your business, such as turnover ranges, menu prices, staff counts or marketing spend, depending on the tool. Those values are processed to produce the result you requested and, where you asked for a report or follow up, to deliver it and to discuss it with you. Tool inputs are not sold, are not published in identifiable form, and are not used to make a decision about you that produces legal or similarly significant effects. Aggregated and anonymised tool usage statistics, such as how many times a tool was used in a month, may be kept after individual lead records are deleted, in accordance with the anonymisation clause in Part A.
5. Product information, demonstrations and downloads
When you request product information, a brochure, a demonstration or a download from bizsensei.co.in, we collect the contact details needed to deliver what you requested and to follow up about it, ordinarily name, email and phone, together with the product you selected and any company or outlet details you volunteer to help tailor the demonstration. A demonstration may be conducted on a test account with sample data, and you should not enter real customer or patient personal data into a demonstration environment. If a demonstration is set up inside a trial account that you will operate, the trial account rules in Part F apply to any data you choose to enter there.
Download and information delivery records are kept so that BizSensei Digital can prove what was sent, answer questions about the version you received, and, only where you opted in, send you an updated version or related product update. A request for information is not, by itself, an opt in to a general newsletter, and the follow up for an information request is limited to that request and to closely related information about the same product, with an opt out in any follow up email.
6. Cookies and measurement on this website
This website uses the cookie categories described in the Cookie Policy. Session and security cookies support forms, consent recording and any signed in demonstration or account area linked from this website. Preference cookies remember choices such as a dismissed notice. Measurement, where used on this website, is directed to understanding which pages and tools are useful, in aggregate, and is not used to sell data or to build profiles for third party advertising. You may control cookies through your browser and through any consent management control presented on the website, subject to the warning in Part A that disabling session cookies may prevent forms, checkout links and signed in features from working correctly.
7. Links from this website to other properties
BizSensei.co.in links to the store, the agency website, the blog, the OMS portal and other BizSensei properties, as well as to external resources. Moving from this website to another BizSensei property does not change the fiduciary: BizSensei Digital remains responsible as described in the part for the destination property. Moving to an external website takes you outside BizSensei properties, and that website's own privacy policy will govern. Account data may be recognised across BizSensei properties where a single sign on or linked account feature is provided, and where that happens the sign in notice will explain which account details are shared between the properties for authentication, limited to identity and account status data needed to let you sign in without creating a duplicate account.
Part C: BizSensei Store
Applies to: bizsensei.store
1. Scope of this part
This part applies to the BizSensei store at bizsensei.store, which is the commerce property of the ecosystem where products, plugins, licences, subscriptions and billing transactions are sold and managed. It supplements Part A in full. The store processes the most complete transactional dataset in the ecosystem, because a purchase requires identity, contact, order, payment reconciliation and licence delivery data to be handled together, accurately and for a long retention period required by tax law. This part explains each element of that handling so that a buyer knows exactly what is collected at checkout, what is never collected by BizSensei, and how long each record is kept.
2. Account and checkout data
When you create a store account or check out as a buyer, we collect your name, email address, phone number, account credentials in hashed form, the products or plans you select, any add ons you select, billing details you provide for invoicing such as a business name and tax identifier where you supply it for a tax invoice, and order details generated by the transaction. Where a plan requires the creation of a linked product account, for example an OMS account provisioned from a billing purchase, we also collect the login identifier and the initial account setup details needed for provisioning, and a password set through the secure account setup flow for that product. Passwords you set are handled only in hashed form by BizSensei systems after submission over an encrypted connection.
The consent gate operates at store registration and checkout flows that take information, and a consent record is created for each such flow as described in Part A. Checkout cannot be completed without the data that is necessary for payment, delivery of a digital product or licence, invoicing and fraud prevention. Optional marketing opt in at checkout is separate from the act of purchasing: refusing marketing opt in does not affect your order, your licence or your support entitlement in any way.
3. Payment data and the gateway boundary
Payment in the store is processed through a payment gateway. Full card numbers, card verification values, UPI PINs and banking passwords never touch BizSensei servers. You enter payment instrument data into the gateway's secure interface or into a payment application under the gateway's or your bank's control, and the gateway processes that data under its own security programme and privacy policy. BizSensei Digital receives and retains only transaction references, payment status, amount, method type, the gateway identifier for the transaction, and the limited payer details the gateway returns for reconciliation, such as a masked instrument description where the gateway provides one.
That boundary protects you and limits our risk. Because BizSensei does not receive card data, BizSensei support cannot view, retrieve or read back your card number, and any person claiming to be BizSensei support who asks for your full card number, verification value, UPI PIN or banking password should be refused and reported to info@bizsensei.co.in. Refunds, where approved, are processed back to the original payment method through the gateway using the transaction reference, without BizSensei needing or receiving your full instrument details. Chargeback and payment dispute records are retained with the order record so that the transaction can be evidenced to the gateway, the bank and, where required, a tax or legal authority.
Prices and amounts in the store are stated on the store pages and checkout at the time of purchase. This Privacy Policy itself states no prices and makes no representation about the price of any product. Where an amount must be described in this policy for a legal purpose, it would be written in words or with the currency described as Indian rupees (INR), and no amount in this policy should be read as a price list.
4. Licences, delivery and provisioning
A principal purpose of store processing is delivering licence keys and provisioning purchased products. On successful payment, the store generates or allocates a licence key, links it to your account and order, records the product, plan, domain or installation entitlement where the product is domain or installation based, and delivers the key and activation instructions to your email address and to your account area. Licence records include the key or a keyed reference to it, the product and version entitlement, activation status, the domain or account to which it is activated, issue and expiry or renewal dates where the licence is time limited, and support entitlement status.
Licence validation requests made by installed software may transmit the licence key, the domain or installation identifier, the product version and technical data needed to verify entitlement and to prevent piracy. That validation data is processed to confirm that the licence is genuine and active, to enforce the licence quantity purchased, and to record version information needed for support and security updates. It is not used to collect the end customer data held inside your installation, and a licence check does not transmit your customers' orders, your patients' records or your business's content to BizSensei, save where a separate cloud feature that you have enabled expressly provides for such transmission and is covered by Part F or Part G.
5. Invoices, accounting and tax retention
Order records are kept as required for accounting and tax. The store issues invoices and receipts from order and billing data, records payments and refunds against orders, and retains the resulting accounting records for the period stated in the retention schedule in Part A. That retention continues even if you close your store account, withdraw marketing consent, or request erasure of other data, because the legal duty to maintain tax and accounting records overrides an erasure request for the fields covered by that duty. When the tax retention period expires, invoice data that is no longer needed will be deleted or anonymised in accordance with the schedule, subject to any active dispute or audit.
If you supply a business tax identifier or invoice details belonging to your business, you confirm that you are authorised to supply them for invoicing for the purchasing business and that they are accurate. An error in a supplied tax identifier can affect the validity of a tax invoice and any input tax credit your business may claim, so please verify invoice details promptly on receipt and request correction through support as soon as an error is noticed, noting that a correction to a filed tax record may need to be made by a credit note or revised document under tax rules rather than by silently altering the original record.
6. Store support, returns and disputes
Support for a store purchase uses your account, order and licence data, together with the support conversation, to diagnose activation problems, delivery failures, billing queries and product defects. Where a refund, return of a digital product or cancellation is governed by the Refund Policy for the store, the personal data needed to assess and process that request, including order details, licence activation status and payment transaction references, will be processed for that purpose and retained with the order record. Please read the store's Refund Policy together with this part, because that policy states the commercial terms on which refunds are considered, while this policy states how the data involved in a refund request is handled.
Store grievances follow the grievance procedure in Part A, with acknowledgement within 48 hours and resolution within one month, aligning with the Consumer Protection (E-Commerce) Rules, 2020. For a store grievance, please include your order identifier and the email address used for the order, so that the correct transaction can be located without asking you for payment secrets. BizSensei Digital will never ask you to prove a purchase by disclosing a full card number or a banking password; an order identifier, transaction reference and account email are sufficient for verification in ordinary cases.
7. Store marketing and account notices
Store account holders receive transactional and account notices by email and, where a mobile number is provided for that purpose, by SMS or WhatsApp, including order confirmation, payment receipt or failure notice, licence delivery, renewal reminders for time limited licences or subscriptions, security alerts and material changes to store terms or to this policy. Renewal reminders are considered account notices where they relate to an active licence or subscription that will lapse without renewal, but any promotional content beyond the factual reminder requires marketing opt in and carries an opt out.
Product updates are sent only on opt in, as stated in Part A. A buyer who opts in to product updates for a purchased product will receive updates about that product, including new versions, security notices presented as product information, and offers that relate directly to that product, until opt out. Security notices that affect the safe use of a purchased product may be sent to all affected licence holders regardless of marketing preference, because they are safety and account notices rather than marketing, and they will be limited to the security matter and the action the licence holder should take.
8. Fraud prevention and store security
The store processes device, log, account and transaction data for fraud prevention and payment security. Signals such as repeated failed payment attempts, mismatched transaction details, licence activation anomalies and account takeover indicators may be reviewed, and an order or activation may be paused for verification where a credible fraud or security risk is identified. Verification in such a case will be proportionate and will not request payment secrets. If an order is declined or a licence is suspended for fraud or abuse, the affected buyer will be informed of the fact and of the grievance route, subject to any legal restriction on disclosing investigation details that would prejudice prevention of further fraud.
Store data is not shared with other buyers. One buyer's order history, licence keys and invoices are visible only to that buyer's account, to BizSensei staff with a support or accounting need, and to processors and authorities as described in Part A. Public reviews or testimonials attributed to a buyer will be published only with the content and attribution the buyer supplied for publication or expressly approved.
Part D: BizSensei Agency
Applies to: bizsensei.agency
1. Scope of this part
This part applies to the BizSensei agency website and to the agency services practice of BizSensei Digital, covering performance marketing, web development, search engine optimisation, retention marketing, content and influencer related services, and similar client services presented on the agency website. It supplements Part A. Agency work has a distinctive privacy shape: BizSensei Digital holds its own client relationship data as fiduciary, and it also handles the personal data of a client's audience, customers and prospects as processor on the client's instructions. Both halves of that shape are explained in this part, because a client needs to know what it is entrusting to us, and a member of a client's audience needs to know who is responsible for a message she or he receives.
2. Client and prospect data on the agency website
When you contact the agency through bizsensei.agency, request an audit, book a discovery call, download an agency resource or submit a brief, we collect name, email, phone, business name, website address, the services you select, your budget range or project description where you choose to provide it, and the content of your message. The consent gate and consent record described in Part A apply to agency forms that take information. The data is used to respond to your enquiry, assess whether the agency can help, prepare a proposal, schedule and conduct calls, and keep a record of the discussion. Prospect data that does not become a client engagement is retained under the enquiry and support approach in Part A and is then deleted or anonymised, and it is not added to a general marketing list without opt in.
During an engagement, client relationship data grows to include project communications, meeting notes, approvals, deliverables, feedback, billing contacts, contract documents and support requests. That data is processed to deliver the services, to evidence approvals and instructions, to invoice and account for the engagement, and to defend or establish claims in the event of a dispute. Access within BizSensei Digital is limited to the team working on the engagement and to management and accounting staff with a need to know. Client confidential information, including audience data and campaign performance data, is not disclosed to another client and is not used as a public case study without the client's permission, save for anonymised and aggregated descriptions that do not identify the client or its customers.
3. Client supplied lists and the client's warranty
Agency retention work uses email and WhatsApp with client supplied lists. A client that engages BizSensei Digital for retention, lifecycle, email, SMS or WhatsApp marketing will supply, or direct us to use, a list of its customers or subscribers, together with fields needed for personalisation and segmentation, such as name, contact channel, purchase history with that client, or preference data held by that client. Clients warrant their lists are lawfully collected. That warranty means the client confirms that each person on the list was given proper notice by the client, that the client has consent or another lawful basis for the marketing use proposed, that opt outs previously given to the client have been removed or suppressed, and that the list was not obtained by unlawful scraping, purchase of unlawfully collected data, or deception.
BizSensei Digital relies on that warranty and also applies practical checks: it will ask how a list was collected where the answer is not already documented in the engagement, it will refuse or pause a campaign where a list appears on its face to be unlawfully collected, and it will require suppression of complainers and opt outs from all future sends for that client. BizSensei Digital processes a client supplied list only as processor for that client's campaign. The list is not merged into any BizSensei owned list, is not used for another client, is not sold, and is deleted after the campaign and the short reporting period stated in the retention schedule, with suppression records for that client retained only as needed to honour opt outs for that client's programme.
4. Campaign delivery, measurement and opt outs
To deliver an agency campaign, contact data is shared with the email, SMS or WhatsApp delivery processor for that campaign, limited to the contacts, message content and personalisation fields needed for the send. Delivery processors return delivery, bounce, open, click, reply and opt out signals, which are processed to report campaign performance to the client, to clean the list of undeliverable contacts, and to honour opt outs. Reports to the client are ordinarily aggregated, and individual level engagement data is shared with the client only in respect of the client's own list and its own campaign, which the client already holds as fiduciary for that audience.
A recipient who wishes to opt out of a client's campaign should use the unsubscribe or STOP mechanism in the message, which acts directly on that client's programme. A recipient may also write to BizSensei Digital at info@bizsensei.co.in identifying the sending business and the message received, and BizSensei Digital will forward the opt out or complaint to that client promptly, suppress the contact from further sends through BizSensei systems for that client pending the client's confirmation, and treat an unresolved complaint as a grievance under Part A insofar as it concerns BizSensei Digital's own processing as processor. The client, as fiduciary for its audience, remains responsible for the lawfulness of its list and its campaign content, including any claim made in the message that BizSensei Digital reproduced on the client's instructions and approval.
5. Advertising platforms and audience data
Where an agency engagement includes advertising on third party platforms, the platform's own data practices apply to data collected by the platform, and the client's and BizSensei Digital's use of platform tools must comply with the platform's terms and with Indian law. BizSensei Digital will not upload a client's customer list to an advertising platform for matching or audience building unless the client instructs it in writing, the client confirms a lawful basis for that upload and use, and the upload is configured in the client's own advertising account wherever the platform allows that structure, so that the audience remains the client's asset in the client's account. Hashed uploads, where a platform requires hashing of identifiers before upload, are used where the platform provides that facility, and the unhashed list is not sent to the platform in that case.
Pixels, tags and similar measurement tools on a client's own website are the client's responsibility as the operator of that website, although BizSensei Digital will advise on consent and notice for such tools as part of an engagement where that advice is within scope. BizSensei Digital will not place an advertising tracker on a BizSensei owned property in a manner inconsistent with Part A or the Cookie Policy, and the presence of a tag manager or analytics tool on a client website managed under an agency engagement will be documented to the client so that the client's own privacy policy can describe it accurately.
6. Creative, content and influencer data
Agency work may involve personal data in creative and content production, including photographs, video, voice recordings, testimonials, user generated content and influencer or creator contact and performance data. Where an individual's image, voice or testimonial is to be used in marketing, the engagement should record that individual's consent or release for that use, the scope and duration of the use, and any payment or consideration, and BizSensei Digital will work to the release that is documented. A client that supplies testimonials, photographs or user content for use in a campaign warrants that it has the right and any necessary consent to supply and use that material, and BizSensei Digital may pause use of material where a credible consent complaint is received until the client evidences the basis for its use.
Creators and influencers engaged through the agency provide contact data, audience and rate information, deliverables and payment details, which are processed to brief, contract, review and pay for the engagement. That data is shared with the sponsoring client to the extent needed for selection, approval and payment, and is not sold or added to an unrelated marketing list. Portfolio material published by the agency that identifies a creator or a client will be published only on the basis agreed in the relevant engagement or release.
7. Agency website tools, audits and resources
The agency website may offer audits, calculators, checklists or downloadable resources that ask for a website address, business details and contact details in exchange for a report or resource. The data supplied is used to produce and deliver the requested item, to discuss it with you if you asked for a discussion, and, only on opt in, to send agency updates. A website audit necessarily processes the public content of the website address you supply, and you should supply only a website that you own, manage or are authorised to submit for audit. An audit report is prepared for the requester and is not published by BizSensei Digital in identifiable form without permission.
Part E: Blog
Applies to: blog.bizsensei.co.in
1. Scope of this part
This part applies to the BizSensei blog at blog.bizsensei.co.in, which is the content hub of the ecosystem, publishing articles, guides and commentary. It supplements Part A. The blog is deliberately a low data property: reading an article requires no account and no identification, and the only routine personal data collections on the blog are comments, newsletter subscriptions, and contact or sharing actions that you choose to take. This part states those collections exhaustively for the blog, together with the blog's specific cookie position, so that a reader can be confident about what reading the blog does and does not involve.
2. Reading the blog
You may read published articles on the blog without registering, subscribing or providing personal data. Our servers will necessarily process technical data to deliver the pages you request, including your internet protocol address, browser and device information, the pages requested and timestamps, as device and log data under Part A. That technical data is used to serve the site, protect it from abuse, diagnose errors and produce aggregate readership counts, such as the number of times an article was viewed in a period without identifying individual readers. The blog does not require you to accept advertising trackers as a condition of reading, and it does not fingerprint your device to build a reader profile for sale or for third party advertising.
3. Comments
Comments collect name, email and comment text. If you post a comment on the blog, the name you supply and the text of your comment will ordinarily be published with the article, while your email address is collected for moderation, notification and abuse prevention and is not published as part of the comment display. You should therefore write your comment on the understanding that its text and your supplied display name will be public, and you should not include personal data about yourself or any other person in a comment text that you do not wish to be public, such as a phone number, a home address, financial details or health details.
Comments are moderated. Moderation processing includes reviewing comment text and the supplying account or contact details for spam, abuse, unlawful content and relevance, and may involve automated spam detection by a processor that receives the comment content and technical data needed for that check. Comments kept while the article is published: that is the retention rule for blog comments. When an article is removed from publication, its comments are removed with it, subject to a short retention where a moderation or legal dispute about a specific comment requires the record to be preserved, and subject to copies that readers may have made outside BizSensei systems, which BizSensei Digital cannot retrieve.
You may request correction or removal of your own comment by writing to info@bizsensei.co.in identifying the article, the name used and the approximate date of the comment. Removal of a published comment will be carried out within a reasonable period after verification that the request comes from the commenter or a person with authority to act for the commenter, or without such verification where the comment itself contains personal data that should plainly be removed for safety or legal reasons. Editing a comment after publication may be shown as an edit or may be handled by removal and reposting, depending on the blog system in use at the time, so that the public record is not silently altered in a misleading way.
4. Newsletter
The blog offers a newsletter subscription. Newsletter email is collected until unsubscribe. If you subscribe, we collect your email address and, where the form offers it, your name and topic preferences, together with your consent record where the consent gate is applied to the subscription flow. The newsletter data is used only to send the blog newsletter and, where you selected them, topic specific editions of it. It is not sold, it is not shared with advertisers for their own marketing, and it is not merged with a store or OMS marketing list unless you separately opt in to that list or the subscription form expressly presents a combined opt in that you affirmatively select.
Every newsletter email contains an unsubscribe mechanism. Unsubscribing stops future newsletter sends to that address, and the suppression approach in Part A applies so that the address is not accidentally resubscribed from an old list. Newsletter delivery uses an email delivery processor that receives your email address and the newsletter content and returns delivery and engagement signals. Engagement signals, such as whether a newsletter was delivered or a link was clicked in aggregate, are used to improve content and deliverability and to remove persistently undeliverable addresses. If you forward a newsletter to another person, that person's data is not collected by BizSensei Digital unless that person herself or himself subscribes or contacts us.
5. Blog cookies
The blog uses a session cookie for admin and a consent record, and no advertising trackers. In concrete terms, an ordinary reader who does not sign in as an administrator will not be given an administrative session, and the blog's use of cookies for readers is limited to strictly necessary and consent related mechanisms described in the Cookie Policy, together with any preference you set through a consent control. Administrators and editors who sign in to publish or moderate receive a session cookie that keeps them authenticated, protects the session and records administrative actions in logs for security and accountability.
Because the blog carries no advertising trackers, there is no blog based advertising profile to opt out of. If an article embeds third party content, such as a video or a social post, at your interaction, the provider of that embedded content may set its own cookies or collect data under its own policy once the embed loads or is played. Where the blog system can present an embed in a click to load form, that form is preferred, so that third party collection does not begin merely because you opened the article page. You should review the provider's policy before playing or interacting with embedded content if you are concerned about that provider's practices.
6. Sharing articles and contacting the blog team
Share buttons or links on the blog allow you to share an article address through your own email, messaging or social applications. Using a share function sends the article link from your device or account; BizSensei Digital does not receive the personal data of the person you share to merely because you used a share button, and it does not build a list of your contacts from sharing activity. If you contact the blog team with a correction, a tip, a guest contribution proposal or a copyright or privacy complaint about an article, your name, email and message content are processed as a support or enquiry conversation under Part A, and any article correction that results from your message will be handled editorially, with personal data in the published correction limited to what is necessary and, where a contributor is credited, only with that contributor's agreement.
7. Contributor and author data
Authors and contributors to the blog provide name, author biography, photograph where they agree to publish one, contact details and payment details where a contribution is paid. That data is processed to attribute, publish, promote and pay for contributions, and the published elements are limited to the name, biography and photograph the contributor approved for publication. A contributor may update a biography or request removal of a photograph from future display by writing to info@bizsensei.co.in, noting that articles already syndicated or copied by readers outside BizSensei systems cannot be recalled by BizSensei Digital. Guest contribution proposals that are not accepted are retained under the enquiry approach in Part A and are not published or shared with advertisers or other contributors.
Part F: BizSensei OMS
Applies to: BizSensei OMS: portal, apps and marketplace
1. Scope and the two layers of OMS data
This part applies to BizSensei OMS, the restaurant software product of BizSensei Digital, including the OMS portal, the OMS point of sale and management applications, the food ordering marketplace and customer facing ordering services, the rider application, and related OMS websites, application programming interfaces and integrations. It supplements Part A in full, and it is the longest property part in this policy because OMS contains two distinct layers of personal data that must never be confused. The first layer is the restaurant's own account data, where BizSensei Digital is fiduciary for the account relationship with the restaurant business. The second layer is the restaurant's operational data about its own customers, orders and staff activity inside the software, where the restaurant is fiduciary and BizSensei Digital is processor. This part deals with each layer separately and then explains the customer facing ordering service, where the roles meet.
2. Restaurant account data where BizSensei is fiduciary
When a restaurant, cafe, cloud kitchen, bakery, food outlet or other food business signs up for OMS, we collect the business name, outlet details, the owner or administrator's name, email and mobile number, authentication data in hashed or tokenised form, plan and billing linkage to the store where the plan was purchased, branch and outlet configuration, tax and invoice details the business supplies for its OMS billing, and the identities and roles of staff accounts the business creates. The consent gate applies to restaurant signup, and a consent record is created before information is taken in the signup flow, as described in Part A. Without a required consent acceptance, restaurant signup is blocked by the system, because the account cannot be created lawfully and contractually without acceptance of the governing documents.
Restaurant account data is used to create and operate the OMS account, authenticate administrators and staff, enforce plan limits and entitlements, provide billing and renewal processes through the store, deliver support and product notices, prevent account abuse, and maintain security and audit logs for the account. A restaurant's account data is not disclosed to another restaurant, save for marketplace display data that the restaurant itself publishes for ordering, such as its name, menu, prices set by the restaurant, opening hours and delivery areas, which the restaurant controls and can update or withdraw through its account, subject to orders already placed.
3. Operational data where the restaurant is fiduciary
Inside an OMS account, the restaurant and its staff enter, import and generate operational data: menus, tables, orders, bills, kitchen tickets, inventory and purchase records, staff shifts, customer names and phone numbers recorded at the counter or table, loyalty or feedback records the restaurant chooses to keep, and reports derived from that activity. To the extent that operational data contains personal data of the restaurant's customers or staff, the restaurant is the data fiduciary for that data. The restaurant determines why a customer's phone number is taken at billing, how long it keeps its own order history for its own accounting, and what marketing, if any, it sends to its own customers on its own behalf.
BizSensei Digital processes operational data as processor on the restaurant's instructions, which are given through the restaurant's use of the software features, its account settings, and the OMS contract. BizSensei Digital will not use a restaurant's operational customer data to market BizSensei products to those customers, will not sell it, will not disclose it to another restaurant, and will not mine it for BizSensei advertising. Anonymised and aggregated operational statistics may be produced in accordance with Part A only where the aggregation cannot identify the restaurant or any individual, or, where a restaurant's own dashboard shows it benchmarks, only in the anonymised comparative form the feature describes and the restaurant has enabled.
Restaurants are independent data fiduciaries for data they collect directly. That independence covers data a restaurant collects outside the software as well, such as a paper reservation diary, its own social media inbox, a separate delivery register, or a payment it takes directly. BizSensei Digital has no access to and no responsibility for such off system data, and a customer whose data was collected by a restaurant outside OMS should direct her or his request to the restaurant for that data. Conversely, a restaurant cannot use its OMS account to disclaim responsibility for data it chose to collect through OMS: choosing the software does not transfer the restaurant's fiduciary duties to the software provider.
4. Staff accounts, roles and activity logs
A restaurant administrator creates staff accounts for managers, cashiers, waiters, kitchen staff and other roles, assigns permissions, and removes access when a staff member leaves or changes role. Staff personal data processed in OMS includes name, mobile or email used for login, role, branch assignment, login history, one time password verification results for staff login where that method is enabled, and activity logs showing orders created, edited, billed, cancelled or settled under that staff account. Those logs serve the restaurant's own accountability, cash and stock control, dispute investigation and fraud prevention, and they serve BizSensei Digital's security and support functions where a support issue requires tracing an action.
A staff member's activity data inside a restaurant account belongs, for fiduciary purposes, to the employment or engagement relationship between the staff member and the restaurant. The restaurant should inform its staff that the point of sale system records activity under their login, should issue individual logins rather than shared logins so that logs are accurate, and should not use OMS logs for a purpose incompatible with that notice. BizSensei Digital will provide staff activity data to the restaurant administrator under the account's permissions, and will provide it directly to a staff member on a rights request only to the extent that the data is that staff member's personal data, verification succeeds, and disclosure does not reveal another person's personal data or the restaurant's confidential information that is not the requester's data.
5. Food ordering account data
The customer facing food ordering service, including the OMS Food application and web ordering pages, collects account data consisting of name, mobile number, email address where you provide it or where it is needed for a receipt or account recovery, and one time password verification results only, never the codes. That distinction is deliberate and important. When you verify your mobile number, the verification system confirms to BizSensei whether the code you entered was correct, and BizSensei records the result, the time and the number verified. The one time password code itself is generated and checked by the verification provider or system component for that purpose and is not stored by BizSensei as part of your account profile, is not visible to restaurant staff, and is not used for any other purpose.
You may in some flows place an order with guest or minimal account details where the ordering page allows it, in which case the name, mobile number and delivery details needed for that order are still collected as order data, because an anonymous food order cannot be prepared, paid for or delivered. Creating a full account adds saved addresses, order history and preference features for your convenience, and you may update or delete saved addresses and profile details through the application or by a rights request. Account deletion for a food ordering account deletes or anonymises the profile and saved address data in accordance with the retention schedule, while order records that a restaurant or BizSensei must keep for accounting and tax are retained in the limited form the schedule describes, detached from marketing use.
6. Order data and delivery data
Order data in the food ordering service includes the restaurant and outlet selected, items and quantities, variants and add ons, price, taxes and charges as calculated for the order, discounts or offers applied, order notes you write, payment status and method type, order status history, kitchen and dispatch timestamps, and cancellation or refund status where applicable. Delivery data includes your delivery address, saved address label such as home or work where you supply one, delivery instructions, landmark or gate instructions you write, the rider assigned to the order, and delivery status and timing records. Order and delivery data are shared with the restaurant that must prepare your order and, where delivery is by a rider, with the assigned rider to the extent needed to collect and deliver it, as explained in the sharing clause for OMS below.
Sensitive data shared voluntarily in order notes is used only for the order. Customers sometimes write allergy information, spice or ingredient restrictions for medical reasons, instructions relating to a disability, or other personal information in an order note. Please include in an order note only what the kitchen and rider genuinely need for that order, because the note is visible to the restaurant staff preparing the order and, where relevant to delivery, to the rider. BizSensei Digital does not extract order note content for profiling, advertising or any purpose beyond order fulfilment, support investigation of that order, and safety investigation where a note is relevant to an incident report about that order.
7. Location data in ordering and tracking
Location is collected only with device permission for ordering and tracking. Where the food ordering application asks for your device location, it does so to show nearby outlets, to pre fill or verify a delivery area, to estimate delivery feasibility, and, during an active delivery, to show tracking where that feature is provided. Precise location access depends on the permission you grant in your device settings, and you may deny or revoke that permission at any time, in which case you can still ordinarily order by typing an address manually, although nearby discovery and live map features that depend on location will not function fully.
Rider location during a delivery is the rider's personal data as well as an operational record. It is collected while the rider is on duty and assigned to deliveries, for dispatch, customer tracking of that delivery, safety and dispute resolution, and it is shared with the customer only as a live delivery position for that customer's own active order and only for the duration needed for that tracking. It is not published as a general public track of the rider, and historical rider location is retained only as an operational and dispute record under the retention schedule, accessible to the restaurant, to BizSensei support for a relevant investigation, and to the rider in respect of her or his own data on request.
8. Payment data in food ordering
Payment data in food ordering follows the same gateway boundary as the store, stated here in full because it is a harvested commitment for the Food service. Full card numbers, CVV, UPI PINs and banking passwords never touch BizSensei servers. Payment instrument data is entered into the payment gateway's or your payment application's secure flow, and the gateway, your bank and your payment application handle that data under their own policies and security programmes. BizSensei retains only transaction references, status, amount and method type, together with the restaurant, order and payer account linkage needed to reconcile the payment with the order, to process a refund to the original method where a refund is due, and to investigate a payment dispute for that order.
Cash on delivery and pay at outlet options, where a restaurant offers them, involve no gateway data, and the only payment data recorded is the method type selected, the amount due, and the settlement status recorded by the restaurant or rider on completion. A rider or restaurant staff member must never ask for your UPI PIN, banking password or full card details to complete a delivery, and any such request should be refused and reported to the restaurant and to BizSensei Digital at info@bizsensei.co.in.
9. Communications, reviews and support in OMS
Communications data in OMS includes order confirmation and status messages by push notification, SMS, email or WhatsApp where those channels are enabled for the outlet or the marketplace, in application chat or support messages where provided, call records where you contact support by phone and a note of the call is made, and system notifications to restaurant staff and riders about new, updated or cancelled orders. The OMS sends order communications as a core function, and those messages are transactional: opting out of marketing does not stop an order confirmation or a delivery update for an order in progress, although you may control push notifications at device level, noting that disabling push may mean you miss a time sensitive update about your own order.
Reviews and ratings you submit for a restaurant, an order or a rider are processed to display the review in the form described at submission, to moderate it for abuse and unlawful content, to share feedback with the restaurant concerned, and to produce aggregate ratings. A review published under a name or initial will carry that attribution, so please choose the attribution the submission form presents with that understanding. Technical and device data and crash logs are collected from OMS applications, including device model, operating system, application version, feature events, error traces and crash reports, to keep the applications stable, to fix defects that affect ordering or point of sale reliability, and to plan capacity for peak ordering periods. Crash logs are designed to contain technical traces rather than order content, and where a crash report inadvertently contains personal data, it is used only for defect investigation and is deleted on the crash retention rule in Part A.
10. The marketplace and discovery
The OMS marketplace and discovery features list restaurants that have chosen to be discoverable, showing the restaurant's published name, cuisine, menu, prices set by the restaurant, offers the restaurant has configured, opening and closed status, delivery areas and estimated times. Discovery uses your selected location or area to order and filter results, and, where you grant device location permission, your device location for that purpose as described above. A restaurant that is closed is shown as closed upfront in discovery, so that you do not build an order at an outlet that cannot accept it, and the closed status shown is the status the outlet's account and hours provide to the marketplace at that time.
Marketplace account and checkout flows are covered by the consent system. Creating a marketplace account and placing a marketplace checkout order each present the applicable documents through the consent gate, and consent records are created for those contexts as described in Part A. Marketplace order data is shared with the fulfilling restaurant as described in this part, and the restaurant is fiduciary for the customer relationship it builds from that order beyond the marketplace transaction, subject to the customer's rights and to the restaurant's own privacy notice where it provides one. BizSensei Digital does not give a marketplace customer's data to any other restaurant for marketing, and a restaurant may market to its own marketplace customers only where it has a lawful basis to do so as fiduciary for that relationship.
11. Rider data and the rider application
Riders register with name, mobile number, email address where required, identity and eligibility documents the onboarding process specifies, vehicle details, bank or payment details needed to pay delivery earnings, and account credentials. Rider registration uses the consent gate, and onboarding documents are processed to verify eligibility to perform delivery work, to create the rider account, to assign deliveries, to calculate and pay earnings, and to meet any legal or insurer requirement that applies to delivery operations. A document supplied for verification is used for verification and account administration, is visible only to staff with an onboarding or compliance need, and is retained only for as long as the rider account and any legal duty require, after which it is deleted or archived in restricted form under the retention schedule approach for account records.
Rider application data during work includes availability and duty status, assigned orders, pickup and drop details including the drop location and delivery instructions for an assigned order, delivery completion records, customer ratings for deliveries, earnings records, device and technical data, and location data while on duty as described in the location clause. A rider may access her or his own profile, earnings and delivery history through the application, and may exercise data principal rights in respect of rider account data for which BizSensei Digital or the engaging restaurant or delivery operator is fiduciary, following the roles stated in the engagement: where a rider is engaged by a restaurant directly, that restaurant is fiduciary for the engagement data it controls, and BizSensei Digital assists as processor in the same way as for customer data.
12. Point of sale, waiter and kitchen flows
OMS point of sale and waiter ordering flows process order data at the table, counter and kitchen. A waiter order may record the table, the staff account, items, notes including allergy or preparation instructions given by the diner at the table, and the bill and payment settlement method. Customer personal data in a dine in flow is ordinarily limited to what the diner volunteers or what is needed for billing, a tax invoice in the diner's name, a phone number for a bill copy or loyalty record where the restaurant offers it, and payment settlement data handled at the restaurant's own terminal or gateway. Kitchen display and ticket systems receive the order content needed for preparation, including order notes, and do not need the customer's payment or contact data, which is therefore not displayed on kitchen tickets beyond any identifier the restaurant's configuration genuinely requires for order matching.
Offline or continuity modes, where the product provides them, store orders on the device or outlet system until connectivity returns and then synchronise them to the account. During an offline period, the restaurant is responsible for the physical and device security of the outlet system holding unsynchronised orders. On synchronisation, the orders become operational data under the processor terms of this part. If a synchronisation conflict or failure causes a record to be duplicated or lost, BizSensei Digital will assist the restaurant in reconciling the affected orders from available logs, and affected customers' rights in respect of any incorrect record will be honoured through the restaurant with BizSensei assistance.
13. OMS integrations and marketplace platforms
OMS may integrate, at a restaurant's direction, with external ordering platforms, accounting tools, communication providers and other services the restaurant selects. Where a restaurant enables an integration that transmits order or customer data to an external platform, for example an order originating on an external food platform and flowing into OMS, or a bill flowing to the restaurant's accounting tool, that transmission occurs on the restaurant's instruction and under the restaurant's agreement with that platform. The external platform's privacy policy governs its own handling of data it receives as fiduciary or processor under its terms with the restaurant. BizSensei Digital will transmit only the fields the integration is designed to transmit, will record integration transmissions in logs sufficient to investigate a failure, and will disable an integration on the restaurant's instruction or where it presents a clear security risk, with notice to the restaurant.
14. OMS retention, export and account closure
A restaurant may export its operational data through the export features provided in the product, for its own accounting, migration or record keeping, subject to the account's permissions and plan. On termination of an OMS account, BizSensei Digital will make operational data available for export for a reasonable closure window stated in the contract or account closure notice, after which processor held operational data will be deleted or anonymised in accordance with the retention schedule and the contract, except for records BizSensei Digital must keep as its own fiduciary records: the restaurant account record, billing and tax records, consent logs, security logs and support records evidencing the relationship. A restaurant that needs a longer export window for its own legal duties should request it before the closure window expires, because deletion after that window is designed to be irreversible in live systems.
Individual food ordering customers and riders exercise their rights as described in Part A, routed according to the layer of data involved. Profile, saved address and application account data for which BizSensei Digital is fiduciary will be handled directly by BizSensei Digital. Order data held inside a particular restaurant's fiduciary relationship will be handled through that restaurant with BizSensei assistance as processor, as described in Part A. In practice BizSensei Digital will not use that routing distinction to delay a request: a request received at info@bizsensei.co.in will be logged, the responsible layer identified, and the requester told who is handling it and what the next step and timeline are.
Part G: Qiaomed
Applies to: qiaomed.space
1. Scope, status and care standard
This part applies to Qiaomed at qiaomed.space, a healthcare product of BizSensei Digital for clinics, practitioners and pharmacies, covering practice management, patient records, prescriptions, appointments and pharmacy dispensing support. It supplements Part A in full. Qiaomed is currently in pre-launch, and this part therefore deals first with waitlist data collected before launch, and then with the full patient, practitioner and pharmacy data model that will apply when the product is live, so that practitioners and patients who join the waitlist or evaluate the product can read, in advance, exactly how health data will be handled. Health data is treated throughout Qiaomed as sensitive personal data requiring the highest level of protection available in this policy.
The care standard for Qiaomed is consent, purpose limitation and restricted access. No health data is collected without a lawful basis centred on the patient's consent or on the treatment relationship the patient has entered into with the treating practice, no health data is used for a purpose beyond the care, dispensing, billing and practice administration purposes for which it was provided, and no health data is accessible to any person other than the treating practice, the patient herself or himself, and those acting strictly on their behalf or under a legal duty, as detailed in the access clause below. Qiaomed data is never sold, never used for advertising, and never used to profile a patient for marketing by BizSensei Digital or by any other business.
2. Pre-launch and waitlist data
Before launch, Qiaomed collects waitlist data only: name, contact details and practice details. A practitioner, clinic owner, pharmacy operator or other interested person who joins the Qiaomed waitlist provides a name, an email address and or a mobile number, the name and type of the practice or pharmacy, its town or city area in general terms where the form asks for it, the size or nature of the practice where the person chooses to describe it, and any message the person writes about what she or he needs from the product. No patient data, no prescription data and no clinical data should be submitted through the waitlist, and the waitlist form does not ask for any such data. If a person mistakenly includes patient information in a waitlist message, BizSensei Digital will delete that patient information from the waitlist record on discovery and will advise the sender not to transmit patient data outside a clinical system.
Waitlist data is used only to communicate launch. That means sending launch announcements, early access invitations, onboarding information and a reasonable number of pre-launch updates about the product the person asked to hear about, and administering the order and allocation of early access where places are limited. Waitlist data is not added to a general BizSensei marketing list for unrelated products, is not shared with any clinic, pharmacy or third party for their marketing, and is not used to infer anything about the health of the person who joined the list, who is ordinarily a practitioner or business operator rather than a patient in that context. A person may leave the waitlist at any time by the unsubscribe mechanism in any waitlist email or by writing to info@bizsensei.co.in, and on launch the waitlist record is either converted into an account record where the person proceeds to register, with fresh notice and consent at registration, or deleted on the waitlist retention rule in Part A where no account follows.
3. Patient identity and contact data in the live product
When Qiaomed is live, patient identity and contact data entered into a practice's Qiaomed account will include the patient's name, date of birth or age where the practice records it for clinical identification, gender where clinically relevant and recorded by the practice, mobile number, email address where provided, address where needed for billing, home delivery of dispensed medicines or clinical correspondence, an emergency contact where the patient provides one, and a patient identifier assigned within the practice's account. That data is entered by the practice from information the patient provides to the practice, or by the patient herself or himself through a patient facing flow where the practice has enabled one, in which case the consent gate and notice for that flow will apply.
The practice is the data fiduciary for its patients' data. The practitioner or clinic that provides care to the patient determines what patient data to record, why it is clinically or administratively necessary, how long clinical records must be kept under applicable law and professional obligations, and who on the care team may access the record. BizSensei Digital, as provider of the Qiaomed software, processes patient data as processor on the practice's instructions, provides the access controls, audit logs and security measures described in this part and in Part A, and does not determine the clinical content of any patient record. A patient should therefore address questions about why a particular item is recorded in her or his clinical record to the treating practice, which can explain the clinical reason, while BizSensei Digital will assist the practice in locating, correcting or exporting the record as instructed.
4. Prescriptions, clinical notes and health records
Prescriptions and clinical notes entered by practitioners form the most sensitive category in Qiaomed. This category includes consultation notes, presenting complaints, examination findings, diagnoses and assessments recorded by the practitioner, investigation orders and results that the practice uploads or enters, prescriptions including medicine name, strength, dosage, frequency, duration and instructions, treatment plans, referral notes, follow up instructions, and attachments such as reports or images that the practice or the patient adds to the record for care purposes. Each entry is attributed to the practitioner or authorised staff account that made it, with a timestamp, so that the clinical record shows who recorded what and when, and edits to a clinical entry are handled as amendments that preserve the record's integrity rather than as silent overwrites, in accordance with good clinical record practice.
Health data in Qiaomed is subject to strict purpose limitation. It may be used by the treating practice to provide care to the patient, to prescribe and dispense safely, to maintain the clinical record the law and professional standards require, to bill for the care provided, and to communicate with the patient about her or his care, appointments and prescriptions. It may not be used by the practice through Qiaomed, or by BizSensei Digital in any way, for advertising, for sale, for unrelated research, or for any decision about the patient in a non clinical context such as employment, insurance eligibility or credit, unless a separate lawful basis, the patient's explicit consent where consent is the proper basis, and, for research, applicable ethics and legal requirements, are all independently established and documented outside the ordinary treatment flow. BizSensei Digital will not access the content of clinical notes or prescriptions for its own purposes; support access to a clinical record occurs only where the practice requests support that cannot be provided without it, is limited to the specific record and issue, is logged, and ends when the support issue is resolved.
Patients should understand that a clinical record is also a legal and professional record. A practitioner may be required to keep a prescription or consultation record even after a patient asks for erasure, because medical record retention duties and the practitioner's need to evidence care given can constitute a legal basis for continued retention in restricted form. The retention clause in this part explains that balance, and the rights clause explains how a patient can obtain a copy of her or his record, seek correction of factual errors, and add a statement where a clinical opinion recorded in good faith is disputed, which is ordinarily the professionally appropriate remedy for a disputed opinion rather than alteration of the practitioner's contemporaneous note.
5. Pharmacy dispensing data
Pharmacy dispensing data in Qiaomed includes the prescription presented or transmitted for dispensing, the patient name and contact detail needed to identify the correct patient and to communicate about the dispensing, the medicines dispensed including name, strength, batch and expiry details where the pharmacy records them for safety and recall purposes, quantity, dispensing date, the pharmacist or staff account that dispensed, substitution or partial dispensing notes where applicable and lawful, billing data for the dispensing transaction, and delivery data where the pharmacy delivers medicines to the patient. That data is processed to dispense accurately and safely, to check the dispensing against the prescription, to maintain the dispensing record the pharmacy must keep under applicable drugs and pharmacy law and professional standards, to enable a product recall to reach affected patients, and to bill and account for the sale.
Where a prescription originates from a practice using Qiaomed and is dispensed by a pharmacy using Qiaomed, only the prescription and patient data needed for dispensing pass from the practice context to the pharmacy context, and that flow occurs on the patient's direction or the practice's referral at the patient's request, as presented in the product flow at the time. A pharmacy does not receive access to the patient's full clinical record merely because it receives a prescription for dispensing: consultation notes, history and unrelated prescriptions are not shared with the pharmacy unless the patient or the treating practitioner expressly directs a specific item to be shared for a dispensing safety reason, such as an allergy relevant to the medicine being dispensed. A pharmacy that collects patient data directly at its own counter remains an independent fiduciary for that directly collected data, in the same way as restaurants under Part F.
6. Who can access what in Qiaomed
Access in Qiaomed is role based and restrictive, and this clause states the access model in full. The patient can access her or his own record through a patient account or through a copy provided by the practice, limited to her or his own data. The treating practitioner can access the records of patients of that practice to whom she or he provides care or provides cover within the same practice. Authorised staff of the practice, such as a receptionist managing appointments or an assistant preparing a visit summary, can access only the categories their role requires: appointment and contact data for scheduling roles, billing data for billing roles, and clinical data only for clinical roles acting under a practitioner's responsibility. A pharmacist and authorised pharmacy staff can access dispensing data and the prescriptions presented to that pharmacy, as described in the pharmacy clause, and not the wider clinical record.
| Who | What they can access | What they cannot access |
|---|---|---|
| Patient | Own identity, contact, appointment, prescription and dispensing records, through own account or a copy from the practice | Any other patient's data, practice internal notes not forming part of the patient's record, other practices' data |
| Treating practitioner | Full clinical record of own practice's patients for care, prescribing and record keeping | Records of patients of an unrelated practice, BizSensei internal systems beyond the practice account |
| Practice clinical staff | Clinical data needed for their clinical role under practitioner responsibility, attributed to their own login | Records outside the practice, bulk export except where the practice authorises an export role |
| Practice administrative staff | Contact, appointment and billing data needed for scheduling and billing | Clinical notes and prescriptions except a specific item a practitioner directs them to process |
| Pharmacy staff | Prescriptions presented to that pharmacy, dispensing and related billing and delivery data | Full clinical record, consultation notes and unrelated patient history held by a practice |
| BizSensei support | Account, technical and log data; a specific clinical record only where the practice requests support requiring it, logged and time limited | Routine browsing of clinical content, any use of health data for BizSensei marketing, analytics or product profiling of patients |
No access under the table above permits downloading, copying or exporting patient data for a purpose outside the role described. Bulk exports from Qiaomed are restricted to authorised practice roles, are logged, and are the practice's responsibility once exported, because BizSensei Digital cannot control a file the practice has taken into its own systems. A practice must promptly remove Qiaomed access for staff who leave or change roles, must use individual logins for every staff member so that the audit trail is accurate, and must report suspected unauthorised access by its own staff to BizSensei Digital promptly so that account level containment can be applied while the practice investigates as employer and fiduciary.
7. Practitioner responsibility and professional obligations
Practitioner responsibility for clinical records and professional obligations under applicable medical laws and the Telemedicine Practice Guidelines where relevant rests with the practitioner and the practice. Each practitioner who uses Qiaomed remains responsible for the accuracy and completeness of the clinical entries she or he makes, for verifying patient identity to the standard her or his profession requires before prescribing, for ensuring that a remote consultation, where the Telemedicine Practice Guidelines apply, is conducted only in the circumstances, by the methods and with the documentation those guidelines permit, for prescribing only medicines that may lawfully be prescribed in the mode of consultation used, and for obtaining and recording patient consent for a teleconsultation where the guidelines or applicable law require it.
Qiaomed provides tools to support those obligations, including identity fields, consent recording fields, attributed and timestamped notes, prescription records and audit logs, but the provision of a tool does not discharge the practitioner's professional judgement or transfer professional liability to BizSensei Digital. A practice must configure its Qiaomed account, its staff roles and its retention practice to meet the obligations of the law applicable to its profession and State, including medical council requirements, clinical establishments legislation where applicable, drugs and cosmetics legislation and pharmacy obligations for dispensing records, and information technology requirements for sensitive personal data. Where a professional obligation and a patient request conflict, for example a request to delete a record the practitioner must by law retain, the practitioner will explain the conflict to the patient, retain the record in restricted form for the legally required period, and record the request and the reason it could not be fully granted.
8. Health data as sensitive personal data: consent and security
Health data is treated as sensitive personal data with consent and purpose limitation throughout Qiaomed, as stated in Part A and applied here with additional measures. At patient registration or first record creation by a practice, notice will be given of the categories of health data the practice records, the purposes of care, record keeping, dispensing and billing, the persons and roles who may access the record as described in this part, and the patient's rights. Consent for the processing of health data for care will be recorded in the manner the product flow and the practice's own patient documentation provide, and a patient who declines consent for non essential processing, such as receiving general health information messages from the practice, will still receive care and essential care communications, because optional processing is separated from treatment processing.
Security for Qiaomed follows the security programme in Part A, applied at its highest level for health data: encryption in transit for all patient facing and practice facing connections, hashed or tokenised authentication credentials, least privilege access enforced by the role model in this part, session controls for practitioner accounts, logging of access to patient records sufficient for the practice and BizSensei Digital to investigate a suspected unauthorised access, and backups protected with the same access controls as live data. BizSensei Digital describes these measures generically and does not claim any external certification for Qiaomed in this policy. A practice must complement platform security with its own device and premises security: a shared or unlocked clinic device undermines platform controls, and BizSensei Digital is not responsible for a disclosure that occurs because a practice's own device or staff practice exposed a record that the platform had correctly restricted, without prejudice to BizSensei Digital's duty to assist in investigating and containing such an incident once reported.
9. Patient rights in Qiaomed
A patient may exercise all the data principal rights in Part A in respect of Qiaomed data, routed through the treating practice as fiduciary, with BizSensei assistance as processor, and directly to BizSensei Digital through the grievance route if the practice does not respond. In practical terms, a patient may request a summary and copy of her or his record, may request correction of factual inaccuracies such as a wrong phone number, a misspelled name or an incorrectly recorded allergy, may request that a disputed clinical statement be noted with the patient's own statement, may withdraw consent for optional processing, may nominate a person to exercise rights on death or incapacity, and may complain first to the practice and to the BizSensei Grievance Officer, and thereafter to the Data Protection Board of India, following the escalation order in Part A.
Erasure in Qiaomed is subject to the clinical retention balance already explained. Qiaomed records retention follows this rule: clinical records retention is the practitioner's duty under applicable law. BizSensei Digital will erase or anonymise processor held patient data on the practice's documented instruction when the practice determines that its retention duty has expired or that erasure is otherwise proper, and will erase waitlist, account contact and optional communication data on the patient's own request where BizSensei Digital is fiduciary for that data and no duty requires its retention. Where a practice has ceased using Qiaomed, patient records held as processor will be exported to the practice or its nominated successor system during the closure window and then deleted from Qiaomed live systems, because continuity of the clinical record with the responsible practitioner, and not indefinite retention by a former software provider, is the correct outcome for patients.
10. Qiaomed communications and appointments
Qiaomed communications include appointment confirmations and reminders, prescription ready and dispensing notifications, follow up reminders configured by the practice, and care instructions the practitioner sends to the patient. Those communications are sent on behalf of the practice or pharmacy, contain only the personal data needed for the message, and should be read with care by patients who share a phone or email account with family members, because an appointment reminder sent to a shared number will be visible to anyone with access to that number. A patient who needs communications to be sent to a different or more private channel should tell the practice, which can update the contact preference in the record. Marketing communications are not sent to patients through Qiaomed by BizSensei Digital, and a practice may use Qiaomed communication tools for its own patient marketing only where it has a lawful basis as fiduciary and the message carries the opt out required by Part A, noting that clinical and appointment messages are not marketing and cannot be opted out of while the underlying care or appointment is active, although the channel for them can be changed at the patient's request.
Closing provisions
1. Changes to this policy
BizSensei Digital may change this Privacy Policy from time to time to reflect changes in law, in the properties it operates, in the processors it uses, or in its own practices. A material change will be notified before it takes effect for future processing, by a prominent notice on the affected property and, where account holder contact details are held, by email or account notice to affected account holders, stating the version number and date of the new version, a summary of what has changed, and the date from which the change applies. The version and last updated lines in the introduction to this policy will be updated with every version, and earlier versions will be retained in BizSensei records so that the version applicable to a particular transaction or consent can be identified from the consent log for that transaction.
A change to this policy does not retroactively authorise processing that was not authorised under the version in force when the data was collected. Where a change proposes a new purpose for existing personal data that requires fresh consent, processing for that new purpose will not begin for existing data until the fresh notice and consent steps described in Part A have been completed for the affected data principals. Continued use of a property after a notified change takes effect will be treated as acknowledgement of the change for future processing, but it will not be treated as consent to a new purpose for which the DPDP Act requires express consent by clear affirmative action; such consent will always be sought by an explicit action.
2. How the parts of this policy work together
This policy is a single document with a general part, property parts and these closing provisions. If a statement in a property part appears to conflict with a statement in the general part, the interpretation that provides the greater protection to the data principal and the fuller compliance with the DPDP Act should be preferred, unless the property part expressly states a specific rule for that property that the general part contemplates, such as a property specific retention rule for blog comments or clinical records. Headings are for convenience and do not limit the meaning of the text beneath them. If any provision of this policy is held by a competent authority to be unenforceable, the remaining provisions continue in full effect, and the unenforceable provision will be read, so far as possible, in the manner closest to its original intent that is enforceable and lawful.
3. Contact
For any question about this policy, for a data principal rights request, for a correction, for an opt out that you cannot complete through an automated mechanism, or for any privacy concern about any BizSensei property, please contact BizSensei Digital by email at info@bizsensei.co.in or by phone at +91 93726 65745. Please identify the property concerned, the account, order, practice or article involved where relevant, and the nature of your request, so that it can be routed correctly the first time. BizSensei Digital does not publish a physical address, and written communication should therefore be sent by email, which also creates the dated record that both sides need for rights and grievance timelines.
4. Grievance escalation order restated
The grievance escalation order for this policy is restated here so that it is the last operative statement a reader encounters. First, contact the Grievance Officer, which is a role within BizSensei Digital, at info@bizsensei.co.in, marking the message as a grievance and describing the matter clearly; your grievance will be acknowledged within 48 hours and resolved within one month, in alignment with the Consumer Protection (E-Commerce) Rules, 2020 where the grievance concerns the store. Second, if the matter remains unresolved, escalate within BizSensei Digital by writing again to the same address referring to the original grievance. Third, only after exhausting grievance redressal with BizSensei Digital may a complaint be made to the Data Protection Board of India under the DPDP Act. This order does not remove any direct right a court or another competent authority gives you under law, and nothing in this policy limits a data principal's statutory rights under the DPDP Act, which is the express saver on which this policy closes.
End of Privacy Policy, Version 2026-10-23, BizSensei Digital. Thank you for reading this policy in full. If any part of it is unclear, please ask at info@bizsensei.co.in before providing personal data, and we will explain the relevant part in plain language for your situation.