Data collected and privacy
What the browser sends to Antisy, what Antisy keeps and for how long. This page summarises the privacy policy, which is authoritative.
This English translation is provided for information only. The French version is the authoritative text and prevails in the event of any discrepancy. Read the French version
Who is responsible for what
- Your site
- The controller for the visitors to its forms.
- Antisy
- Processor (FADP, Art. 9), under contract: it processes these data on behalf of the site. The template data processing agreement is online.
- Purpose
- To tell human visitors from automated programs, for the security of the site. These data are not used for advertising.
What the browser sends
When you protect a form with Antisy, the visitor’s browser sends technical measurements directly to Antisy. Your site does not receive these measurements: it receives a token, then a verdict.
- What the script measures in the browser: the capabilities the browser declares, the languages and the time zone of the browser, the graphics rendering and the fingerprint of the device, signs of automation, the behaviour of the JavaScript engine and the course of the interaction. The fingerprint leaves as digests salted per site, the interaction as counters and aggregates, never the path nor the content of the keystrokes and the fields.
- What Antisy’s server reads from the request: the order of the HTTP headers, the IP address, the User-Agent and the request context. The order of the headers is kept as a digest of their names, never their values.
- For a sign-in or a sign-up, the account identifier that your site passes on, encrypted and hashed.
These data are encrypted at rest, except a few items kept in clear, which the privacy policy names one by one. The hosting is at Infomaniak, in Geneva, Switzerland; it has been in service since 27 October 2026. The encrypted backups are planned: one export a day, kept for 14 days (Antisy’s decision), plus one copy a week outside the host, 14 days at most; an erased item of data may remain in them for up to 14 days. So that a restore does not bring back a person who was erased, a register kept outside the database keeps their blind index for 30 days, 44 days at most with its copies.
How long
| Period | What happens |
|---|---|
| A few minutes | Measurements sent by the browser for a token: kept encrypted for a few minutes, the time it takes to verify the submission, then deleted. If keeping is switched on for the site (it is off by default), some of them are kept for 30 days, encrypted: the graphics rendering measured, the class and two digests of the graphics processor, the behaviour of the JavaScript engine and the signs of automation; neither the capabilities the browser declares, nor its languages and time zone, nor the overall fingerprint of the device, nor the course of the interaction. |
| 30 days | IP address, User-Agent, request context (accepted language, names of the headers present, referrer host, path, method; characteristics of the connection: TLS and HTTP versions, negotiated protocol, presence of Client Hints, digest of the order of the headers; and, when the site passes them on, the time taken to fill in the form and the rank of the attempt in the session) and event identifier chosen by the site, encrypted while they are kept; digest of the order of the HTTP headers, encrypted at rest (their names, never their values); results of the verification of the token: all erased from the record. No prefix or digest of the IP address is kept beyond that. The event identifier also has, apart, a blind index (a keyed digest) used only to recognise the retry of the same attempt: it is erased after 25 hours. |
| 90 days | Sign-in identifier (encrypted and hashed), outcome of the attempt, outcome reports sent by the site: erased. |
| 180 days at most | What remains (verdict, score, reasons, browser family, event type, timestamps): the record is deleted. |
These are the periods Antisy applies. After 90 days, a record no longer carries either the sign-in identifier or the address: it can no longer be found from either of them. See also the data processing agreement.
On your side
- Your own privacy policy must describe this processing and name Antisy. The data processing agreement offers, in its section 7, a model text to adapt and to have validated (see the agreement).
- For the rights of the visitors (access, rectification, erasure), they contact your site first, the controller. Antisy assists you in replying.
- The token your server verifies is opaque, and the response of
/v1/siteverifycontains only the verdict, indicators, the time of submission, the host name of the page, the action label and an event identifier.
Antisy accepts customers established in the European Union: the data are processed at Infomaniak, in Geneva; the European Commission recognises Switzerland as offering an adequate level of protection, and the data processing agreement is offered on every tier. Antisy has not designated a representative in the European Union (GDPR, Art. 27).
Sub-processor: Infomaniak, in Geneva, Switzerland (hosting and backups). No visitor data leave Switzerland without the customer’s written authorisation, and none is sent to an artificial intelligence service.