Skip to content
Frictions

Your data, explained

Know what your browser stores.

Understand the difference between this website’s services and the recording settings on your own WordPress store.

Browsing this websiteProduct previews and local controls Accounts & supportSession and request-security mechanisms Setting up your own storeConnect and test shopper consent The interactive demoTemporary workspaces, access and cleanup

Product pages and replay

The synthetic replay runs in your browser and does not create an order or record a real shopper. Currency controls update displayed prices locally. A URL or manual choice takes priority; otherwise our existing Cloudflare network suggests an approximate country, with browser settings as a fallback. No IP address or currency preference is saved by the selector, and it does not request GPS access. The replay is an example, not a recording from your store.

Accounts, support and optional signup

Account and support services use necessary session and request-security mechanisms. Support may offer spam protection, with its own explanation before loading. Read the support privacy notice for details.

The optional newsletter has separate signup, confirmation and unsubscribe controls. You do not need to subscribe to read the site or request support.

Website performance measurement

Cloudflare’s performance beacon runs on website pages including the blog. It reports loading and responsiveness without cookies or browser storage. It can run without an analytics choice and with GPC or Do Not Track enabled. This is separate from your store’s shopper-consent settings. Read what is measured and who receives it.

Recordings on your WordPress store

Frictions capture requires a supported consent integration and an affirmative shopper analytics choice. Configure and test that choice on your own checkout. Your store’s notices should explain its actual recording and storage setup.

Read the consent setup guidance · Understand recording data

Interactive demo sessions

Starting the interactive demo uses an essential __Host-frictions_demo browser cookie for access and session limits. It expires after 24 hours and uses Secure, HttpOnly and SameSite=Lax protections. WordPress sign-in cookies are scoped to the individual workspace. Frictions stores appearance, fullscreen and guide preferences in browser local storage until you clear them; these preferences contain no replay data or notes. The demo gateway’s 30-minute access limit is separate from the browser cookie’s expiry.

The demo has fictional recordings and temporary, isolated changes. It does not connect to your store or send email. Use Reset or End when finished; do not put personal information into notes or briefs. Read the demo data and limits notice for the session, cleanup and rate-limit details, or the demo privacy summary.

Newsletter invitation preference

The setup guide and articles can show an invitation after you have spent time reading. Desktop uses a closable dialog when you move to leave; mobile uses a small card that does not move focus or block the page.

Viewing or closing with × or Escape stores no dismissal preference. Choosing Not for 30 days explicitly saves one first-party cookie named frictions_newsletter_dismissed. It contains only its expiry time, no email, subscriber identity or browsing history. It suppresses invitations on this browser for 30 days. It is separate from analytics and marketing consent.

Opening a signup form and recognising an already confirmed subscriber use separate protected cookies. Read newsletter privacy.