Cookie Policy

Part A: General

Applies to: All BizSensei Digital properties

1. Scope of this part

This part applies to every property operated by BizSensei Digital, including the websites and products covered in Parts B to G of this policy, any future subdomain or successor address that links to this policy, and the native applications described in Part F. Where a later part states a more specific rule for a particular property, the specific rule governs that property and this part continues to govern everything else. If you use more than one property, for example you read the blog, buy from the store and work in the OMS dashboard, each property stores its own choices separately unless the text expressly says otherwise.

2. What a cookie is

A cookie is a small text file that a website asks your browser to store on your computer, phone or tablet. When you return to the same website, or move to another page on it, your browser sends the cookie back. That round trip lets the website recognise the same browser across page views, remember that you are signed in, keep temporary information such as a basket or an order while you build it, and recall choices you made earlier. A cookie by itself is not a program. It cannot run code on your device, it cannot contain a virus, and it cannot read unrelated files stored on your device.

The information inside a cookie is usually a short identifier and a small amount of state, such as a session reference, a preference value or a timestamp. Some cookies contain no personal data at all, for example a flag that records that a banner was dismissed. Others become personal data when they can be linked to you or to your account, for example a session identifier attached to a signed in profile. Where this policy refers to personal data, it uses the meaning given in the Digital Personal Data Protection Act, 2023, namely data about an individual who is identifiable by or in relation to that data.

3. Similar technologies covered by this policy

Modern websites and applications rely on several related technologies that behave like cookies even though they are technically different. This policy uses the word cookies in a broad sense to cover all of them, and it names the specific technology wherever the distinction matters for your control choices.

• Local storage: browser storage that persists until it is cleared by the website or by you. It is not sent automatically with every request, and it is commonly used for preferences, drafts and offline queues.
• Session storage: browser storage that lasts only for the current tab session and is discarded when the tab is closed. It suits temporary form state and single visit workflows.
• Secure token storage in apps: protected storage provided by the phone operating system or by the application itself, used by our native apps to keep sign in tokens so that you do not have to log in again on every launch.
• Device identifiers: identifiers generated by an app or read with permission from the device, used to distinguish one installed app or one delivery device from another for security, routing and support.
• Pixels and web beacons: tiny loading requests, sometimes embedded as an invisible image, that signal that a page or a message was opened. We describe any use of this kind in the relevant property part rather than treating it as invisible by default.
• Tags and scripts: small pieces of code that load a feature, such as a checkout, an embed or a measurement tool. A tag may set cookies of its own, and when it does, the provider of that tag is identified in the relevant part.
• Cache entries and service data: files a browser or app keeps locally so that pages and screens load faster on a repeat visit. Cache entries are storage for performance, not a substitute for the consent choices described in this policy.

4. First party and third party cookies

A first party cookie is set by the property you are visiting. If you are on the store, a first party cookie is set under the store domain by BizSensei Digital. First party cookies support sign in, security checks, baskets, consent records and preferences for that same property. We are responsible for the first party cookies described in this policy, for the purposes for which they are set, and for honouring the choices you make about them.

A third party cookie is set by a different organisation whose feature appears inside our property, for example a payment provider whose checkout is embedded in the store, or a video provider whose player appears in a blog article. We do not control how a third party designs its cookies, how long it keeps the resulting data, or how it combines that data with information from other websites. Third party cookies are governed by the third party provider's own cookie and privacy policies, and you should read those policies for the provider concerned. We choose providers carefully, we describe their role here in good faith, and we limit third party features to purposes that are explained on the page where they appear.

5. Session cookies and persistent cookies

A session cookie exists only while your browser session continues. It is normally deleted when you close the browser, and it is suited to information that should not outlive the visit, such as a short lived security token, a single checkout attempt or the contents of an order being built on a customer ordering page. Closing the browser is therefore a simple way to end most session based storage, although an app or a browser setting that restores tabs may preserve some session state for convenience.

A persistent cookie stays on your device for a stated period, such as 30 days or 12 months, or until you delete it earlier. Persistent storage is used only where remembering something between visits is the point of the feature, for example your consent choice, a remembered sign in on a trusted device that you expressly opted into, or a dashboard preference. Every persistent item described in this policy has a maximum duration in the tables that follow, and the actual life may be shorter if you clear storage, if the purpose is completed sooner, or if we retire the feature.

6. Why we use cookies at all

We use cookies and similar technologies for a limited set of purposes, each of which maps to a category in Clause 7 of this part. The purposes are security and fraud prevention, essential operation of the property, remembering preferences and convenience choices, understanding aggregate usage so that we can improve content and reliability, and enabling a specific third party feature that you choose to use, such as paying online or playing an embedded video.

We do not use cookies for behavioural advertising. We do not sell cookie data. We do not share cookie data with advertisers, data brokers or ad exchanges. We do not build advertising profiles from your browsing on our properties, and we do not use a cookie set on one property to advertise to you on an unrelated website. If any of those positions ever changes, the change will be treated as a material change under the closing provisions of this policy: this page will be updated first and fresh consent will be requested before any new optional cookie is set.

7. The four categories used across the ecosystem

Every cookie and comparable storage item in this policy is assigned to one of four categories. The category decides whether consent is needed, whether the item can be switched off inside the property, and what happens if you block it. The same four labels are used in every property part so that you can compare properties without learning a new vocabulary each time.

The category of an item is decided by its purpose, not by its name or by who sets it. A third party item can be strictly necessary, for example the storage a payment gateway needs to complete a payment you requested. A first party item can be optional, for example a preference we remember only because you agreed. Where an item serves two purposes, we classify it by the more sensitive purpose and apply the stricter consent rule.

8. Master table of cookies and storage across the properties

