Updated October 27, 2026

Privacy notice

Snared LLC operates Snared. The intended privacy and removal mailbox is removal@snared.com. Receiving is not yet active. The client assessment service remains limited to Snared-owned testing while a working contact route and production validation are completed. The interactive demo uses the same assessment service on Snared’s own website, with automatic collection on the demo page as described below.

Scope and current availability

This notice describes the Snared website, the owned integration test at pilot.snared.com, and the categories of information held by Snared's assessment service. Snared-owned simulations collect measurements from consenting test browsers and label their assessments as simulations; this does not describe all historical service records. Real client onboarding requires a working privacy contact and completed tenant-specific integration, retention and deletion checks.

If you encounter Snared on another website, that website's operator determines why it uses the integration and should provide its own notice. Contact that operator about its account records and decisions; you can also contact Snared about information processed by our service.

Interactive assessment demo

Opening the demo page automatically starts a device check. You can cancel the check or clear its display using Cancel / clear display, and run another check using Run again. It runs Snared’s signed browser SDK with its full collector profile and submits the resulting browser, device, rendering, capability, interaction-summary and network measurements to the Snared assessment service. The server evaluates them and the website verifies the assessment before showing your result. The optional interaction area is for test input only; do not enter personal information or passwords. The submitted keyboard telemetry contains timing summaries, not the characters typed.

Cloudflare supplies the browser connection’s IP address and available approximate geography and ASN to the demo edge. The edge signs those observations for the assessment service. This deployment does not capture the browser’s native TCP, TLS ClientHello, HTTP/2 settings or p0f fingerprint; missing measurements remain unavailable.

The demo uses a signed, HttpOnly first-party session cookie to restrict results to the session that collected them. The SDK may also use first-party continuity cookies, local storage and a cache pixel. The weekly count describes completed assessments in this demo session since Monday at 00:00 UTC. It is not a count of all visits across private windows or other browsers.

Assessment and signal records follow the retention periods below. Clearing the displayed result or the browser session does not erase records already submitted to Snared. Keep your assessment ID if you need us to identify a test. Closing the page stops new collection but cannot retract an assessment already received.

Scores are server-generated shadow assessments. Private browsing and VPN indicators can be heuristic or unavailable. They are not proof of fraud. Approximate IP location can describe a network exit instead of the device. Durable cross-browser identity linking remains disabled pending validation; a candidate match is a diagnostic hypothesis, not a verified shared identity.

Information we receive

Visiting our sites sends ordinary connection information, including an IP address, to Cloudflare, which hosts the sites. The owned pilot loads the browser SDK only after you agree to the collection description and start the test.

SDK submissions can include browser and device characteristics, rendering and capability measurements, interaction timing, connection and request metadata, and user/account, device and session identifiers when supplied or generated by the integration. Available fields depend on the browser, permissions and integration. The service creates assessment, event and trace identifiers, records assessment results, and verifies assessment tokens.

Operational records can include logs, metrics, diagnostic audit entries and records used to manage deletion and retention. Historical service storage includes signal and probe submissions; its full placement and legacy coverage review is still being completed.

Why we use information

We use these records to provide and troubleshoot the integration, investigate unavailable or suspicious results, measure performance, protect the service and handle privacy requests. Trial simulations are identified as simulations and do not count as evidence of real customer detection outcomes.

The current website trial uses shadow assessments. Durable identity linking is disabled. The demo signs browser-edge IP and geography observations; native TCP, TLS, HTTP/2 and p0f capture remains unavailable.

Processing and access

Cloudflare provides hosting and storage infrastructure. Authorized operators can access records through diagnostic and governed deletion tools. We make no geographic data residency commitment. A participating website receives results from its integration and is responsible for its own use and disclosure of those results.

Retention

The following periods are configured in the approved trial policy, version 2026-10-19.pilot.v1. They are policy settings, not a promise that every physical copy has already been verified to expire automatically.

Some control records remain while referenced by active records, workflows or unresolved operations. A retention or deletion attempt may need reconciliation before safe removal. Minimized evidence follows the applicable resource rule.

Current validation limits: Automatic expiry runs in bounded hourly batches on the isolated client service. Unfinished work is carried forward to later runs. Older deployments and historical records remain outside that verification and may retain records beyond the configured periods until separately reconciled or removed. Explicit governed deletion is a separate path. Provider-managed logs, traces, analytics and backups follow separate settings; the application policy table does not establish their retention. Backup removal timing has not been verified, and we do not promise immediate backup deletion. The separate historical production inventory and placement review is incomplete. We will update this notice as verified behavior changes.

Choices, questions and removal

The public demo begins SDK collection when its page loads. You can cancel a running check using Cancel / clear display or by closing the page; this does not remove information already submitted. The separate owned pilot requires you to agree and start the test before loading the SDK. Ordinary connection metadata is processed when either page is visited.

Once receiving is activated, email removal@snared.com to ask about information associated with you, request a correction or removal, or raise a privacy concern. Include the website involved and an assessment ID if you have one. We may need enough information to verify and scope a request. Do not send passwords, service tokens, raw telemetry payloads or other people's identifiers.

Requests are reviewed by an authorized operator. Available rights and any applicable exceptions depend on the circumstances and jurisdiction. Automated service data exports are currently unavailable; contact us about access requests.