Cookie policy

Cookies, and the other ways a site can store something on your device or read something back off it: local storage, session storage, pixels, fingerprinting scripts and anything else that does the same job under a different name. The UK’s Privacy and Electronic Communications Regulations and the EU’s ePrivacy Directive treat all of them the same way, and so does this page.

It covers this website and the RampFunnels scorecard. What happens to the data itself, once it exists, is in the privacy policy.

Strictly necessary

None. There is no login, no basket, no consent record and no session to keep, so nothing has to be stored to make the site work.

Preferences

None. The site has one theme and one language, so there is no choice to remember.

Analytics and performance

None. No analytics product, no tag manager and no performance monitor is installed.

Marketing and advertising

None. No advertising pixel, no remarketing tag and no conversion tracker is installed.

Local and session storage

Neither is used. The site stores nothing in your browser between pages or between visits.

So the count is zero. Not zero after you decline something, and not zero except for the ones everybody sets: zero.

Checked on 20 September 2026 against the source the site is built from:

1. Every file the site is built from was searched for the ways a cookie gets set or read: document.cookie, the Set-Cookie header, localStorage, sessionStorage and IndexedDB. Nothing matched.
2. The dependency list was read. There is no analytics package, no tag manager, no consent platform and no advertising SDK in it.
3. There is no middleware, so no cookie is attached to a response on its way to you.
4. Every external address in the source was listed. The list is empty, so no page loads a script, a stylesheet, an image or a font from another company.
5. The typefaces are downloaded once when the site is built and served from the site itself, so your browser never requests them from a font service.

You can confirm the result from your side in about ten seconds. Open the developer tools in your browser, go to the storage or application panel, and look at the cookie list for this site. It is empty.

Consent under the ePrivacy rules is consent to something specific. With nothing being set, a banner would be asking you to agree to an empty list, which teaches you to click through the next one without reading it.

A banner arrives when there is something behind it, and the thing behind it will be named on this page first. Until then the honest interface is no interface.

Nothing here needs controlling yet, but the controls are worth knowing about for every other site you use. Every major browser lets you see the cookies a site has set, delete them, block new ones, and block third-party ones separately. The settings are under privacy or under site data, depending on the browser.

Blocking cookies outright will break sites that rely on them for logging in. It will not break this one.

The inventory is re-checked, by the method in clause 3, whenever anything is added to the site that could set something, and always before a release that adds a third-party script. The date on the check moves when the check is redone, not when the page is edited.

Questions about this page, or about anything you find in your browser that this page does not list, go to nooruddin@sellmysaas.io. A cookie on this site that is not in the inventory above is a mistake, and it is one worth telling us about.