Read the sections that matter to you
Each section stays collapsed until you choose to open it.
1. Essential cookiesOpen to read the full section.
Essential HttpOnly order cookies support the protected browser session for up to 30 days, subject to server-side expiry and revocation. Essential Razorpay checkout mechanisms may be used during payment. A signed file link is short-lived; neither a cookie nor a phone number overrides an unpaid, expired or revoked entitlement.
2. First-party analyticsOpen to read the full section.
The website records limited events such as page views, CTA clicks, form starts, order submissions, checkout opens or errors, and requests for download links. Browser events describe an observed step and are not proof of payment or a file being saved. Successful payment records come from server verification. A download-link event means a link was issued, not that the file reached the device. Additional journey details are limited to an event identifier, the page surface, a controlled error category and, where relevant, the volume number. They must not include entered phone numbers, email, UTR, order references, payment identifiers, private tokens or signed URLs.
The first-party anonymous visitor cookie lasts up to 90 days and the session cookie up to 30 minutes. Browser privacy signals can suppress optional analytics. These identifiers never unlock an order or PDF and are not themselves sent as Meta matching identifiers.
3. Optional Meta sharingOpen to read the full section.
When enabled and separately allowed, the Meta Pixel measures public English homepage views, product views and checkout opens. It is not installed on admin, protected order or legal pages. Automatic event configuration is disabled in this integration and no phone or email is passed to browser matching. Public URLs that could expose private information are not tracked. Advertising cookies such as _fbp and _fbc can identify a browser or advertising click.
Only the server sends the Purchase event, after it verifies a captured payment for a supported order created with the optional permission. It includes the actual amount and INR currency, capture time, an opaque event identifier, a SHA-256 hash of the normalised mobile number, browser user-agent and available advertising identifiers. Hashing still allows account matching and does not make the information anonymous. Failed, unverified, held, refunded or already-marked test orders are not newly sent as live purchases. Old purchases without this permission are not reconstructed or exported.
Repeated payment checks and delivery retries reuse the same purchase-event identifier. A browser callback, Pay button click or download click does not send a Purchase event. Pending event delivery can be retried within a limited window; Meta acceptance and ad attribution are different outcomes. Changing a test label or refund after Meta has already received an event does not retract it.
4. Your choice and browser signalsOpen to read the full section.
The optional choice is independent of purchase acceptance and is remembered in an HTTP-only preference cookie for up to 90 days. Select Continue without, or later Stop optional sharing under Privacy choices, to decline. Declining leaves payment, customer support and protected downloads available. Do Not Track and Global Privacy Control override optional tracking permission.
On a confirmed change to decline, browser events stop, website advertising cookies are cleared where the browser permits it and unsent server events are cancelled. A request already in flight or accepted by Meta cannot be withdrawn by the switch. If the change cannot reach the server, the page pauses browser sharing and asks you to retry; do not treat an error as confirmation that queued server sharing has been updated.
The website does not load the Pixel in its test measurement mode. Server test events are marked for Meta’s Test Events tool. Optional ad sharing can be paused by the operator without affecting purchase or download access.