Privacy policy

Who is responsible

The controller is FUO.FI Cybersecurity di Nicolò Campari, VAT number (Partita IVA) 04388461206. Its registered office and other details are in the imprint. For anything about your data, write to privacy@ingres.si.

What this policy covers

What we process today: when you visit this site, when you write to us, and the usage ping of Ingressi installs. Online purchases and self-service trial requests are not open yet; this policy will describe them before they open.

Ingressi installs are run by their own operators, who decide what is processed there; license keys are checked offline, on the operator's own server.

Visiting this site

• Hosting. Cloudflare, Inc. hosts this site and delivers it through its network. To deliver each page and protect the site from attacks, Cloudflare processes your IP address and the request: the address of the page, what your browser sends with it (such as its user agent and preferred language) and the time. Cloudflare acts as our processor, and may keep data about attacks and abuse under its own terms.
• No access logs. Request logs, traces and log exports are turned off for this site, so we keep no record of individual visits. Cloudflare gives us aggregate traffic statistics derived from the requests, such as the number of visits, the countries they come from and the pages requested, with no script on the page and nothing stored on your device.
• No cookies, no tracking. The site sets no cookies and uses no analytics scripts, advertising or tracking of any kind. Fonts, styles and scripts all come from this site, and the pages load nothing from other sites.
• Theme. If you use the theme button, your choice (light or dark) is kept in your browser's local storage. It never leaves your device.
• Legal basis: our legitimate interest in running a secure website (Article 6(1)(f) GDPR). Storing the theme you chose is needed for the function you asked for.

Writing to us

• How it reaches us. Messages to sales@ingres.si and privacy@ingres.si arrive through Cloudflare Email Routing, which forwards them to our own mail server in Italy. There we read and answer them.
• What: your e-mail address, your name and anything else you put in your message or its attachments, and our replies.
• Why: to answer you and follow up: questions, quotes, orders, trial keys, license support and privacy requests. A trial or license key we send you names your company and can contain the e-mail address it was issued to. We do not send newsletters or marketing.
• Legal basis: steps you ask for before a contract, or the contract itself, when you write about buying, a trial or your license (Article 6(1)(b) GDPR); our legal obligations when you exercise your rights (Article 6(1)(c)); otherwise our legitimate interest in answering you (Article 6(1)(f)).
• How long: up to 1 month after the last message of the conversation. We keep messages longer only when they become part of a contract, an order or a legal claim, and then only as long as that requires.

The usage ping of Ingressi installs

• What it is. An Ingressi install can send a usage ping once a day to our receiver at ping.ingres.si. It is off until an administrator of the install turns it on, and the dashboard shows the exact document before anything is sent.
• What a ping contains: a random install id; the Ingressi version, edition and role (standalone or master) and the processor architecture; the number of proxy hosts, L4 hosts, users and replicas as ranges (such as 6–20); and, for each feature, whether it is in use. It never contains hostnames, domains, IP addresses, e-mail addresses, names, license ids or configuration.
• What the receiver keeps: a SHA-256 hash of the install id (never the id itself), the first and the last day a ping arrived, the time of the last ping it accepted (it accepts one every 12 hours at most), and the values of the latest ping. It does not store IP addresses, user agents or other request data, and its request logs are off. Cloudflare sees the IP address a ping comes from while delivering it, as for any request.
• Where: the receiver runs on Cloudflare Workers, and the data is stored in a Cloudflare D1 database in Cloudflare's EU jurisdiction.
• Why: to know how many installs run which versions, editions and features, so we know which releases still need fixes and what to support. Only totals are ever read.
• Legal basis: consent (Article 6(1)(a) GDPR), which also covers sending the ping from the install's server. Turning the ping off withdraws your consent, at any time; that does not affect what was sent before.
• How long: 90 days after an install was last seen, then deleted automatically. When an administrator turns the ping off, the install asks the receiver to delete everything stored for it, and it is deleted at once.

Every field of the ping is described in the product's documentation: Anonymous usage ping.

Recipients and transfers

Cloudflare, Inc. hosts and delivers this site, routes our e-mail and runs the usage ping receiver, as our processor. Cloudflare may process data in the United States and other countries outside the EU: it is certified under the EU-U.S. Data Privacy Framework, and its data processing addendum includes the European Commission's Standard Contractual Clauses. Messages you send us are then stored on our own mail server in Italy; they do not leave the EU after Cloudflare has routed them. Nobody else receives your data, and we never sell it.

Your rights

You can ask for access to your data, its correction or deletion, a restriction of its processing, or a copy in a portable format, and you can object to processing based on our legitimate interest. Where processing is based on your consent, you can withdraw it at any time. Write to privacy@ingres.si. You can also complain to a supervisory authority; in Italy, the Garante per la protezione dei dati personali (garanteprivacy.it).

No decision about you is made automatically, and nobody is profiled.

Changes

We publish every change on this page with its date. Before online purchases or self-service trial requests open, this policy will describe how they process your data.