Cookie and tracking notice

This notice lists the cookies and browser storage PageFox uses in two places: on websites that install the PageFox script, and on pagefox.co itself. Read it with our Privacy Policy and with the privacy notice of the website you are visiting. That website's owner decides whether PageFox runs and runs its own cookie banner.

These keep the service working and let repeat visits be linked. They hold a random ID, never a name or an email address.

• pagefox_visitor_id: a random visitor ID, kept in local storage and in a first-party cookie of the same name. Expires after 180 days without a visit.
• pagefox_visitor_id_last_seen: local storage. When the ID was last used, so it can expire on time.
• pagefox_config_*: session storage. The chat's settings for this website, cached for the visit.
• pagefox_session_started_at, pagefox_pages_viewed, pagefox_prompts_fired: session storage. Keep the chat from prompting more than twice a visit. Cleared when the tab closes.
• pagefox_time_leader: local storage. Lets only one open tab count time on page.
• pf_exit_capture: local storage. Remembers that a leaving visitor was already asked once.

• pagefox_conversation_id, pagefox_messages_active, pagefox_messages: session storage, falling back to local storage if session storage is blocked. Keep the conversation on screen as the visitor moves between pages.
• pf_id:*: session storage. Stops the same email from being sent twice when a visitor fills a form.

Some tracking waits for the visitor's consent. Without a consent signal, PageFox treats the answer as no.

• Scroll depth, form behaviour and return-visit prompts
• pagefox_returning: a first-party cookie for 7 days that marks a returning visitor

PageFox reads consent from:

• Cookiebot (statistics consent)
• Google Consent Mode v2 (analytics_storage)
• window.PageFox.consent or window.__pagefox_consent, set by the website owner
• the pagefox_consent cookie, read only; PageFox clears it and pagefox_returning when consent is withdrawn

When a browser sends a Global Privacy Control signal, PageFox records it on that visit and treats it as an opt-out of sale and sharing: no lookup of personal details is made for that visitor, now or later. You can also opt out on our opt-out page.

• The PageFox script itself, with the storage listed above
• Sign-in cookies (sb-*-auth-token) when you log in to the dashboard. They keep you signed in and are needed for the service.
• Two first-party cookies when we measure our own ad campaigns: __Host-pf_acquisition (30 days) and __Host-pf_acquisition_session (until the browser closes)
• On public marketing pages only: Microsoft Clarity, which may set its own cookies such as _clck and _clsk, and Vercel Web Analytics, which sets no cookie. Neither loads if your browser sends Global Privacy Control or Do Not Track, and neither runs on the dashboard.

You can block or clear cookies and site storage in your browser settings. Clearing them resets the visitor ID and any open chat. Turning on Global Privacy Control stops personal lookups. Questions: privacy@pagefox.co.