The table in this clause is the master inventory for the ecosystem. It gathers the principal cookies and storage items described in the property parts so that you can see the whole picture in one place. Individual property parts repeat the rows that belong to them with additional detail about that context. Durations are maximums unless the row says session, in which case the item ends with the session described in that row.

9. Representative names and the limits of any inventory

Cookie names in this policy are representative examples where a complete enumeration is not practical. Names can differ slightly between browsers, product versions, hosting configurations and provider releases, and a provider may rename a cookie without changing its purpose. A difference in an exact name therefore does not mean that an undisclosed purpose is being pursued. What we commit to is accuracy about purposes, categories, consent positions and maximum durations. If a new purpose or a new category is introduced, this policy is updated and, where consent is required, fresh consent is requested before the new item is set.

The tables in this policy are updated as the properties evolve. When we add a routine strictly necessary item for security or reliability, we add it to the relevant table at the next policy revision. When we retire a feature, the related rows are removed and any stored values that are no longer needed are allowed to expire or are deleted in the ordinary course of system maintenance. You should treat the version date at the top of this page as the date against which the inventory was last reviewed as a whole.

10. The consent block and the consent record

Across this ecosystem, information is not collected behind a silent assumption. Our websites and sign up flows show an agreement block built around an I agree with all control. Opening that control shows each legal document that applies to the action you are about to take, with its own checkbox and a link to the full text, a select all option for convenience, and a continue control that stays disabled until every required document has been ticked. The design is deliberate: agreement is an active step, not a pre ticked bundle, and consent for cookies is never bundled with unrelated processing. Agreeing to terms for an account, for example, does not by itself switch on analytics cookies. Optional cookies have their own choice.

When you make a consent choice, two things are created. The first is a consent flag stored on your device, described in the master table as the cookie_consent style flag. That flag records the choice itself, such as optional cookies accepted or optional cookies rejected, together with the versions of the documents or the cookie categories that were shown to you. The flag stores no directly identifying information by itself. It does not contain your name, your email address or your phone number. It is a machine readable memory of a choice, designed so that the property does not ask you the same question on every page view.

The second thing created is a consent record held on our systems where the flow involves providing information, such as a sign up, a checkout or a lead form. That server side record logs the context of the agreement, an identifier for the transaction or account where one exists, the documents and versions accepted, the date and time, and technical details such as the internet protocol address as received directly and through any forwarding service, and the browser or app user agent string. The server record exists so that both you and we can later establish what was agreed, in which version, and when. It is evidence of consent, not a marketing list, and it is not used to set advertising cookies.

11. How long a consent choice is remembered

On websites, the consent flag described in Clause 10 of this part lasts for 12 months from the choice. After 12 months it expires and the consent block is shown again so that you can confirm or change your position against the current version of this policy. The same 12 month memory applies where a property uses local storage rather than a classic cookie to hold the flag, unless the relevant property part states a shorter period. Expiry is automatic. You do not need to do anything to trigger it, and expiry does not delete your account or any separate record we are required to keep for legal or accounting reasons.

In the native apps, the consent and sign in state is held as a local record inside the app, supported by secure token storage where the platform provides it. That record lasts until you log out, until the token expires or is revoked for security reasons, until you clear the app storage through your device settings, or until you uninstall the app. An app update that is installed over the existing app normally preserves the record, because the update is treated as the same app on the same device. A fresh install on a new device starts with no memory of the earlier choice.

12. A new device, a new browser and private browsing

Consent is stored per property and, on websites, per browser and device. If you accept optional cookies on your phone browser, that choice does not travel to your laptop, to a different browser on the same phone, or to a browser profile used by another person in your household. On a new device or a new browser you will be asked again. That repetition is not an error. It is the consequence of storing the choice on the device rather than building a cross device profile of you, which we do not do for cookie consent.

Private or incognito windows are treated by browsers as temporary sessions. A consent choice made inside a private window normally disappears when the last private window is closed, so the consent block will appear again in the next private session. Similarly, browsers that are configured to clear cookies on exit will clear the consent flag on exit. In each case the result is the safe one: optional cookies remain off until a fresh choice is made in that new session.

13. Withdrawing consent and changing your mind

Withdrawing consent must be as easy as giving it, and rejecting optional cookies must be as easy as accepting them. There is no penalty wording, no repeated nagging loop and no design that hides the reject route. You can change your mind in any of these ways: reopen the consent block or cookie settings control on the property and make a new choice; clear the consent cookie or the site storage for that property in your browser, which causes the block to be shown again; clear the app storage or log out inside a native app, as described in Part F; or write to us at info@bizsensei.co.in and ask us to record a withdrawal for an account based service.

Withdrawal takes effect immediately for future setting of optional cookies. It does not rewrite history. Analytics data already aggregated before withdrawal, consent records that evidence an earlier agreement, and records we must keep for legal, tax or security reasons are handled under the retention rules in the closing provisions and in the Privacy Policy. Cookies already on your device at the moment of withdrawal remain there until they expire or until you delete them in your browser, because a website cannot reach into your browser and erase storage on command. Clause 18 of this part and the property parts explain the deletion steps for each browser and device.

14. Global Privacy Control and Do Not Track

Some browsers and extensions can send a Global Privacy Control signal, often shortened to GPC, which communicates a preference not to have personal information sold or shared and not to be tracked for optional purposes. As a policy choice, BizSensei Digital honours a detected GPC signal as an opt out for optional cookies on its websites. In practice that means analytics and functional cookies that require consent are treated as not consented where a GPC signal is present, unless you later make an express contrary choice in our own consent block after seeing the documents presented there. Honouring GPC is our voluntary commitment in this policy. It does not create a marketing use to opt out of, because we do not sell cookie data and we do not set marketing cookies.

