Privacy Policy

This policy covers getquario.com, the marketing site you are reading. It does not describe the quario engine's behavior on your own systems. quario runs on your infrastructure, and it verifies license keys offline — the key is never transmitted.

There is no account and no newsletter. Two things do take something you type. A chat window, if you accept cookies and open it, takes your message and the email address it asks for first. Buying a license creates a record, and it happens on Stripe's checkout rather than on this site. Each has a section of its own below.

The pages are static files. Serving one carries a request through Cloudflare, which fronts the site, to the origin on Fly in Amsterdam. The origin keeps a request log: which pages were asked for and how they were answered. It holds no IP address and nothing derived from one. Cloudflare keeps none on quario's behalf. What each provider keeps to operate and secure its own network is governed by its terms, not by this policy.

These pages carry one analytics script, PostHog. There is no tag manager and no advertising script. It records which pages are read and in what order, the clicks on them, and the referrer that brought you. It also records the browser and the device.

What it stores on your machine is your decision, and until you make one it stores nothing at all. A small banner asks once. Before you answer it, no cookie is set and this origin's storage stays empty. The visit is still counted, by the daily hash described below, which is the same way a refusal is counted.

Deny, and one entry is written to remember the refusal — no cookie, and nothing that identifies you. The counting carries on as before, and that is the whole of it.

Accept, and PostHog sets a cookie of its own, ph_<project key>_posthog, holding a device identifier, a session identifier, and the page you arrived on. It keeps the same in this origin's storage. That identifier persists between visits, which is the difference the banner asks about. It is also what lets the chat window keep a conversation open.

Where you have not accepted, an identifier is derived instead, on PostHog's servers. It hashes that day's rotating salt together with your IP address, your browser's user agent, and this site's domain. The salt is deleted once the day's events are processed. The hash cannot be turned back into any of its inputs. It also changes daily, so tomorrow's visit is a stranger's as far as this site can tell.

Your IP address is an input to that hash and nothing else. It is stripped before anything downstream reads it, so no location is derived from it and none is recorded. Session replay and surveys are switched off, and the script this site serves does not carry them.

Nothing accumulates at the other end either. This site switches person profiles off, so the events stand alone and PostHog builds no person from them.

Events go to PostHog's European region, eu.i.posthog.com. The script itself is fetched from eu-assets.i.posthog.com. It loads on the published site alone — a local build serves the pages without it.

No cookie reaches you from the infrastructure either. Cloudflare fronts the site without setting one, and the origin sets none. Every cookie described here is set by the script in your browser, never by a response from this site.

None of this is used to build a profile of you. It is not sold, it is not rented, and it is not shared for advertising.

Four, and each has a job. Cloudflare fronts the site and terminates the connection. Fly runs the origin that answers it. PostHog is the analytics named above, and it also carries the chat. A message you send, and the email address given with it, are held by PostHog as a support ticket. A data processing agreement covers that arrangement. Stripe is the fourth, and only buying reaches it: the checkout runs on Stripe's own pages, and reading this site never contacts it.

Nothing else is reached. Web fonts are served from this origin, not from a font vendor, so fetching a page contacts no font host.

Links out — to GitHub, for instance — open sites that operate under their own policies, not this one.

A visit leaves little to keep. The daily hash that counts an unaccepted visit expires with the salt it was made from. The request log is held by Fly, which runs the origin, for a week. Two things are kept longer than that. A message sent through the chat is kept by PostHog as a support ticket for as long as that ticket is. The purchase record described below is the other, and the period for it is stated there.

Buying a Deployment license sends you to Stripe's checkout, where Link, Stripe's merchant of record, takes the payment. It collects your name, your email address, your country, and a company name if you give one. It also asks for the licensee name to print on the key. Card details go to Stripe alone and never reach this site. OEM is still arranged by email.

The record is held to perform the contract and to meet the statutory invoicing obligations that come with it. Link sells the license, raises the invoice and accounts for the tax, and holds that record. The trader named under Contact below reads the order back to issue the key, and again to write the renewal notice a year later. The bookkeeping sees the money and not you: no customer detail is entered into Moneybird, the accounting system. The license key itself carries the licensee name.

The record is kept as long as the statutory retention period on invoices requires — seven years under Dutch tax law — and then no longer.

None of it is used for marketing. It is not sold, and no advertising profile is built from it.

The banner is the choice, and it is a real one. Denying leaves nothing on your machine but the record of the refusal, and blocking the script stops even the counting. The request log records the request either way. Reading this site still creates no account to close.

There is no second banner for changing your mind. Clearing site data for getquario.com forgets the decision, and you will be asked again on your next visit.

A Do Not Track or Global Privacy Control signal is not acted on. The banner asks the same question those signals answer, and nothing about you is sold or shared for either to object to.

Where personal data about you is held, you can ask for a copy of it. You can ask for it to be corrected or erased. You can ask that its use be restricted, object to that use, or ask for the data in a portable form.

In practice these reach the purchase record, and any chat you have started. A visit where you denied or ignored the banner leaves no identifier, so there is nothing there to look up, correct, or delete.

Write to [email protected] to exercise any of them, and you will have an answer within a month. If you think this is being handled wrongly, you can complain to the Autoriteit Persoonsgegevens, the Dutch supervisory authority.

Questions about this policy: [email protected]. The controller is quario, a trade name of Webstronauts, KvK 61815977, BTW NL001146763B06.