How we measure visits.

Visits to SiteSnug

When collection is enabled, a short-lived, first-party session cookie connects page views and selected interactions during a visit. It expires after 30 minutes of inactivity, with a maximum session length of 24 hours. Signing out closes that session.

For a newly observed public visit, we can record the referring website's hostname and short source, medium and campaign labels from a tagged marketing link. We keep the first observed source for that session. Missing or blocked information stays unknown; it does not tell us who a visitor is.

After a verified sign-in, the current visit can be linked to your SiteSnug account. Authorized administrators can see your account's screen visits, selected interactions and server-recorded actions, such as preparing a release. Visits before sign-in can appear in that same account timeline.

When you request a website review

We save the contact details, website address, goal, costs, and notes you submit so we can assess the site and reply. Only authorized administrators with a verified multi-factor sign-in can open this inbox. Requesting a review does not create an account, approve paid work, or subscribe you to marketing emails.

When journey collection is enabled and your browser allows it, a saved request can count as an outcome in the same recorded visit. Marketing reports do not include the form contents. Requests still reach the private inbox if analytics is blocked. Intake records are separate from analytics and are removed in batches after 180 days as the service runs; this is not an exact deletion deadline.

Visitors to customer websites

Site owners choose whether to enable website analytics. Instrumented published sites can report page views, referring websites, broad device categories and the sequence of pages visited in a short-lived browser session. Session information is scoped to the website and its origin in browser session storage. Duplicated tabs may share a session. These visits are not linked to SiteSnug account identities.

What analytics leaves out

Analytics does not record form contents, passwords, API keys, payment details, full query strings or full referring URLs. Marketing links can supply only validated utm_source, utm_medium and utm_campaign labels; ad-click identifiers and other parameters are omitted. Campaign labels should never contain personal information or credentials.

We do not use session replay, keystroke recording or browser fingerprinting. Our analytics tables do not store IP addresses or raw user-agent strings. Hosting providers may maintain their own request logs.

Do Not Track and Global Privacy Control browser preferences stop page-view and journey observations. Server-recorded workspace access counts and the operational audit trail remain separate. Blocking scripts or clearing browser storage can also interrupt a recorded path. Counts and paths are observations, not a complete record of a person or proof of their identity.

History and access

Detailed journey reports cover at most 30 days. Customer website aggregates cover up to 90 days in the dashboard, with up to 180 dates retained for reporting. Older analytics is excluded from reports and removed in batches as the service runs; this is not an exact deletion deadline. Account records and the release audit trail are separate.

Customer website reports require access to that site. SiteSnug account timelines require an explicitly authorized administrator with a verified multi-factor sign-in.