Do Not Track, often shortened to DNT, is an older browser signal with no universally agreed response standard. Our position, carried forward consistently across our properties, is that our behaviour does not change in response to a DNT signal alone. The consent choice governs. If you reject optional cookies in the consent block, no analytics or functional cookies are set regardless of DNT. If you accept them, the acceptance you gave in the block is the instruction we follow. We state this plainly so that you do not rely on a DNT toggle in the mistaken belief that it has replaced the consent choice on our properties.

15. Analytics without a fingerprinting fallback

Where analytics is offered, it is offered honestly. If you reject analytics cookies, no analytics cookies are set. We do not replace them with browser fingerprinting, canvas based identification, font enumeration, device graph matching or any other workaround designed to recognise you after you said no. Server logs that are kept for security and reliability are a different matter and are described in the Privacy Policy. They are not used as a covert analytics substitute to rebuild the visit statistics that consent was refused for.

Where you do consent to analytics, we configure the tools to collect aggregate information wherever the provider supports it, such as pages viewed, approximate visit duration, referral source and broad device class. We do not use analytics on our properties to identify you by name in a report, to record the contents of forms you did not submit, or to capture passwords, payment details or private messages. If a provider changes its product so that a previously acceptable configuration is no longer available, we will either reconfigure, replace or remove the tool rather than quietly accept a more intrusive default.

16. Marketing cookies: none anywhere

No property covered by this policy sets marketing or advertising cookies at the date of this version. There is no behavioural advertising programme to describe, no advertising identifier is created by us, no remarketing list is built from our properties, and no cookie data is sold or rented. Social media links on our pages are links. Following a link takes you to that platform under its own policies. The mere presence of a link or an icon does not set a platform cookie on our property before you interact with it, except where a property part expressly describes an embedded feature and the interaction that loads it.

17. Security of cookie based information

Cookies and tokens that protect accounts are treated as security material. Session identifiers and remember me values are generated with randomness suitable for that purpose, remember me values are stored on our side in hashed form so that a database disclosure does not directly reveal usable tokens, and sensitive cookies are marked for protected transmission and restricted access by scripts where the property configuration supports those flags. You play a part in that security as well. Do not share a signed in device without logging out, do not tick remember me on a public or shared computer, and log out of the OMS on any device that leaves your control.

18. Browser controls in general

Every major browser lets you view, block and delete cookies, and the detailed steps for Chrome, Firefox, Safari and Edge appear in the property parts and are summarised again in Part B, which carries the fullest browser guidance inherited from our long standing public guidance. The general principles are the same everywhere. You can usually block all cookies, block only third party cookies, allow cookies only for listed sites, clear cookies for one site without clearing everything, and order the browser to clear cookies when it closes. Blocking only third party cookies is a middle course many visitors choose, although it will still prevent an embedded checkout or an embedded video from working where that feature genuinely needs its own storage.

Browser controls act on the browser you use them in. Clearing cookies in Chrome does not clear Safari, and neither action clears storage inside a native app. If you use several browsers or several devices, repeat the steps in each place where you want the result. The property parts therefore give both browser steps and, for the apps, device steps for Android and iOS.

19. Consequences of disabling cookies in general

The consequences of blocking cookies depend on the category blocked, and each property part gives the specific list for that property. In general, blocking strictly necessary cookies prevents sign in, causes baskets and in progress orders to be lost, makes protected forms fail their security checks, and prevents online payment from completing. Blocking functional storage removes remembered preferences and causes the consent block to reappear because the choice can no longer be recorded. Blocking analytics storage has no visible effect on your use of a property. Deleting a session cookie in the middle of a visit can sign you out without warning and can restart a checkout from the beginning.

20. Retention of cookie data and related logs

A cookie retained on your device is retained for the duration stated in the tables, unless you delete it sooner. Data generated on our side from the use of cookies, such as security logs, consent records and aggregate analytics reports, is retained only for as long as it is needed for the purpose that generated it, for the protection of accounts and services, or for compliance with a legal obligation. Aggregate analytics that no longer identifies a browser or a person may be kept for longer trend comparison. Detailed operational logs are rotated and deleted in the ordinary course of hosting and security maintenance, and they are not kept indefinitely merely because storage is available.

21. Children

Our public websites are directed at adults running or evaluating businesses, and the OMS and related apps are workplace and consumer ordering tools provided through restaurants and our business customers. We do not target optional cookies at children, we do not knowingly set analytics or preference cookies for the purpose of profiling a child, and we do not offer any child directed advertising feature, because we offer no advertising feature at all. Where a service is used by a family, for example a customer ordering food through the Food app or an ordering page, the consent and account choices should be made by the adult account holder. If you believe that a child's information has been provided to us without appropriate consent, write to us using the contact details in this policy and we will review the concern under the Privacy Policy.

22. Cross references and precedence

This policy deals with cookies and similar technologies. It does not replace the Privacy Policy, which is the primary document for personal data, lawful bases, sharing, retention and data principal rights. It also does not replace the terms that govern a purchase, a subscription or a service engagement. If a statement in this policy conflicts with a mandatory protection in the Digital Personal Data Protection Act, 2023 or the Consumer Protection Act, 2019, the mandatory protection prevails and the statement in this policy is to be read down to the extent needed to comply with it.

Part B: bizsensei.co.in

Applies to: bizsensei.co.in, the main BizSensei Digital showcase website

1. What this property is

bizsensei.co.in is our main public website. It presents our software products, including BizSensei OMS, explains what each product does, carries product pages and supporting information, and provides contact and enquiry routes. It is a showcase and information property. Commerce, billing, checkout and account based purchasing are handled on the store described in Part C, not on this website, and product operation itself happens inside the OMS described in Part F. That separation matters for cookies, because this website needs far less transactional storage than a checkout or a working dashboard.

