Wolf Visibility / Legal
Cookie & Tracking Notice
Wolf Visibility uses a small first-party consent control. This notice describes the current application code; the hosting provider’s logs and separate Dodo checkout must be assessed separately.
Effective date: 30 October 2026
Your choice
On a first visit or after a choice expires/version changes, you can Accept all, Reject all (everything optional stays off), or open Preferences to choose by category. Acceptance and rejection have equal prominence. All optional categories are off unless you choose them. Strictly necessary functions remain on. You can change or withdraw choices using or the same link in the footer. Rejecting optional features does not prevent enquiries, reading the research or following checkout links.
What this site stores
- Strictly necessary: first-party localStorage key
wolf-privacy-choicerecords functional, analytics and marketing booleans, an ISO timestamp and consent version (current version: 2026-10-24-v3). It lasts up to 180 days before being treated as expired, or until the version changes or you replace/delete the choice. This stores refusals as well as acceptances so we can honour your choice on future pages/visits without repeated requests. LocalStorage is chosen instead of a cookie because no server needs this browser-only preference and it need not accompany every HTTP request. No identity, IP or form answers are stored in the consent record. - Strictly necessary: first-party cookie
wolf_report_checkout, set only when you start a report checkout. It holds a random value for one hour, is readable only by our server (HttpOnly, Secure) and only on the purchase confirmation page, and lets that page confirm it is being opened in the browser that started the purchase. It contains no personal data. It is not used for analytics or advertising. - Preferences / functional: first-party sessionStorage key
what-ranks-cta-dismissed, valuetrue, remembers a report-offer dismissal for that browser tab/session. It is read/written only with functional consent; withdrawing that consent removes it. Dismissal also works in memory without permission or persistent storage. - Analytics: only with analytics consent, a page-measurement script is loaded from
aromatic-caribou-889.convex.site(hosted on Convex). It stores three localStorage keys:am_vid(a random visitor ID, kept until you withdraw consent or clear site data),am_sid(a random session ID) andam_st(session start time; a session ends after 30 minutes of inactivity). For each page it sends those IDs, the page address and path, the referring page, screen size, browser language, any utm_source/utm_medium/utm_campaign values, scroll depth and time on page. That host also receives your IP address and ordinary network metadata. The script is not loaded on the purchase confirmation page. Withdrawing analytics consent removes the three keys and reloads the page so the script stops. - Analytics: only with analytics consent, Google Analytics 4 (measurement ID G-Y43G5L35PD) is loaded from
www.googletagmanager.com. It sets the first-party cookies_gaand_ga_Y43G5L35PD(random visitor and session IDs, up to two years) and sends page views, the page address and title, referrer, browser and device details, approximate location derived from your IP address, and interactions such as scrolls and outbound clicks to Google, under Google’s Privacy Policy. It is not loaded on the purchase confirmation page. Withdrawing analytics consent deletes the two cookies and reloads the page so it stops. - Analytics: Microsoft Clarity. Only with analytics consent, Microsoft Clarity (project y0bw962zo5) is loaded from
www.clarity.ms. It records how pages are used (clicks, scrolling, mouse movement) as heatmaps and session replays, with text typed into form fields masked, and sets the first-party cookies_clck(up to one year) and_clsk(one day) to group page views into visits, under the Microsoft Privacy Statement. It is not loaded on the purchase confirmation page. Withdrawing analytics consent deletes these cookies and reloads the page so it stops. - Marketing: only with marketing consent, the Meta Pixel (ID 1832543974433012) is loaded from
connect.facebook.net. It sets the first-party cookies_fbp(a browser ID, about 90 days) and, when you arrive from a Meta ad,_fbc(the ad click ID, about 90 days), and reports page views with the page address, referrer, browser details and your IP address to Meta Platforms, which may match them to a Facebook or Instagram account and use them for ad measurement and targeting under Meta’s Privacy Policy. The pixel is not loaded on the purchase confirmation page, and never when your browser sends Global Privacy Control. Withdrawing marketing consent deletes the two cookies and reloads the page so the pixel stops. This category does not subscribe you to emails; email permission is a separate optional form choice.
No application-set HTTP cookies, authentication cookies or form-answer local/session storage were found. If storage is blocked, consent and dismissal use page memory; the banner may return on a later visit. Expired/version-mismatched choice data is ignored, rather than treated as permission; it may remain physically in your browser until overwritten or you clear it. You may clear site data in browser settings, which resets the choice.
Network calls, images and fonts
Functional consent enables remote photographs from Pexels, external logos supplied by the audit service, and hook example video embeds from YouTube (youtube-nocookie.com), Instagram and TikTok. Video embeds load only after functional consent, without additional third-party scripts on our page. The video provider receives your IP and ordinary network metadata and may use its own storage while the embed is active. Withdrawing functional consent removes these embeds; links to the original posts remain available. Their hosts receive your IP and ordinary network metadata when the image is requested. We send no referrer with these optional images. Without permission, placeholders retain the layout; local site images still load. Withdrawing permission prevents further loads but cannot recall a completed request or a provider’s existing logs.
The old ipapi.co timezone request has been removed. Report dates use your browser’s Intl timezone locally, with the report’s timezone/UTC as fallback. The banner itself loads no third-party script; the analytics and marketing scripts described above load only with the matching consent. Google fonts are downloaded by Next.js at build time and served locally to visitors; the site does not direct your browser to Google Fonts.
Enquiry submissions use same-origin API requests and, when configured, are written with consent evidence to Neon Postgres. Browser cookie choices and marketing email consent remain separate; see the Privacy Policy for database storage. The audit page fetches its configured audit service from our server using the report ID; that requested content delivery is not browser tracking. Hosting/CDN may log requests or set infrastructure cookies. Hosting provider: Vercel Inc.. Optional images are external recipients, not necessarily processors under our instructions.
Global Privacy Control, withdrawal and future features
When your browser sends Global Privacy Control, marketing/sale-or-share permission remains rejected even if you choose Accept all. We do not sell personal information for money. The Meta Pixel may count as sharing for cross-context behavioural advertising; it runs only if you opt in to marketing and never under Global Privacy Control. The older Do Not Track signal does not change current site behaviour; advertising tracking is off unless you opt in.
Optional integrations must check the relevant category before storage or network access, respond to withdrawal and clean up optional data where appropriate. Current choice control is first-party, with no external consent-management vendor. Consent withdrawal is available through the footer on every page. Contact support@wolfvisibility.com for privacy help and see our Privacy Policy.
Checkout and other websites
Clicking a report purchase link navigates to Dodo Payments, the merchant of record, which may use payment, fraud and other cookies/technologies under its own notice and choices. Our purchase buttons request a hosted Checkout Session from this site’s server; if no API key is configured, they use the product’s static hosted link with a return URL. We do not embed a browser payment SDK or pre-load checkout scripts. Returning buyers’ payments and purchase grants are verified through server-to-server Dodo API requests; the thank-you page uses no-store caching and sends no referrer. This necessary purchase verification works regardless of optional cookie choices. Other external links also have their own privacy practices. Our settings cannot control storage or requests on a different origin.
We will update this notice and obtain new permission where needed before introducing a materially different optional purpose/provider.
