Cookie & Local Storage Policy

• We set no cookies for advertising, analytics, profiling, retargeting or cross-site tracking. There is no tag manager, no pixel, no session replay and no heat map on this site.
• We use the browser's local storage rather than cookies for nearly everything. Local storage is not attached to network requests, so the data physically cannot travel to a server the way a cookie does.
• Everything we store is first-party — written by bruteinfo.in, readable only by bruteinfo.in, in your browser.
• One value, your resolved light or dark theme, is read before the page paints so that you never see a flash of the wrong colour scheme.
• You can inspect, change or erase all of it yourself. Section 5 has the controls; section 7 explains the browser-level route.

The two are often confused, and the difference matters for your privacy.

A cookie is a small value that your browser attaches to every request it makes to the site that set it. Cookies travel over the network by default, which is what makes them useful for tracking.

Local storage is a key–value store inside your browser profile. Nothing is attached to a request; JavaScript running on the page has to read a value deliberately and send it deliberately. Brute Info reads these values to draw the interface and never transmits them.

Brute Info uses local storage for its account records, learning data, cart, orders and preferences. It sets no first-party cookies of its own. Where Firebase Authentication is enabled by us as the identity provider, Google's SDK may set its own storage entries in order to keep you signed in; those are described in section 6.

Strictly necessary

Without these the Platform cannot function: your sign-in session, your account record, your enrolments and orders. They cannot be switched off, because switching them off means being permanently signed out. No consent is required for this category under Indian law, and none is asked for.

Functional

Your learning record — lecture ticks, progress, notes, certificates and the cart. These make the product work as a course platform rather than a brochure. They exist only on your device.

Preferences

Theme, accent colour, density, text size, playback speed, autoplay, captions, reduced motion, high contrast, language, keyboard shortcuts, notification choices and profile visibility. All of them are yours to change, and all of them are erasable in one click below.

Analytics

Not used. There is no analytics key, no measurement identifier and no third-party analytics script on this site.

Advertising and social

Not used. The links to our social profiles in the footer are ordinary hyperlinks; no social widget, share button or embedded feed loads on any page, so no third-party social cookie is ever set.

This is the complete list. You can verify it yourself: open your browser's developer tools, go to Application → Local Storage → the Brute Info origin, and compare. The right-hand column is live and shows whether each key exists in this browser right now.

No key on this list contains a card number, UPI handle, bank account, CVV or OTP — none of those is ever collected, because the payment gateway is not connected. No key is transmitted to a Brute Info server, because the Platform runs without a backend.

These controls are live. Each one writes immediately to the bruteinfo:v1:settings key described above and takes effect across the whole site without a reload. If you are signed in they are saved against your account; if you are not, they are saved against a guest bucket on this device and adopted when you next sign in.

The full preference set — accent colour, density, text size, playback speed, captions, reduced motion, high contrast, weekly goal and language — lives on the Settings page. This panel exposes the ones that affect what we store and what we send you.

Loading a Brute Info page makes network requests to exactly three hosts. There is no fourth.

Google receives the IP address and user-agent of any request your browser makes for a font file — that is inherent in fetching a file from another host, and applies to every site that uses a font CDN. Google's handling of that data is governed by its own privacy policy.

We embed no third-party video player, no advertising script, no chat widget and no social media embed anywhere on the Platform. Videos are not streamed at all: opening a lecture runs a short timer and marks it viewed.

You do not need our permission to remove any of this. Every major browser lets you inspect and delete site data:

• Chrome and Edge — Settings → Privacy and security → Third-party cookies → See all site data and permissions, then search for the Brute Info origin.
• Firefox — Settings → Privacy & Security → Cookies and Site Data → Manage Data.
• Safari — Settings → Privacy → Manage Website Data.
• Any browser — open developer tools, go to the Application or Storage panel, expand Local Storage and delete individual bruteinfo:v1 keys.

Inside the product, Settings offers a reset for your preferences, a reset for your course progress and full account deletion. Those are the same operations, with a confirmation step and without a developer console.

Private or incognito windows discard everything when the window closes, so the Platform works there but forgets you completely afterwards.

We honour these signals by construction: there is no tracking to switch off. Sending a Do Not Track header or a Global Privacy Control signal to Brute Info changes nothing, because we do not build profiles, do not share personal data with advertisers and have nothing to sell.

We do honour the prefers-reduced-motion and prefers-color-scheme signals your browser sends, and the reduced-motion and high-contrast settings you can set yourself — those genuinely change how the site behaves.

Blocking local storage entirely does not lock you out — the site detects it and falls back to an in-memory store for the session — but it does degrade the product in ways you should expect:

• you are signed out the moment you close the tab, and cannot stay signed in;
• lecture ticks, course progress and notes are lost when the tab closes;
• your cart empties on every page load;
• order history and certificates cannot be kept;
• the site falls back to your system theme, and you will see a brief flash of the light theme before a dark-mode page paints.

Because the learning record has no server-side copy, storage that your browser evicts is gone for good. Section 4 of the Privacy Policy explains why, and what we plan to do about it.

If we add a key, change what a key holds or introduce a new third-party host, we update the table in section 4 and the “last updated” date at the top of this page. If we ever introduce a category that requires your consent, we will ask for it before setting anything, not afterwards.

Questions about this policy, or about anything we store, go to our grievance officer at privacy@bruteinfo.in, or to support@bruteinfo.in for day-to-day help.