2. Cookies this website sets

On this website we set a small set of first party cookies for session continuity, form security, consent recording and load and security protection. A visitor who only reads public pages, without signing in to any restricted area and without submitting a form, will encounter mainly the consent flag and any strictly necessary technical flags needed to serve the page safely. Restricted areas, where access is provided to our team or to authorised users, add a session identifier so that the signed in person is recognised from page to page without entering credentials repeatedly.

3. Contact forms and enquiry flows on this website

When you submit a contact or enquiry form on this website, the consent block described in Part A applies before information is taken. The form itself uses a session cookie and a CSRF token so that the submission can be validated as coming from the form we served to your browser. Those items do not track you across other websites. If you abandon a form before submitting it, the session storage connected with that attempt ends with the session, and no enquiry is created from a half completed form merely because a cookie existed.

4. Analytics on this website

Analytics on this website is optional and consent based. Its purpose is practical: to see which product pages are actually read, which explanations are confusing enough that visitors leave quickly, and whether important pages load and are found as intended. Reports are read in aggregate. We do not use the analytics on this website to decide a price for you, to change the product information shown to you based on a profile, or to follow you to other websites with advertising. Rejecting analytics leaves every public page, product description and contact route fully available.

5. No shop checkout on this website

Because purchasing has moved to the store, this website does not operate its own product checkout and does not set shop cart cookies for a purchase journey of its own. Historical references in older versions of our cookie guidance to a shop on the main website should be read in that light. Where a page on this website links to the store, the store's cookies begin only when you arrive on the store, under Part C. A link by itself does not set a store cookie while you are still reading this website.

6. Consequences of disabling cookies on this website

If you block all cookies on this website, public pages will still load for reading in most browser configurations, but the consent block may appear repeatedly because your choice cannot be saved, contact forms may refuse to submit because their security token cannot be maintained, and any restricted area will not keep you signed in between pages. If you block only optional cookies through the consent block, reading, browsing and enquiring remain available, and the only loss is remembered preferences and our ability to count your visit in aggregate statistics.

7. Browser control steps

The steps below are the fullest browser guidance in this policy and they apply in the same way to our other websites, with the site address changed to the property you are managing. Menu labels change between browser versions, so treat the wording as a guide to the correct settings area rather than as a promise about the exact label on your screen.

• Google Chrome: open Settings, then Privacy and security, then Third party cookies. From there you can allow or block third party cookies, block all cookies, see the cookies stored for this website, and remove them individually or together. The Delete browsing data control clears cookies across sites for a chosen time range.
• Mozilla Firefox: open Settings, then Privacy and Security. Enhanced Tracking Protection offers Standard, Strict and Custom levels. The Cookies and Site Data area lets you clear data for all sites or manage exceptions and stored data site by site.
• Apple Safari on macOS: open Safari Settings, then Privacy. You can review website data, remove data for this website alone, and choose to block all cookies. Blocking all cookies in Safari will affect sign in and form behaviour as described in this part.
• Apple Safari on iPhone and iPad: open the device Settings app, then Safari, then the Privacy and Security options. Clear History and Website Data removes stored website data, and the advanced website data view allows removal for an individual site where your version provides it.
• Microsoft Edge: open Settings, then Cookies and site permissions, then Manage and delete cookies and site data. You can block third party cookies, inspect the cookies stored under this website, remove them, and set the browser to clear chosen data when it closes.

After clearing cookies for this website, reload the page. The consent block should be presented again, which confirms that the previous flag has gone. You can then make a fresh choice, including a choice to reject all optional cookies, and that fresh choice will be recorded for a further 12 months unless you clear it again sooner.

Part C: bizsensei.store

Applies to: bizsensei.store, the BizSensei Digital store, billing and checkout website

1. What this property is

bizsensei.store is the single home of commerce in this ecosystem. It is where products and plans are bought, where billing and checkout happen, where customer accounts for purchases are maintained, and where licences connected with a purchase are issued and managed. Because money, accounts and licences meet on this property, its strictly necessary cookie use is heavier than the showcase website, and its checkout depends on a third party payment provider in a way the other websites do not.

2. Cookies and storage the store sets

3. Razorpay checkout cookies and payment storage

Payment on the store is handled through Razorpay. When you start a payment, the Razorpay checkout is loaded and Razorpay may set cookies and use comparable storage that are necessary to process the payment securely, maintain the payment session, detect fraud and prevent abuse. Payment pages may also involve gateway fraud prevention storage operated for the payment flow, for the same security reasons. These items are strictly necessary for the payment you requested. They are not optional analytics, they are not set because you agreed to marketing, and there is no marketing use of the store checkout at all.

The practical consequence is direct: if you block third party cookies completely, or block the payment provider's storage, the payment will usually fail or the checkout will not load correctly. That is not a penalty imposed by us. It is the payment system refusing to proceed without the security state it needs. If a payment fails for this reason, no charge should be treated as completed unless the provider confirms it, and you should check any confirmation message or write to us at info@bizsensei.co.in before trying repeatedly, so that duplicate attempts can be avoided and checked properly.

Razorpay's cookies are governed by Razorpay's own privacy and cookie documentation, not by this policy. We describe their role here so that the checkout is not a surprise, but we do not control their internal retention, their fraud models or their own sub providers. Card numbers and comparable payment credentials are entered into the payment flow provided for that purpose. They are not stored in a BizSensei Digital cookie, and you should never send card details to us by email or through a contact form.

4. Embedded content on the store

