Cookie policy

Last updated 2026-11-01

No tracking cookies

NamePump does not use analytics, advertising, or any other tracking cookies. There is no consent banner here because there is nothing to consent to — the desk sets no marketing or measurement cookies at all.

What about functional cookies?

The marketing pages — the appraisal, the generator, the bulk analysis — are static and set no cookies at all. They compute in the browser and keep no state beyond the per-tab query described below.

The workspace is the exception. Signing in (/login) sets one session cookie so the desk can tell one signed-in account from another. It carries a random identifier and nothing else, and only a hash of it is stored on the server. It isHttpOnly, SameSite=Lax,Secure in production, and lasts up to 30 days; signing out revokes it immediately. It is strictly functional: it identifies you to us, not to anyone else. It is never shared, and it is not used to build a profile or measure behaviour.

Third-party cookies

The desk does not embed third-party trackers, social widgets, fonts, or ad networks, so no third-party cookies are set by this site. The social links in the footer are ordinary outbound links; following them takes you away from the desk and onto those platforms, whose own cookie policies then apply.

Local browser state

The appraisal and the generator compute in memory and store nothing. Outside the signed-in workspace the desk sets no cookies; it keeps the last typed query in per-tab session storage so a backspace can return to it, and that entry disappears when the tab closes. Within the workspace, the session cookie above is the only browser state the desk relies on.

What you don't need to do

There are no analytics, advertising, or third-party cookies, so there is no consent banner, no opt-out panel, and no categories to manage — there is nothing to consent to beyond the one session cookie that signing in depends on. You can block cookies for this domain in your browser; the public pages will keep working exactly the same way, and only the workspace will be unable to keep you signed in.

Changes

If the desk ever adds analytics or a preferences mechanism, this policy will be updated first and the date above will change.

Questions

Ask on the project on GitLab.