Useful evidence. Minimal data.

Visiting this website

Our public website and the monitoring installed on a merchant’s store serve different purposes. This website keeps optional analytics and support chat off until you choose. Rejecting them does not prevent you from reading the site or booking a demo. Hosting and network services still handle the requests needed to deliver the pages.

Use in this page or the footer to change your preferences. We remember your choice in this browser’s local storage for up to 180 days. Expired preferences or a change to the configured optional services require a new choice. These preferences apply to this website origin, not your monitored storefront.

Optional website analytics

With analytics permission, our own Dozenfold SDK also records anonymous sessions, page visits, clicks, browser errors and page performance to monitor this website. It uses a site-scoped session cookie and local storage. It does not record input values. Screen replay is off; if we turn on error-session replay to test it on our site, it records a masked page reconstruction only around a browser error, never typed values. It stays off before permission, and withdrawing permission stops capture and clears its session storage.

When configured and allowed, Google Analytics measures visits to our public pages. It is not loaded before analytics consent; rejecting analytics also prevents consent-mode pings to Google. Advertising storage, advertising personalization and Google signals are disabled. Our pageview configuration sends the page path and title, excluding query strings, URL fragments and referrer values. With analytics permission, we also count named actions such as opening a product example, downloading a brief, opening a demo booking or viewing release follow-up. Each milestone is counted at most once per page load. We do not replay actions taken before permission, or send form answers, submission identifiers or support messages as analytics events.

The preference panel states whether analytics is currently configured. Adding it later requires a fresh choice; accepting chat today does not authorize future analytics. Google Analytics may use first-party cookies to distinguish visits once allowed. See how Google uses information from sites using its services.

What we process

We process session-linked error events, performance metrics, page groups, bounded diagnostic context, and funnel signals to help merchants identify and investigate storefront issues.

Diagnostic context is kept coarse. Country is a two-letter code from our network edge; IP addresses are not stored with events. Connection type, data-saver mode, device memory and processor cores are recorded as bands only where the browser exposes them. A social app’s in-app browser is recorded by name, derived from the user agent, which itself is not stored. For errors we record whether the shopper was online and whether the failing code belonged to a browser extension, without the extension’s identifier.

On Shopify, collection follows the shopper’s analytics consent from Shopify’s customer-privacy API. Custom storefronts can also run in cookieless mode: the SDK stores nothing in the browser and the collector groups events under a server-side identifier that changes daily, derived from network details that are hashed and never stored. Error-session replay never runs in cookieless mode.

Processing on behalf of merchants

For store monitoring, the merchant determines the purpose of processing and Dozenfold acts on its instructions. Session-linked information is treated as potentially personal data. Our Data Processing Terms identify the service provider and explain responsibilities, service providers, transfers and assistance with privacy requests.

What we do not collect

Dozenfold does not use browser fingerprinting, record DOM snapshots, capture input values, or create cross-session shopper identities. URLs are stripped of query strings and other sensitive components before storage.

Merchant accounts

We process store and authorized staff account information you provide or supply through an integration such as Shopify, service access credentials, and subscription and usage records to provide and secure the service. We use contact information you give us to respond to your requests. Store visitors’ contact fields are not requested for monitoring.

Storefront history and billing records

The evidence history included in a plan describes how long storefront events remain available for investigation. Our public paid plans include 30 days of evidence history. It does not mean that account, subscription and usage records are erased after 30 days.

For session-based billing, we keep period totals and a minimal record of each counted session, including a hashed session identifier scoped to that store and app. This prevents the same session from consuming allowance twice, including across billing periods. These records do not contain page contents, error messages or a persistent shopper profile. They remain with the store’s billing history and are removed when its store record is deleted through our data-deletion process.

Uninstalling stops new collection; it is not an immediate deletion of every stored record. Contact privacy@dozenfold.com about deleting store data or information you have shared with us.

Founding Store Program applications

The current website uses external demo-booking links and does not embed an application form. If you use a separately shared Founding Store Program form, Tally processes the name, work email, store details, role and problem context you submit. We use that response only to review your application and contact you about Dozenfold. See Tally’s privacy policy.

Scheduling a call

We do not load Cal.com on Dozenfold pages. If you choose a booking link, your browser opens Cal.com in a new tab. Cal.com processes the name, email, Shopify store URL, role, meeting context and optional notes you submit, together with the technical information needed to provide and secure its booking service. We use the booking details only to arrange and prepare for the conversation. See Cal.com’s privacy policy.

Support conversations

Crisp loads only after you allow support chat. It may process the current page and basic browser or device context needed to operate the conversation, together with messages and contact details you provide. Crisp uses cookies to retain the conversation and technical network information for service security. We use the conversation to answer questions, receive feedback and provide support. Crisp explains its chat cookies here. You can use email without loading chat.

Changing your choice

Turning off a previously loaded service saves your choice and reloads the page to stop its running code. We remove the known analytics or chat cookies accessible on our website; this does not erase information already processed by a provider or submitted in a conversation or application. Contact us for questions about information you have shared.

If your browser cannot save a preference, we show an error instead of claiming success. Optional services are not newly enabled. If a running service must be stopped despite a storage failure, we return you to this page with optional services disabled for that page and explain that the choice could not be saved for a future visit.

Questions

For privacy questions, contact privacy@dozenfold.com.