The store is primarily transactional, so embedded third party content is limited. Where a help page, a product explanation or a billing guide on the store embeds a video or other external content, the same rule as the blog applies: the embed is loaded in a privacy conscious way where the provider supports it, and the provider's cookies are generally set only when you interact with the content, for example by pressing play. Merely reading the surrounding store page should not be treated as agreement to the embed provider's optional cookies.

5. Accounts, licences and the consent record at checkout

Before the store collects checkout information, the agreement block described in Part A is presented with the documents that apply to the purchase. The consent flag on your device remembers the choice for 12 months, and the server side consent record for the transaction logs the documents and versions accepted, the time, and the technical details described in Part A. That record is attached to the order history because a dispute about what was agreed at purchase cannot be resolved years later from a browser cookie alone. Deleting your browser cookies after a purchase therefore does not delete the order, the licence or the consent record connected with that purchase.

6. Consequences of disabling cookies on the store

• Account sign in fails: without the session cookie, the store cannot keep you signed in, and account and licence pages will return you to the sign in screen.
• Baskets are lost: without the cart token, items selected in one page view cannot reliably be carried to checkout, and a basket may empty when you move between pages.
• Forms fail security checks: without the CSRF protection working as designed, checkout and account forms may be rejected rather than processed with reduced security.
• Payments fail: without the payment provider's necessary storage, the Razorpay checkout may not load, may not complete its fraud checks, or may abandon the payment attempt.
• The consent block returns: without the consent flag, the store must ask again, including in the middle of a return visit where you expected to proceed directly to your account.

If you want the privacy benefit of blocking optional cookies without breaking a purchase, use the consent block to reject optional cookies and leave strictly necessary cookies enabled in your browser for this domain. That combination completes purchases normally while keeping analytics off unless you separately consent to it.

7. Abandoned baskets and reminders

A cart token existing on your device does not by itself authorise marketing messages. Any basket reminder or purchase related communication, where offered, follows the account and communication choices described in the Privacy Policy and the terms of the purchase, not the mere presence of a cookie. Clearing the cart token ends the browser side memory of an unsigned basket. It does not cancel an order that was already placed and confirmed, which must be dealt with under the refund and purchase terms that apply to that order.

Part D: bizsensei.agency

Applies to: bizsensei.agency, the BizSensei Digital services and portfolio website

1. What this property is

bizsensei.agency presents our services work: performance marketing, web development, search optimisation, retention work and content and influencer related services, together with portfolio examples and case material drawn from real client work. It is an enquiry and credibility property for prospective service clients. It does not operate the product checkout, which belongs to the store in Part C, and it does not run client campaigns from inside its own cookies. Advertising that we manage for clients runs on the advertising platforms concerned, under those platforms and the client engagement terms, and is not the same thing as cookies set by visiting this website.

2. Cookies this website sets

3. Portfolio previews and external project links

Portfolio entries on this website may show an automatic preview image of a project's front page, obtained through an image preview service, with the project name or initials as a fallback where no preview is available. Viewing a portfolio tile is browsing our website. It does not make you a visitor of the client project for cookie purposes, and the client project's own cookies are set only if you follow the link and visit that project under its own policies. Where an uploaded portfolio image supplied through our administration replaces an automatic preview, no preview service request is needed for that image, and the position is correspondingly simpler.

4. No prices and no advertising cookies on this website

Service pricing on this website is handled by enquiry and a fixed itemised quotation after a discovery discussion, rather than by published price cookies or personalised price tracking. Consistently with the general position in Part A, this website sets no marketing cookies, runs no behavioural advertising of its own, and does not place advertising pixels for the purpose of building a remarketing audience from agency website visitors. If a future campaign ever required such a tool, it would be a material change requiring an updated policy and fresh consent before the tool was activated for visitors who had not agreed to it.

5. Enquiries and the consent block on this website

An enquiry on this website is preceded by the agreement block described in Part A wherever information is collected. The consent flag remembers your cookie position on this domain separately from the showcase website and the store, even though the wording of the choice is the same. That separation is intentional. A prospective client who rejected optional cookies while reading product pages should not find that an unrelated acceptance on the agency website silently changed the earlier property's setting, and the reverse is equally true.

6. Consequences of disabling cookies on this website

Blocking all cookies on this website leaves the service descriptions and portfolio material readable, but enquiry forms may fail their security validation, the consent block may reappear on each new page or visit, and any remembered portfolio filter or display choice will be forgotten immediately. Blocking only analytics through the consent block has no effect that you will see while browsing. It simply means your visit is not counted in the aggregate statistics we use to judge which service explanations need improvement.

Part E: blog.bizsensei.co.in

Applies to: blog.bizsensei.co.in, the BizSensei Digital blog and content hub

1. What this property is

blog.bizsensei.co.in is the single content hub for BizSensei Digital. Articles, guides, product explanations and longer educational material are published here rather than being scattered across the other properties. Reading a blog is a low transaction activity: there is no basket, no restaurant operation and no payment taking place in an article. The cookie position reflects that simplicity, with one important exception, namely embedded third party content inside articles, which is dealt with in Clause 4 of this part.

2. Cookies the blog sets

The blog does not inherit the consent flag of the main showcase website merely because it sits on a subdomain of the same domain family. Browser cookie rules and our own configuration treat the blog's choice as its own record in the ordinary case, so you may be asked on the blog even if you already answered on the main website. We recognise that this is a small inconvenience, and we prefer it to the alternative of silently spreading a choice across properties you may experience as different places.

3. Newsletter and subscription forms on the blog

Where an article or a blog page offers a newsletter or an update subscription, the form is protected by the session and CSRF items in the table above, and the agreement block in Part A applies before your details are taken. Subscribing is a separate act from accepting cookies. Ticking the agreement for a subscription does not switch on analytics, and accepting analytics does not subscribe you to anything. The two choices are kept apart on purpose, because bundled consent is not informed consent.

