Cookie Policy

There are no cookies on this site, so this page lists none. It explains what that means, what happens instead, and what the publisher commits to if it ever changes.

Effective date: 21 September 2026

What a cookie is

A cookie is a small text file that a website asks your browser to store and to send back with later requests, which is how a site recognises a returning visitor or keeps you signed in. Related technologies — localStorage, sessionStorage, IndexedDB and browser fingerprinting — achieve similar results by storing data in your browser or by identifying your device from its characteristics.

This site sets no cookies

agilebase.online sets no cookies of its own and permits no other party to set cookies through it. That is the complete position, and it is not a summary of a longer arrangement.

Specifically, there is no analytics cookie, no advertising or retargeting cookie, no conversion or tracking pixel, no session identifier, no preference cookie, no social media embed and no A/B testing tool. No third-party script of any kind runs on any page. This page lists no cookie names because there are none to list.

The site also uses no localStorage, no sessionStorage, no IndexedDB and no fingerprinting technique. The only JavaScript on the site is a single first-party file, served from this domain, which opens the mobile menu and highlights the current section in the contents list. You can read it at /assets/main.js; it stores nothing and sends nothing anywhere.

Consent banners exist so that a site can obtain permission before setting cookies that are not strictly necessary. This site sets none, so there is nothing to ask permission for. A banner here would tell you something untrue about what the site does, which is why one is not shown.

What happens instead

Two things occur when you read this site, and both are described in full in the privacy policy.

Server logs. The hosting provider records ordinary web server access logs — IP address, user agent, requested address, response code and timestamp — for availability, diagnostics and abuse prevention. These are logs, not cookies: nothing is stored on your device, and nothing follows you to another site.
Requests you initiate. If you follow a link to another website, your browser contacts that site, which applies its own cookie practices. That includes the paid link described on the affiliate disclosure page: attribution of a subscription to this site happens on the advertising network's own systems, after you have left, under that network's and the vendor's policies rather than this one.

No font, stylesheet, image or script is loaded from any other company's servers. Reading a page here makes requests to this domain and to nothing else.

Controlling cookies in your browser

Nothing here needs to be blocked, but browsers let you manage cookies for every site you visit, and the controls are worth knowing. In Chrome, Firefox, Safari and Edge, cookie settings are found under privacy or site settings, where you can block third-party cookies, block all cookies, clear what is already stored, or set exceptions per site. Each browser's own help documentation gives the current steps. Blocking cookies broadly can prevent other sites from working as intended, particularly sites you sign in to; it makes no difference to this one.

If this ever changes

The publisher's commitment is specific. If a cookie, a tracking script, an analytics service or an embedded third-party component is ever added to this site, this page will be rewritten to describe exactly what is set, by whom, for what purpose and for how long, and a working consent mechanism will be in place before anything is set on any reader's device. The privacy policy would be updated in the same change, and both pages would carry a new effective date.

Questions about any of this go to info@agilebase.online.