SSecuTest
DatasetsPricingBlogAbout
Log InTry for Free

Browser technologies

Cookie Policy

How SecuTest uses cookies, optional audience measurement and necessary browser technologies.

Effective: October 12, 2026Version: 2026-10-12-v5Audience measurement update: October 27, 2026B2B only

1. Current use

SecuTest does not deploy advertising cookies or third-party cross-site tracking. It operates first-party product analytics for aggregate site and application measurement. Anonymous page events without a browser identifier may be counted, but they are not identifiable unique visitors.

With your optional prior consent, SecuTest also sets a first-party browser identifier to deduplicate visits over time. Rejecting these optional statistics does not prevent you from using the site or the application.

2. Optional unique visitor measurement

When you select Allow analytics, the first-party cookies st_analytics_consent=yes, st_analytics_visitor (128-bit random browser identifier), and st_analytics_first_source (first observed referrer category) are set for up to 180 days; their expiry is not extended automatically by subsequent page views. The random token is transformed server-side into a one-way reference before analytics storage. The token is not used for advertising and is not transferred to third-party analytics systems.

When you select Reject analytics, only a necessary cookie recording that choice (st_analytics_consent=no, up to 180 days) is retained; the optional identifier and stored source are deleted. The anonymous page-event stream continues separately. Separate anti-abuse systems may process network information for security and are not advertising or behavioural analytics.

You can change your choice using the Analytics preferences control on this page or the public website. Withdrawing consent stops future identified measurement and deletes the optional browser cookies; it does not retroactively erase previously recorded analytics events. For data rights requests, use the contact form.

3. Strictly necessary technologies

SecuTest may use necessary cookies or browser storage for authentication, CSRF prevention, temporary onboarding state, theme, checkout returns, abuse prevention and security. Blocking these technologies may prevent some functions from working.

4. Stripe Checkout and billing

Stripe-hosted checkout may use payment-processing, fraud-prevention and authentication technologies under Stripe's policies.

5. Other providers

Formspree may use security technologies for the contact form. Marketing and legal pages may load Instrument Sans via Bunny Fonts. The Privacy Policy explains providers and processing.

Approximate country statistics

SecuTest may infer a country code locally from a visitor's IP address during first-party marketing analytics ingestion. The IP is processed transiently and is not stored in the product-analytics event database. Country-level page views are distinct from consented unique-browser counts. GeoLite2 data created by MaxMind is used under its attribution terms; see the Privacy Policy.

6. First-party product analytics

The analytics system is hosted by SecuTest and does not send product events to a third-party analytics provider. It does not record raw referrer URLs, email addresses, submitted prospect domains, IP addresses, query strings, user-agent strings or form contents in the analytics store. Opt-in public events may contain a pseudonymized browser reference. Authenticated product events may contain a separate hashed workspace reference; the two references are not joined.

Analytics events are retained for up to 90 days. Browser identifiers represent browsers rather than verified natural persons. Reporting separates historical and unconsented page views from consented unique browsers. Anonymous daily totals of bounded event and page/source/country categories (without visitor or workspace identifiers) may be retained long term for all-time reporting; the original detailed events are still deleted under the 90-day retention limit. Lifetime unique browser counts cannot be reconstructed from these aggregates.

7. Session and local storage

Application flows may use temporary browser session storage for onboarding and non-sensitive interface preferences. Optional audience measurement uses first-party cookies, not third-party identifiers.

First-party UTM campaigns

Public campaign links can provide the source, channel, campaign name and message variant using restricted UTM tags. SecuTest counts landing-page views and CTA clicks on that same page, including anonymous views without the optional browser analytics cookie. The system does not set a campaign-tracking cookie or identify visitors across pages after rejection. Only validated non-personal categories and campaign slugs are kept; full URLs, arbitrary query parameters, advertising identifiers and individual visitor identities are not retained in campaign analytics. Daily aggregate campaign counts may remain available for long-term reporting, while detailed events follow the 90-day limit. Measurement clarification: October 29, 2026.

8. Your controls

Use the Analytics preferences control on this page to consent, reject or change your decision. Browser controls can also delete site data, but blocking necessary application cookies may affect functionality.

9. Changes and contact

We update this policy when measurement or processing changes. Contact SecuTest using the contact form for questions or rights requests.

ContentsCurrent useOptional analyticsNecessaryStripeProvidersAnalyticsControls
Privacy PolicyTerms & ConditionsCookie Policy