4. Embedded videos and third party content in articles

Articles may embed videos, posts or other content from third party providers to illustrate a point that text alone would explain badly. An embed is a small piece of another service living inside our page, and the provider of that service may want to set its own cookies, for purposes such as remembering playback position, measuring views on its platform, or, on some platforms, advertising related measurement governed by that platform's policies.

Where the provider supports a privacy enhanced or interaction gated mode, we use it. In that mode the embed is presented without loading the provider's optional cookies at page load, and those cookies are generally set only when you interact with the content, most obviously by pressing play or by opening the content on the provider's own service. If a particular provider does not support such a mode for a particular embed type, we either choose a different presentation, such as a linked thumbnail prepared without the provider's tracking, or we accept that the embed should not be used in that article. Reading the text around an embed never requires you to play it.

Once you interact with an embed, the provider's own cookie and privacy policies govern what it sets and how long it keeps the resulting data. We do not receive the contents of the provider's cookies, we cannot delete them from inside the blog, and you must manage them through your browser controls or the provider's own settings. Blocking third party cookies in your browser will usually prevent embedded players from working fully, and the article text remains available in that case even if the player does not.

5. Comments and reader interaction

Where comments or reactions are enabled on an article, the strictly necessary session items support the submission and moderation flow and help resist spam and abusive automation. We do not use a comment interaction to enrol a reader in advertising measurement. If a third party commenting service is ever introduced, it will be named in this part before it is activated for readers, its category will be stated, and any optional element of it will be subject to consent.

6. Consequences of disabling cookies on the blog

A reader who blocks all cookies on the blog can still read published article text in the ordinary case. What is lost is the memory of the consent choice, any reading preference, the ability to complete a protected subscription or comment form reliably, the functioning of embedded players that need third party storage, and, where analytics was the only item refused, nothing visible at all. The blog is deliberately readable without an account, and no article is placed behind a cookie wall that requires acceptance of optional cookies as the price of reading.

Part F: BizSensei OMS: portal, apps and marketplace

Applies to: BizSensei OMS, including the oms.bizsensei.co.in portal, the OMS, Food and Rider native apps, and customer ordering and marketplace pages

1. What this part covers and why it is longer

BizSensei OMS is our restaurant management software. Unlike the reading and enquiry properties in the earlier parts, the OMS is a working system used during service: taking orders at a point of sale, sending orders to a kitchen display, managing tables and branches, handling delivery, and letting customers order from a restaurant. It reaches the user in three forms: a hosted web portal used in a browser, native applications for restaurant staff, customers and delivery riders, and customer facing ordering and marketplace pages. Each form stores information differently, so this part deals with browser cookies, app storage and ordering sessions separately and in detail.

2. Cookies in the OMS web portal

The staff dashboard inside the OMS does not set analytics cookies or marketing cookies. A working till or kitchen screen is not a place for visit measurement pixels, and we do not ask a cashier to make advertising choices in order to take an order. Aggregated, non identifying operational statistics may be processed on the server side to keep the service reliable, to plan capacity and to investigate errors, as described in the Privacy Policy. That server side processing is not a cookie and it is not a substitute analytics system for the dashboard.

3. Shifts, roles and shared devices in restaurants

Restaurant devices are often shared. A tablet may be used by a manager in the morning and by a cashier in the evening, and a kitchen display may stay signed in for an entire service. The session cookie is what connects the actions taken on that screen to the role that was signed in. For that reason, remember me should be used only on a device that stays under the restaurant's control, staff should log out at the end of a shift where the device passes to another person or leaves the premises, and restaurant admins should treat a lost device as a security event and ask for sessions to be revoked. Clearing the browser cookies on a shared portal device signs that device out and removes its remembered preferences, which is the correct result when a device is being reassigned.

4. Customer ordering and marketplace pages

Customer facing ordering pages, including pages reached from a QR code at a table and the marketplace pages where a customer chooses a restaurant and builds an order, use a short lived ordering session. That session holds the selected outlet, the items being ordered, table or delivery details entered for that order, and the choices needed to send the order to the correct kitchen. It is strictly necessary for the order you are placing. No marketing cookies are set on customer ordering pages, and building an order does not enrol the customer in advertising measurement.

If a customer blocks cookies on an ordering page, the menu may still display, but the order cannot reliably be carried from selection to confirmation, and the customer may find the basket emptying or the chosen outlet resetting. That is a technical limit of a stateless web page trying to remember an order without any storage, not a punishment for refusing optional cookies. No optional cookies are needed to order. Only the ordering session itself is needed, and it ends with the session.

5. Native apps: the central difference

The OMS app, the Food ordering app and the Rider delivery app are full native applications. They are not websites wrapped in a frame, and they do not primarily use browser cookies. Instead they use the storage mechanisms of the phone: local application storage for preferences and working data, secure token storage for sign in credentials, and a device identifier for the installed app. When older guidance or a generic device prompt calls all of this cookies, the substance is what matters, and the substance is set out in this clause and the clauses that follow so that app users are not left guessing from a website oriented policy.

Inside an app, a webview may be used for a limited screen, such as a help page, a legal document or a payment or map related view provided for that purpose. Where a webview is used, cookies inside that webview are confined to that view and its purpose, and they follow the rules for the property being displayed. The existence of a webview for a document does not turn the whole app into a browser, and the main sign in, preference and queue storage of the app remains the app storage described below.

6. What the native apps store, item by item

7. Why the apps store each kind of information

