Cookie policy
Which small files naseebbet.com writes to your device, what each one records, how long it survives, and the browser settings that let you refuse or delete it.
What we set and why
What cookies are
Cookies are small text files that a website writes to your device and reads back on your next request. Their work is unglamorous: carrying a handful of settings from one page load to the next, telling a returning reader apart from a first-time one, and giving publishers counts that describe traffic in aggregate, with no individual reader identified in them. Two categories matter for this policy. First-party files are written by the address showing in your browser bar; third-party files are written by an outside service embedded inside the page, which is how tracking follows a reader between unrelated websites. Everything set under the naseebbet.com name belongs to the first category, and that distinction is what the rest of this document turns on.
What we set, and why (first-party only)
| Cookie name | Type | Purpose | Retention |
|---|---|---|---|
| nb_session | Functional | Maintains site preferences (filter selection, sort order on rating tables) | Session + 30 days |
| nb_consent | Functional | Records cookie-consent acknowledgement | 12 months |
| nb_aff_ref | Functional | Records last-clicked affiliate link for attribution | 30 days |
What we deliberately never set
- Nothing belonging to an advertising network — not one Google Ads, Meta Pixel, DoubleClick, Outbrain or Taboola call is made from these templates, and no DSP or SSP integration exists anywhere in the page source
- No cross-site tracking — neither Facebook Pixel nor Google Analytics 4 is installed; measurement here runs on Plausible, which counts a visit without writing anything to your device
- Zero re-marketing pixels — nothing on the site builds an audience list, so our pages cannot reappear as an advert chasing you around other websites afterwards
- Nothing passed onward — no data-broker tag has ever been placed in the templates, and no reader record leaves our own systems for sale or exchange
Affiliate-tracking parameters (no cookies)
A click on a /go/{operator}/ link carries its tracking parameter inside the URL itself, which is how the operator recognises the visit as one that originated here. Nothing is written to your device by us at that moment, and the parameter disappears once the destination page has loaded. From the moment the redirect completes you are inside the operator’s systems: whatever they keep is kept in their name, under the notice they publish, and entirely beyond our reach. The boundary needs stating plainly — this policy describes naseebbet.com and it stops at the redirect.
Third-party services that may set their own cookies
- Cloudflare CDN — may write a short-lived security token such as __cf_bm, whose only job is to tell automated traffic from human traffic. It is strictly necessary for keeping the site reachable while under attack, carries no advertising identifier, and is never read for behavioural purposes.
- YouTube embeds (rare) — where a page carries an embedded video, the player runs in privacy-enhanced mode, so what YouTube stores is confined to playback state: no personalised advertising is served from it and no viewing profile is built out of the embed.
Browser controls at your disposal
Every mainstream browser exposes the same controls, and they apply to this site exactly as they apply to any other. The paths differ only in wording:
- Chrome: Settings → Privacy and security → Cookies and other site data
- Firefox: Settings → Privacy & Security → Cookies and Site Data
- Safari (iOS): Settings → Safari → Block All Cookies
- Edge: Settings → Cookies and site permissions → Cookies and site data
Blocking the functional files costs you convenience rather than access. Pages still load in full and nothing is withheld from a reader who refuses them; what changes is that a filter applied to a rating table and the sort order chosen alongside it reset on every visit and never carry over, and the consent acknowledgement is asked for again each time.
Cookie retention
Each functional file expires on the schedule recorded against its name: session plus 30 days for nb_session, 12 months for nb_consent, 30 days for nb_aff_ref. Session-scoped entries go the moment the browser window closes, without waiting for that clock to run down. Clearing the lot by hand costs nothing in access — every page stays readable, every table stays usable — and the only casualty is the set of preferences you had stored.
Updates to this policy
This policy is revised whenever a first-party or third-party service is added to the site or taken off it, and each revision carries its own effective date; the version bearing the latest date is the one in force. An older version lapses the moment its replacement goes live, and nothing already sitting on a reader’s device is re-characterised by a later text.
Contact
Anything here that needs clarifying goes to privacy [at] naseebbet [dot] com, and the same address handles a request to have stored preferences wiped at our end, which browser settings on their own cannot reach.