Privacy policy

For this site and the dashboard: Antisy Sàrl (see the legal notice). Contact for data protection: support@antisy.com (the same address as the support; write “data protection” in the subject line).

For the visitors to customer sites: the customer site is the controller; Antisy acts on its behalf as a processor (FADP, Art. 9), see section 3.

The legal bases given for each processing are those of the European regulation (GDPR, Art. 6(1)).

To know which pages are read, this site and its dashboard measure their audience with PostHog, a processor of Antisy, which keeps the data in the European Union (Germany). This measurement concerns this site, not customer sites. PostHog’s library is delivered with the site: no script is loaded from PostHog.

• What is sent: the pages viewed (the address of the page without its parameters or its fragment, its title, and the page you come from, reduced to its domain name when it is another site), the exit from a page (duration, scrolling) and the clicks on links and buttons (the element clicked, its text, the address of the link without its parameters), with the browser and its identification (User-Agent), the operating system, the type of device, the language, the time zone and the size of the screen. No campaign tag, no click identifier, no search keyword. In the dashboard, a click is sent without its text, without its link or its attributes, without a page title, and the identifier of a site is replaced in the addresses.
• What is not done: no cookie, nothing in the browser’s storage, no session recording, no profile of a person. PostHog receives the IP address of each sending, as any server does, and links the sendings to a pseudonymous identifier that it recomputes every day from the IP address and the browser. Antisy’s PostHog account is set not to keep the IP address with the events (setting “IP data capture configuration”, on “do not capture”).
• Basis: our legitimate interest in knowing which pages are read (point f). You may object to it: a browser that asks not to be tracked (“Do Not Track” or “Global Privacy Control”) sends nothing, and the button below refuses the measurement for this browser.
• Retention period at PostHog: one year, the period of PostHog’s free plan, which we cannot shorten; if Antisy takes out a paid plan, it may go up to seven years, and this page will then be updated (PostHog’s documentation, read on 28 October 2026).

• Waiting list and contact: name, business email, company and message (the last two optional), with the date. Purpose: to contact you again when access opens. Basis: your request (point b). Retention period: 90 days from the request, then the request is erased from the site’s database (a request whose notification has not yet been sent is kept until it is sent). Two copies exist outside this database, and are described below. The request also keeps the event identifier that our verification API gave to its submission: it is a pseudonymous identifier, not an anonymous one, since the API keeps with this event the IP address and the User-Agent of the submission (see the protection of the forms below). It is erased with the request and is, like the request, in the backup copies.
• Backup copies: the site’s database is backed up every day, and each copy is encrypted and kept for 7 days at most. A request erased from the database may remain in them for up to 7 more days, then disappears with the copy. The database is a PostgreSQL database of the site’s own, at the host. We have ordered no snapshot and no backup of the server from the host: these encrypted copies, kept for 7 days, are the only copies of the database. Basis: that of the data copied, and our legitimate interest in being able to restore them (point f).
• The founder’s inbox: each request to the waiting list is also sent by email to the founder, with the name, the email address, the company and the message. This email is kept for 90 days from the request, like the request itself, then deleted. Basis: your request (point b).
• Customer account: email, name entered at sign-up and password, the latter being kept only as a hash (scrypt). The sites created and the metadata of their keys are kept; the secrets are shown only once and are not stored. For two-step verification, which is mandatory: the secret of your authenticator app (encrypted) and your backup codes (as hashes) are kept as long as that app is registered, and erased when you change it. Basis: the contract (point b). Retention period after the account is closed: 90 days from the closure, then the data of the account are erased.
• Session: a sign-in cookie (__Host-antisy_session), inaccessible to JavaScript, valid for 7 days, necessary for the dashboard to work. Basis: the contract (point b). After a sign-in completed with the code of two-step verification, or its activation, a device cookie (__Host-antisy_device), inaccessible to JavaScript, valid for 180 days: it contains only an encrypted digest that designates your account, never your address, and serves only not to slow down this browser when your account receives many password attempts. Basis: our legitimate interest in protecting your account (point f).
• Appearance (light, dark or system): your choice is kept in your browser’s local storage (antisy-appearance) and is never sent.
• Limiting abuse: the IP address is used, in the server’s memory, to limit the number of attempts to sign in, to sign up and to make contact. Sign-in attempts are also counted per account, in the site’s database, under a keyed digest of the email address entered (never the address itself, nor the IP address), erased at the latest 7 hours after the last attempt. Basis: our legitimate interest in protecting the site (point f).
• Protection of the forms of this site: the home page, which carries the waiting-list form, and the sign-up page load Antisy’s own script, served by our API, to tell human visitors from automated programs. This script sends our API technical signals of the device, the course of the interaction (counters and aggregates, without the content of the keystrokes or of the fields), the IP address and the User-Agent; our server then has the submission verified by this API. For this processing, Antisy is the controller; the periods are those of the table in section 3, and the verdict is an automated decision (section 4). Basis: our legitimate interest in protecting our forms from automated programs (point f). No other page loads this script. When an account is created from an invitation, our server also reports to this API, by a signed and encrypted call, that the submission that opened this account, and the waiting-list request the invitation came from, led to a real person (outcome “succeeded”). This call passes on only the event identifier that the API had given to the submission and this outcome: neither your name, nor your email address, nor your message. It is sent only for an account created: a request that did not lead to an invitation used gives rise to no report, and no failure is reported. Since the request and the sign-up of the same person are both reported, the API can link them to each other.
• Server logs: the server keeps no log of each visit; only technical errors (for example an encrypted connection that fails) are logged, IP address included, and kept for 14 days, then erased. Basis: our legitimate interest in a site that works and remains secure (point f).