Sign in persistence is the first reason. Restaurant staff, customers and riders open their apps many times a day, often with wet hands, gloves, helmets or a queue waiting. Requiring a full login on every launch would make the apps unusable and would encourage unsafe workarounds such as passwords written on paper near a till. The token solves that problem without storing the password itself. If the token expires, is revoked, or is removed, the app returns to a sign in screen, which is the visible sign that the stored credential is gone.

Branch and device preferences are the second reason. A multi branch restaurant cannot afford for a device to open in the wrong branch during service, and a rider cannot afford for the app to forget which delivery is active when the screen wakes. Preferences and task state stored on the device make the app resume where the work actually is. Offline order queues are the third reason. Connectivity inside restaurants, basements, lifts and delivery routes is imperfect. An order taken during a gap must survive on the device until it can be delivered to the portal, and a queue that vanished when an app closed would lose real orders for real diners. The queue is working storage for a transaction you asked the app to complete, not a tracking mechanism.

8. Permissions are not cookies

Phone permissions, such as location for a rider delivery or for finding a nearby outlet, notifications for order and delivery updates, and camera access where a feature such as a code scan is offered, are controlled by the operating system, not by this cookie policy and not by a consent banner. Granting or denying a permission in your device settings does not change your cookie choices, and changing a cookie choice does not grant a device permission. We mention the distinction here because the controls sit near each other in device settings and are easily confused. Each permission should be judged on its own feature: if you deny location to a rider app, deliveries that depend on location cannot be performed correctly from that device, whatever your cookie position may be.

9. How to clear app storage: in app, Android and iOS

• Inside any of the apps: use the app settings or profile area and choose logout to end the signed in session and remove the active token from that device. Where the app offers a clear local data or reset option in its settings, using it removes preferences and queued local state that has already been synced. Do not clear an OMS device that holds unsynced offline orders until those orders have synced, or the queued orders may be lost.
• Android app storage: open the device Settings app, then Apps, then the app concerned, then Storage and cache. Clear cache removes temporary files. Clear storage or clear data removes the app's local record more completely, including sign in state and preferences, and the app will behave like a fresh install at the next launch.
• Android permissions: in the same app information area, open Permissions to review and change location, notification, camera and other permissions for that app alone, without affecting other apps.
• iOS app settings: open the device Settings app and scroll to the app concerned to review the permissions Apple exposes for it. iOS does not offer a general clear storage button for most apps. Logging out inside the app removes the active account state, and deleting the app removes its local storage from that device.
• Uninstall on either platform: uninstalling the OMS, Food or Rider app removes its local tokens, preferences, queues that remain on the device and device identifier record held inside the app. Uninstalling does not delete the server side account, order history or consent record, which are governed by the Privacy Policy and the applicable service terms.

10. Consent storage in the apps and on a new phone

In the apps, consent and agreement state is held as a local record in the app, supported by the server side consent record where an account action is involved, exactly as described in Part A. The local record is what lets the app open directly into work without presenting the full agreement block on every launch. Move to a new phone, reinstall after clearing storage, or sign in on a colleague's device, and the local record is not there: the app will present the required agreement and sign in steps again for that installation. Your server side account and earlier consent records are not erased by that repetition. The new presentation exists because the new device has no local memory to rely on.

11. Consequences of clearing or blocking storage in OMS contexts

• Portal session removed: the staff member is signed out immediately and must sign in again before taking, viewing or settling orders.
• Remember me removed: the trusted device convenience ends, which is the right outcome for a lost, sold or reassigned device.
• Preferences removed: branch, language and kitchen display choices return to defaults and must be selected again for that screen, which should be checked before service begins.
• App storage cleared: the app signs the user out, forgets device preferences, and loses any local state that had not yet synced to the portal.
• Ordering session blocked: a customer order cannot reliably be built or confirmed on the ordering pages, for the reasons given in Clause 4 of this part.
• Rider state cleared during a delivery: assignment and status may need to be reloaded from the portal, and the restaurant or support should be told if a delivery in progress is affected.

12. Restaurant customers, restaurant staff and responsibility

The OMS is provided to restaurants, and a restaurant's own staff and customers encounter storage set in the restaurant's service flow. BizSensei Digital remains responsible for the OMS software storage described in this part. A restaurant that adds its own separate tools, links or embeds to its own pages outside the OMS is responsible for those additions under its own policies. If you are a diner with a question about an order, the restaurant is usually the fastest route for the order itself, while questions about OMS cookies and app storage under this policy can always be sent to us directly at info@bizsensei.co.in.

Part G: qiaomed.space

Applies to: qiaomed.space, the Qiaomed product website and service

1. What this property is and its current stage

qiaomed.space is the home of Qiaomed, our healthcare related product. It is in a pre launch stage at the date of this version, which means that public features, account features and any appointment, enquiry or care related workflows are limited to what is expressly opened on that property from time to time. The cookie position in this part is written for that reality. It describes the storage the property uses for the pages and flows that exist, and it sets the rules that any later feature must follow before it is opened: a new optional purpose needs an updated entry in this part and fresh consent before it is switched on.

2. Cookies this property sets

3. A stricter approach because the subject is health

Because Qiaomed concerns health, we apply a deliberately stricter approach to storage on this property. No marketing cookies are set, in line with the ecosystem wide position in Part A, and that position is especially firm here: a visit to a health related page must never become the basis for advertising measurement elsewhere. No cookie on this property is used to infer a medical condition for promotional purposes. Information you type into a form on this property should be limited to what the form asks for, and sensitive health details should not be sent through a general enquiry or cookie related contact route at all.

