Cookie & Local Storage Policy

Last updated: 3 July 2026

This policy explains exactly what Code In Plain (operated by Sifarhub) stores in your browser and why. The short version: we use no advertising cookies, no analytics cookies, and no tracking of any kind. Everything we store is either strictly necessary to run the Service or a preference you chose yourself.

Because none of our storage is used for advertising, analytics, or cross-site tracking, it falls under the "strictly necessary" and "user-preference" exemptions of European ePrivacy rules — which is why we show you a simple notice rather than a consent pop-up. If we ever add analytics or marketing tools, we will update this policy and ask for your consent first where the law requires it.

1. What we store, item by item

Name	Type	Purpose	Duration
`sb-*-auth-token`	localStorage (first-party)	Keeps you signed in between visits (your Supabase session). Strictly necessary for accounts.	Until you sign out
`theme`	localStorage (first-party)	Remembers the colour theme you picked.	Until you clear it
`codeFontSize`	localStorage (first-party)	Remembers your chosen text size.	Until you clear it
`period`	localStorage (first-party)	Remembers your billing-period choice (monthly/yearly) on the pricing page.	Until you clear it
`cookie-notice-ack`	localStorage (first-party)	Remembers that you dismissed our storage notice so we don't show it again.	Until you clear it
Repository tree	sessionStorage (first-party)	Holds the file tree of the repository you are browsing so navigation is instant.	Cleared when the tab closes
`visited`	sessionStorage (first-party)	A yes/no flag so each browsing session is counted once in our anonymous, aggregate visit counter. No identifier, IP, or personal data is stored with it.	Cleared when the tab closes
`gh-token`	sessionStorage (first-party)	Your own GitHub personal access token, if you choose to add one to read a private repository. Stored only in your browser and sent with your requests; we never store it on our servers.	Cleared when the tab closes
Payment cookies	Cookies (third-party: Stripe / Razorpay)	Set only during a checkout you start, by our payment processors, for payment session handling and fraud prevention. Governed by their own policies.	Set by the processor

2. What we do not use

No advertising or marketing cookies.
No analytics or measurement cookies (no Google Analytics, no pixels, no heatmaps).
No cross-site tracking or fingerprinting.
No selling or sharing of personal data derived from storage.

3. How to clear or block storage

You can clear all of the above at any time from your browser's site-data settings (usually under Privacy → Cookies and site data → codeinplain.com). Note that clearing the authentication token signs you out, and blocking storage entirely will prevent sign-in from working.

4. Payment processor cookies

When you open a checkout, Stripe (international cards) or Razorpay (India) may set their own cookies to complete and secure the payment. These are necessary for the transaction you requested and are described in Stripe's Privacy Policy and Razorpay's Privacy Policy.

5. Changes to this policy

If we introduce any storage that needs your consent (for example analytics), we will update this page and ask first where required. The "Last updated" date reflects the current version.

6. Contact

Questions? Email info@codeinplain.com or see our Contact page. Related: our Privacy Policy and Terms & Conditions.