SignalSearch intelligence
Cookie & local storage policy
This page explains the browser storage and security technologies used by Salyant Signal, operated by Salyant Ltd.
First-party browser storage
Signal stores information locally in the browser you use:
- Audit reports: completed reports you choose to keep.
- Competitor watchlist: website URLs and labels you add.
- Preferences: default email, audit scope and appearance choices.
- Issue review markers: findings you mark as reviewed.
- Monthly free-audit hint: local storage may retain the website domain and UTC month for which the browser has already completed an audit. This is only a display hint; the server enforces eligibility.
- Temporary checkout return details: session storage may retain the website URL, audit scope, email and random order reference needed to resume an audit after returning from the Stripe payment page.
- Analytics consent: local storage remembers whether you allowed or declined optional analytics.
- Analytics browser ID and experiment assignment: if you allow analytics, a random browser ID and the assigned A/B copy variant are held in local storage and rotate after 30 days.
This information is not automatically synchronised between browsers or devices. You can export or clear local data in Settings, or remove it using your browser's site-data controls. Clearing browser storage does not erase server-side quota, audit, payment or accounting records.
Security and anti-abuse technologies
The audit form loads Cloudflare Turnstile to help distinguish people from automated abuse. Cloudflare may use cookies or other browser storage required to provide and protect that challenge. These technologies are not used by Salyant for advertising or cross-site behavioural tracking.
Competitor discovery
When you use automated competitor discovery, Signal retrieves the publicly accessible homepage from the website you enter. It checks DNS responses before the request, validates each redirect to a public destination, limits the response size and extracts publicly visible page metadata and headings. Signal then sends search queries based on that page information, your optional business description and the selected region to LangSearch to retrieve public search results. Selected candidate homepages are checked in the same bounded way before results are displayed. Your audit email address and locally saved audit reports are not included in these discovery requests. Each suggestion includes source evidence for you to review.
Optional analytics and experiment measurement
After you choose “Allow optional analytics”, Signal sends first-party funnel events to Salyant’s n8n analytics endpoint and consented usage events to Google Analytics 4 (GA4), using measurement ID G-3ZF3X6JFWQ. GA4 is loaded only after consent. It records page views and high-level interaction events with a sanitised page path, page title and non-identifying event parameters. The page location retains only approved campaign labels (UTM source, medium and campaign); it excludes email addresses, the full website being audited, form notes and full referrer URLs. IP addresses are not included in event parameters; Google may process standard network connection metadata when receiving GA4 requests. GA4 cookies _ga and _ga_<container-id> are scoped to signal.salyant.co.uk, keeping Signal’s browser consent separate from the main Salyant website. Google processes GA4 data under its own Privacy Policy; GA4 retention follows the property’s configured retention settings. The separate first-party event table contains a random browser ID that rotates after 30 days, page group, audit scope, product and price tier, whether an email was entered (never the address itself), an A/B copy variant and limited campaign/referrer-host metadata. It does not contain full website URLs, email addresses, IP addresses, audit notes or full referrer URLs. First-party records are retained for up to 90 days and automatically deleted.
The A/B test in this version changes only the explanatory wording shown at the existing email step. Both variants retain the current email-before-audit order. The deployed audit API still requires a valid email address at audit submission, but the free allowance itself is enforced by website domain and UTC month, irrespective of the email. This experiment changes only the explanatory copy; it does not move the email step after the free readiness check.
Analytics are not used for advertising or retargeting. Choose “Decline” to prevent both GA4 and first-party event collection, or withdraw consent at any time in Settings → Privacy & optional analytics. Withdrawal updates Google Analytics consent to denied and expires Signal GA cookies where present. Consent is stored locally so the choice can be remembered. Previously collected first-party pseudonymous events remain for up to 90 days and then are deleted; GA4 data follows the property’s configured retention settings.
How to manage storage
Use the dashboard Settings page to export or clear local reports and reset preferences. You can also clear site data for signal.salyant.co.uk through your browser settings. Blocking all storage may prevent local report history and preferences from working correctly.
Contact
Questions can be sent to contact@salyant.co.uk or through the Salyant contact page.