bigbaazi privacy notice — how we handle reader data.

Reader data on this site.

The reader is built as a static editorial site. We do not run advertising trackers, analytics scripts or third-party data-collection tools on the public pages. Standard server logs may record the requested URL, the response code and the user-agent string for the purpose of operating the site.

Platform data on the bigbaazi app.

When you use the official bigbaazi app, the platform's own privacy notice applies. That notice covers account data, KYC documents, transaction history and gameplay history. The platform is the data controller for that data; this reader has no access to it.

The platform's privacy notice is published on the customer-care page.

Cookies and local storage.

The reader does not set advertising cookies or tracking cookies. The masthead, the mobile drawer and the FAQ accordion use minimal browser state for their core behaviour (open/closed). No third-party cookies are set by the reader.

Your rights.

You have the right to:

• Ask for a copy of any reader-related data we hold (we hold none beyond standard server logs).
• Ask for deletion of any reader-related data (deletion of server logs is automatic on log rotation).
• Contact the editorial desk with any privacy question or complaint.

Reading the privacy policy in plain language.

A privacy policy is a contract that governs how a platform handles the player's personal data. The policy is usually long, but the substance is in a small number of clauses. The clauses that matter are the data the platform collects, the purpose for which the data is collected, the third parties to which the data is shared, the retention period, the player's rights over the data, and the route for raising a privacy complaint. The rest of the policy is mostly housekeeping that the platform's compliance team is required to include.

