CONFIDENTIALITÉ / Privacy

What Scanapse processes and does not collect

Scanapse works without a user account and includes no audience measurement, advertising pixel, or remote font. The service still processes technical information needed to read a domain and preserve a public record. This page separates those two realities.

At a glance

What enters a record and what stays out

The distinction below summarizes public operation. Each category is explained in more detail in the following sections.

What Scanapse may keep

  • Requested domain and reading timestamp
  • Public observations useful to the record
  • Limited evidence supporting those observations
  • Comparable changes between repeated readings
  • Information needed for abuse prevention according to the implemented mechanisms

What Scanapse does not seek to collect

  • No mandatory user account
  • No advertising audience measurement
  • No visitor fingerprinting for tracking
  • No remote cookie values kept as browsing data
  • No private content behind authentication
01

Data needed to build a record

During a reading, the requested domain, public DNS and HTTP signals, some mail or transport information, calculated results, and the timestamp may be recorded. Remote cookie values are not kept; only their names and selected attributes may be described when relevant. URL parameters and fragments are removed, token-like segments are masked, and overly broad generic DNS data is not published without a reason.

02

Public records and result visibility

A record can be accessed through a public URL when it has been produced and retained by the service. This makes a reading shareable and comparable over time, but also requires care not to publish information that should not be public. Search-engine indexing rules remain distinct from the technical accessibility of the link.

03

Minimal logging and abuse prevention

The application is not designed to build a visitor history. Technical mechanisms may still be needed to limit abuse, protect forms, or diagnose an error. The application-side limiting logic described does not retain the IP address in clear text; the hosting provider may keep its own technical logs under its policy.

04

Local preferences and functional cookie

Language may be stored in a protected functional cookie when this option is used. Light or dark theme preferences may remain in browser local storage. These mechanisms support operation and interface preferences and are not used for advertising or profiling.

05

Correction, deletion, and authority to act

An organization or person with a legitimate reason may ask for review, correction, or deletion of a record concerning them. The request should identify the record and provide enough information to verify authority to act without asking for more data than necessary.

To exercise a right or ask a data question, use the Contact page so the request can be qualified appropriately. Contact Scanapse