Analytics, where enabled on the pre launch pages, is consent based and aggregate, as elsewhere in this policy. If you reject it, the information pages remain available. We do not use analytics storage on this property to build a health profile of an identifiable visitor, and we do not combine a consent flag or an analytics identifier from this property with an OMS, store or blog record to create a combined picture of a person across unrelated parts of their life. The properties are kept separate in their storage, and that separation is a design choice, not an accident.

4. Future features and fresh consent

A pre launch product changes by adding features, and each addition is a moment where cookie discipline can either be maintained or quietly lost. Our rule for this property is therefore stated in advance. Any future feature that needs a new category of storage, a new third party provider, or storage on a device for a care related workflow must be described in this part before or at the time it is launched, with its purpose, duration, provider and category. Where consent is required, the consent block on this property will present the new position and ask again. Silence in an old version of this policy is not permission for a new feature to set storage first and explain later.

5. Consequences of disabling cookies on this property

Blocking all cookies on qiaomed.space leaves published pre launch information readable in the ordinary case, but any form may fail its security checks, the consent block may return on each visit because the choice cannot be stored, and any future signed in feature would be unable to keep a session. Blocking only optional cookies through the consent block removes analytics and any remembered display preference, and nothing else that a reader needs. Given the subject matter of this property, we regard that low cost refusal route as an important part of the design, not as a grudging concession.

6. Contact about this property

Questions about cookies on qiaomed.space go to the same contact route as the rest of the ecosystem, info@bizsensei.co.in and +91 93726 65745, and they are handled under the grievance and contact provisions in the closing part of this policy. A cookie query does not need any health information in it, and you should not include medical details in a message about website storage. If a future Qiaomed service provides a dedicated care or clinical contact channel, that channel will be identified on the property itself for matters that belong there, and it will not replace the grievance route for data and cookie concerns.

Closing provisions

1. Retention in full

Storage on your device lasts for the duration stated in the relevant table, or until you remove it sooner through the browser, device and app steps described in this policy. Records created on our side from the operation of cookies and consent, including consent records, security logs and aggregate analytics, are kept only while they serve the purpose that created them, the protection of accounts and services, the resolution of a dispute about what was agreed, or a legal, tax or accounting obligation. When a record is no longer needed for any of those purposes, it is deleted, anonymised into an aggregate that no longer identifies a person or a browser, or archived under restricted access where a legal obligation requires retention but active use is no longer justified.

2. Children in full

No optional cookie or app storage in this ecosystem is targeted at children, no child directed feature sets analytics storage for profiling, and no advertising storage exists that could be pointed at a child audience. Adults hold the accounts, make the consent choices and operate the workplace and purchasing tools described in this policy. Where a family uses a customer ordering service provided through a restaurant, the adult account holder should make the choices and supervise the use. A concern that a child's data has been provided without appropriate consent should be sent to info@bizsensei.co.in, where it will be reviewed promptly and handled under the Privacy Policy and applicable Indian law.

3. Changes to this policy in full

We may update this policy as the properties, providers and law develop. Every update changes the version line and the last updated date at the top of this page, and the updated text replaces the earlier text from the date shown. Routine clarifications, corrected names and added rows for routine strictly necessary security storage take effect on publication of the new version. A material change, meaning a new category of cookie, a first use of marketing storage, a new third party purpose that needs consent, or a weakening of a commitment in Part A, requires fresh consent before the changed optional storage is set for a visitor who has not agreed to the new position. Continued reading of a public page after a routine update is not treated as consent to a material change. Only the consent block can give that consent.

4. Browser differences and the limits of features

Browsers, devices and privacy tools differ, and they change without asking us. A feature that depends on storage may therefore behave differently in a strict privacy configuration, in a private window, in an older browser, or behind a network filter that strips cookies or scripts. We test the properties in current mainstream browsers and we design refusal to be safe, but we do not warrant that every cookie dependent feature will work identically in every browser, version, device and configuration. That practical statement is not an exclusion of your rights. It is an honest description of how the web behaves when storage is blocked or altered outside our control.

Nothing in this Cookie Policy limits, excludes or waives any right or protection available to you under the Digital Personal Data Protection Act, 2023, the Consumer Protection Act, 2019, or any other applicable law of India. If any statement in this policy is read as attempting such a limitation, it is to be read down or, where it cannot be read down, treated as severed, so that your statutory rights remain fully intact.

5. Contact and grievance route

For any question about this policy, about a cookie or storage item on any property, about withdrawing consent, or about exercising a right connected with cookie data, contact BizSensei Digital at info@bizsensei.co.in or by phone at +91 93726 65745. Please name the property concerned, the browser or app involved, and the choice or item your question is about, so that the query can be routed correctly the first time. You do not need to include passwords, payment details or health information in a cookie query, and you should never send them by email for this purpose.

Cookie and privacy complaints are handled through our Grievance Officer function, which can be reached at the same email address, info@bizsensei.co.in, marked for the Grievance Officer in the subject line. A grievance will be acknowledged within 48 hours of receipt and resolved within one month of receipt, in line with the grievance timelines described in the Privacy Policy. If a grievance needs information that only you hold, such as the approximate date of the consent choice concerned, we will ask for that information during the process and the response will explain what was found and what was changed as a result.

6. Governing framework

This policy is framed under the laws of India, including the Digital Personal Data Protection Act, 2023 and its consent requirements for processing that is not strictly necessary. It should be read with the Privacy Policy for the full statement of personal data practices and data principal rights, and with the purchase, subscription or service terms that govern any transaction you enter into. Headings and part labels in this policy are for navigation. They do not change the meaning of the clauses under them, and a reference to a property in one part does not transfer that property's storage practices to a different property described elsewhere in this document.

End of Cookie Policy, Version 2026-10-23, Last updated: 23 October 2026. BizSensei Digital, contact info@bizsensei.co.in, +91 93726 65745.