At the date of this version, this site includes, apart from Antisy’s script described above, neither a third-party script nor an advertising cookie; its only audience measurement is that of the section “Audience measurement”, above.

When a customer site protects a form or a sign-in with Antisy, the visitor’s browser sends technical measurements directly to Antisy; the customer site does not receive these measurements. Antisy then processes, on behalf of the customer site:

• 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 as digests salted per site, the interaction as counters and aggregates, without the content of the keystrokes or of 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;
• for a sign-in or a sign-up, the account identifier that the site passes on, encrypted and hashed.

Purpose: to tell human visitors from automated programs, for the security of the customer site. These data are not used for advertising. Basis: the one the customer site, the controller, relies on.

They are encrypted at rest, except what follows. The IP address and the sign-in identifier also have a blind index (a keyed digest, which makes it possible to find them without decrypting them), kept as long as they are. The event identifier that the customer site chooses to pass on is encrypted, 30 days at most; it too has a blind index, which serves only to recognise the retry of the same attempt and is erased after 25 hours. The rest of the record (verdict, score, reasons, browser family derived from the User-Agent) is not encrypted. The digest of the order of the HTTP headers (their names, never their values) is encrypted at rest, 30 days at most. The TLS fingerprint is not read today; if read, it would be encrypted at rest, 30 days at most. Hosting at Infomaniak, in Geneva, Switzerland; in service since 27 October 2026.

Encrypted backups, planned: one export a day, kept for 14 days (Antisy’s decision), and one copy a week outside the host, kept for 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.

Sub-processors and recipients:

• Host: Infomaniak Network SA, in Geneva, Switzerland. It hosts the servers of the API and of the site, their databases and the encrypted backups (see the legal notice for its contact details).
• Email relay: the service through which the emails of this site leave (notification of each waiting-list request, with its name, its address, its company and its message; invitations; confirmation and reset links). It sees these addresses and these contents on behalf of Antisy. It is Infomaniak’s SMTP relay (Switzerland), chosen; it is not yet in service.

Visitors from the European Union: Antisy accepts customers established in the European Union. Their data are processed at Infomaniak, in Geneva; the European Commission recognises Switzerland as offering an adequate level of protection. The data processing agreement, offered on every tier, meets Article 28 of the GDPR, and the rights of section 5 apply to these visitors. Antisy has not designated a representative in the European Union (GDPR, Art. 27).

Antisy’s verdict, which says whether a submission goes through or not, is given automatically, without human intervention, from the measurements described in sections 2 and 3. It is an automated decision; Antisy treats it as such under the GDPR (Art. 22) and the FADP (Art. 21).

• On this site, the protection of the forms (section 2) may refuse the sending of a waiting-list request or of a sign-up. If this happens to you, write to support@antisy.com: you may state your point of view there and ask for the decision to be reviewed by a person (FADP, Art. 21(2)).
• On a customer site, the verdict is given to the site, which decides what follows (refusing the submission, asking for a confirmation…). Contact that site, the controller; Antisy assists it in its reply.
• The verdict is not used for advertising.

You may ask for access to your data, their rectification or their erasure, the restriction of their processing, and the handing over, in a common format, of those you have provided to us (portability). You may object to a processing based on our legitimate interest, including the audience measurement, and withdraw at any time a consent you may have given: the withdrawal applies from then on.

For the data of this site: write to Antisy (contact above); we may ask you to confirm your identity. Time limit for our reply: 30 days at most (FADP, Art. 25(7)); if we must extend it, we tell you why before it expires. For the data of a visitor to a customer site: contact that site first, the controller; Antisy assists it in its reply.

You may also refer the matter to a supervisory authority: in Switzerland, the Federal Data Protection and Information Commissioner (FDPIC); if you reside in the European Union, the data protection authority of your country.

• Passwords kept as a hash (scrypt), never in clear.
• Session cookie inaccessible to JavaScript, and security headers on every page.
• Personal fields of the visitors encrypted at rest.

The date of the version in force is at the head of this page. For a significant change, we notify customers by email 30 days before it takes effect; the former version remains available on request.