The data the platform collects is the first thing to read. The categories typically include the account data (name, email, phone), the verification data (the documents submitted for KYC), the payment data (the payment method details the platform stores or tokenises), the device data (the IP address, the device fingerprint, the operating system), the session data (the logs of the player's activity on the platform), and the support data (the messages the player sends to customer care). The honest read is to verify that the categories the player expects the platform to collect are the only categories the platform does collect.

Purpose, third parties, and retention.

The purpose clause names the reason each category of data is collected. The reasons typically include account operation, fraud prevention, regulatory compliance, marketing (where consent is given), and product improvement. The honest read is to verify that the purposes the player expects are the only purposes the platform uses the data for. A platform that collects data for one stated purpose and uses it for another has a privacy problem that the policy itself surfaces.

The third-party clause names the parties the platform shares data with. The parties typically include the payment processor, the KYC vendor, the cloud hosting provider, the customer-care tool, the analytics provider, and (where the player has consented) the marketing partner. The honest read is to verify that the parties the player expects are the only parties the platform shares data with. A platform that shares data with an unexpected party — a data broker, a marketing network, an advertising partner — is a platform whose policy the player should re-read.

The retention clause names how long each category of data is kept after the account is closed. The honest read is to verify that the retention period is consistent with the legal requirement and the legitimate business need. A platform that retains data indefinitely after account closure is a platform that is retaining more data than the policy needs. A platform that retains data only for the legal minimum is a platform that is doing the right thing.

Rights, complaints, and the route for a real privacy issue.

The rights clause names the player's rights over the data. The rights typically include the right to access the data, the right to correct the data, the right to delete the data (where the legal minimum is met), the right to restrict the processing of the data, the right to object to the processing of the data, and the right to data portability. The honest read is to verify that the rights the player expects are the rights the policy names. A policy that does not name the right to delete is a policy that does not give the player the right the player expects.

The complaint clause names the route for raising a privacy issue. The route is typically the platform's privacy officer or data protection officer, with a contact email and a response window. The honest read is to verify that the route is a real email, the response window is a real window, and the escalation to the regulator is named. A platform that does not publish a privacy contact is a platform that does not have a real complaint route. The honest habit is to send the privacy query through the published route and to keep a dated record of the message, the reply, and the resolution.

Cookies, tracking, and the on-device footprint.

Most platforms use cookies and similar tracking technologies for session management, analytics, and (where the player has consented) advertising. The honest read is to verify that the cookie list is published, the purpose of each cookie is named, and the consent mechanism for non-essential cookies is a real consent mechanism — not a pre-ticked box, not a "by continuing to browse you agree" footer, and not a setting that is harder to disable than to enable. A platform that uses dark patterns in the cookie consent is a platform whose privacy practices the player should re-read.

The honest habit is to keep a short record of the privacy policy version the player accepted, the date the player accepted it, and the consent choices the player made on cookies and marketing. The record is the evidence base for any later dispute about what the player agreed to, and the re-read is the cheapest way to know whether the platform changed the policy without notice. The privacy policy is a contract; the contract is worth reading once, and worth re-reading on any material change.

Reading the data flows in plain language.

A privacy policy is a contract that governs how a platform handles the player's personal data. The data flows are the operations the platform performs on the data — collection, storage, processing, sharing, retention, deletion. The honest read is to verify that the data flows the player expects are the data flows the platform actually performs. The honest habit is to read the data flows on the day the account is created, and to re-read the data flows on the day the platform publishes a material change.

The data flows are typically described in the privacy policy under headings like "Data we collect," "How we use your data," "How we share your data," "How long we keep your data," and "Your rights." The honest read is to read each section, to confirm that the data flows the player expects are the data flows the platform describes, and to keep a dated record of the privacy policy version the player accepted. The record is the evidence base for any later dispute, and the re-read is the cheapest way to know whether the platform changed the flow without notice.

The lawful basis for processing — what it means for the player.

Most privacy policies name a lawful basis for processing the player's data. The lawful basis is the legal reason the platform is allowed to process the data — consent, contract, legal obligation, vital interests, public task, or legitimate interests. The honest read is to verify that the lawful basis the platform names is a lawful basis the player accepts, and to verify that the lawful basis is appropriate for the data flow the player is consenting to. The honest habit is to read the lawful basis clause before the first deposit, and to re-read the clause on the day the platform publishes a material change.

The lawful basis for processing is the difference between a privacy policy the player can accept and a privacy policy the player cannot accept. A platform that names consent as the lawful basis for marketing is a platform the player can opt out of. A platform that names legitimate interests as the lawful basis for everything is a platform the player needs to read more carefully. The honest read is to verify that the lawful basis is appropriate for each data flow, and to keep the verification in the player's own file.

International transfers — where the data actually goes.

Most platforms process some data outside India. The honest read is to verify that the international transfers the platform performs are the international transfers the player expects, and to verify that the international transfers are protected by the legal safeguards the player expects. The legal safeguards are typically the European Commission's standard contractual clauses, the UK International Data Transfer Agreement, or the player's own country's data protection law. The honest habit is to read the international transfers clause before the first deposit, and to re-read the clause on the day the platform publishes a material change.

The international transfers clause is the part of the privacy policy that names the countries the data goes to, the legal safeguards the platform uses, and the player's rights over the data once it is in the destination country. The honest read is to verify that the countries the player expects are the countries the platform names, and to verify that the safeguards the player expects are the safeguards the platform uses. The honest habit is to treat the international transfers clause as the floor for the privacy policy, and to re-read the clause on the day the platform publishes a material change.

Children's data — the boundary the player should know.

Most platforms publish a minimum age for the account. The minimum age is the platform's commitment to the children's data boundary. The honest read is to verify that the minimum age the platform publishes is a minimum age the player accepts, and to verify that the platform's children's data practices are the practices the player expects. The honest habit is to read the children's data clause before the first deposit, and to re-read the clause on the day the platform publishes a material change.

The children's data clause is the part of the privacy policy that names the minimum age for the account, the verification step the platform uses to confirm the age, and the platform's practices if the platform discovers that a child has created an account. The honest read is to verify that the verification step the platform uses is a verification step the player accepts, and to verify that the platform's practices are the practices the player expects. The honest habit is to treat the children's data clause as the boundary, and to re-read the clause on the day the platform publishes a material change.