privacy
Last updated 19 September 2026
in short
- We hold an email address, a hashed identifier and a name for each device you activate, and the record of your purchase.
- If you write to support, we keep the message and our answer, so that the conversation can be read as one thread.
- While you are signed in, your IP address and browser are recorded with the session.
- We count how many people read the public pages. Nothing is stored in your browser for it and no advertising or tracking service is involved. The identifier that lets us tell one reader from another is worked out on our server, kept for the rest of the day, and deleted within an hour of the day ending. There is more about it below.
- The only cookie we set is the one that keeps you signed in. It is strictly necessary, so it does not need consent, and that is why there is no cookie banner. The site is not cookie-free: if you have an account, you have that cookie.
- Two things on this site are loaded from elsewhere: the video clips and screenshots, which come from a content delivery network, and the checkout, which only the checkout page loads. Reading the rest of the site sends nothing to Paddle. Both see your IP address, as any server you fetch a file from does. Neither of them counts you, and everything else on the site, the typefaces included, is served from here.
what we hold
You give it at checkout, or when you ask for a sign-in link. It identifies your account and your licence, and it is where sign-in links are sent. We store it lowercased.
Paddle.com tells our server over a signed webhook that a transaction completed. We keep the transaction id and the email on it. Card numbers, billing addresses and tax details stay with them and are never sent to us.
When you activate, we store a SHA-256 hash of an identifier the operating system reports for that device, the time, and the name the computer reports for itself, which is what labels the device on your account page. You are not asked for any of it; the plug-in reads it off the computer and sends it. The hash cannot be turned back into a serial number, but it is stable: the same computer produces the same hash, so it could tell us that one device was activated under two accounts. We use it to count seats and for nothing else.
A cookie and a matching row keep you signed in between visits, and that row records the IP address and browser the sign-in came from. The cookie is strictly necessary, because the account does not work without it. The address is kept for security, so that a compromised account can be investigated. The row is deleted when the session expires or you sign out.
While the plug-in waits for its licence, the signed token sits in a row under an id the plug-in generated. It stays readable for fifteen minutes, so that a dropped reply costs a retry rather than the licence, and it is deleted the next time anyone activates. The token inside only unlocks the device it was issued for.
When you write to support@aquirosa.com, the mail is stored in our database, not only in a mailbox: your address, the subject, the text and any HTML version of the message, the headers that say which earlier message it answers, and the file name, type and size of anything you attach. The attachments themselves are not downloaded and not kept. Our replies are stored the same way, so that a conversation can be read as one thread. When it is opened, we look up whether the address it came from has a licence, so that whoever answers can see what you bought without asking you to prove it.
A gift licence is the same as a bought one, and its record is a code, the address it was meant for, the note whoever sent it wrote, which is quoted in the gift email you received, and the address that actually redeemed it. There is no transaction and no payment data, because nobody paid.
how we count readers
We keep a daily tally of how often somebody arrived on a public page, roughly how many people that was, which country they came from, and which site linked them here. We do not keep which page it was. We also count how often an installer download starts, by version and operating system. The account pages, the checkout and the admin area are left out of it entirely.
There is no script in this page doing any of it, and nothing is written to your browser. The server counts the request it already had to answer, and once you are here, moving from one page to another happens inside your browser and we never hear about it. To tell two readers apart without recognising either of them, it makes a short code out of your IP address and your browser's user agent string, mixed with a secret that is generated at random each day and never written down anywhere else. The code cannot be turned back into an address, it is different tomorrow, and the same person on two days is two visitors to us.
Those codes and the day's secret are deleted within an hour of the day ending. The totals stay: how many per day, per country, per referring site and per release. No page, IP address, user agent string or account is stored in those totals. Country and network lookup happen on our own server against local databases, so no visitor address is sent anywhere for it.
We keep a 7 day access log. For each request for a public page it holds the time, your IP address, the country and the network operator that address belongs to, your browser's user agent string, the path of the page (without anything after a question mark), and the site that linked you here. We keep it to tell people from automated traffic and to notice abuse. Most requests to a small site come from scripts that claim to be a browser, and the network they come from is the only reliable way to see that. When a request arrives we decide whether it looks like a person at a browser, and only that yes or no goes into the daily totals. Rows are deleted when they are seven days old. The log is not linked to your account, and we do not use it to follow anybody from one visit to the next.
The numbers are approximate on purpose. Two people on the same connection look like one, one person on a phone and a laptop looks like two, and a page your browser draws for itself — from its own cache, or as you move around the site — is not counted at all.
Requests whose user agent string says they come from a search engine, a link preview, a monitoring service or a script are not readers, and are not counted as any. So that we know how much of the traffic they are, we keep a daily count of them sorted into seven fixed kinds of our own naming, such as “search” or “script”. That word is all the count keeps. The request itself is in the seven-day log described above, like any other.
Country and network lookup use the IP to Country Lite and IP to ASN Lite databases by DB-IP, licensed under CC BY 4.0.
what we do not collect
- Beyond the daily totals and the seven-day request log described above, we do not record which pages anybody read, in what order, or on which visit. We do not use an analytics company, a tracking pixel, a session recorder or an advertising identifier. There is no mailing list unless you ask to be on one, and we collect nothing about the audio you make. The device hash above is the only thing here that identifies a device, and it is used to count seats and for nothing else.
- The plug-in does not report usage, presets or projects. It contacts our server in two situations: when you activate a device, because you clicked activate, and then a few times a day to ask whether that device still holds its licence. The second request sends the licence file and nothing else, and the answer is either yes, or a signed statement that the device has been taken off, which is how revoking a seat and refunding a purchase take effect.
- We do not record that it asked: not the time, not a count, not an address. There is no log of when you work.
- Nothing expires. If that request never gets through, whether because of a missing network, a firewall, or this site no longer existing in ten years, the licence stays exactly as it is, indefinitely.
who else handles it
Four companies, and no others.
The merchant of record for every purchase. They take the payment, hold the billing and tax data, and tell us a transaction completed.
Carries our mail in both directions. They deliver the sign-in, licence and gift emails, and they also receive everything sent to an aquirosa.com address: mail for the domain is routed to them, they hold it, and they tell our server it arrived. Your address and the text of the message pass through them either way.
Runs the web server and the database the account lives in, on a rented virtual machine.
A content delivery network in Slovenia that serves the video clips and screenshots on this site from a server near you. Your browser fetches those files from them directly, so they see your IP address and browser when a page shows one. They get nothing else: no account, no cookie, and their logs store the address shortened.
We do not sell data.
who is responsible for it
Lukas Oppenheimer, c/o flexdienst – #22083, Kurt-Schumacher-Straße 74, 67663 Kaiserslautern, Germany. Questions about any of this go to support@aquirosa.com.
why we are allowed to hold it
We hold it to provide what you paid for: an account, the software, and a licence that runs on two devices. That is the contract between us, and it is the legal basis for most of what is listed above. The device hashes have a second basis, our legitimate interest, because without them the two-device limit could not be enforced.
Support mail has that second basis too. Answering the question you sent us, and keeping the answer so that your next one can be read in context, is what you wrote in for. A gift licence rests on the same footing as a bought one: its record is what the licence is.
Counting readers rests on our legitimate interest under Art. 6(1)(f) GDPR: we need to know whether the documentation is being read and whether anybody is downloading the software. We take the least that answers that question, keep the visitor codes for less than a day, and keep no profile of any reader. The seven-day request log rests on the same basis: our interest in telling readers from automated traffic and in keeping the site secure. Because nothing is stored in or read from your device, we take the view that §25 TDDDG consent does not apply. You can object to this processing under Art. 21 GDPR by writing to the address under your rights, below.
Serving the clips through a content delivery network rests on the same basis: our interest in a site that loads quickly wherever you are and stays up on a busy day. The network is run by a company in the EU under a data processing agreement with us, and it acts only on our instructions.
how long
The licence is perpetual, so the account is too. We keep it for as long as the licence exists, so that you can sign in years from now, download the current 1.x build, and activate a new device. Revoked activations keep their row, which is the hash and the two dates, so that the seat count stays accurate.
Support mail is kept for as long as the account is, and for the same reason: a question you ask next year is easier to answer beside the one you asked this year. Nothing deletes it on a timer. If you want a conversation gone before then, say so and we will delete it, whether or not you want the account itself removed.
The reading codes and the day's secret are deleted within an hour of that day ending in Berlin. The daily totals that remain are kept indefinitely, because they are the history of how the site was used and there is nobody in them to identify. A request for a copy of your data cannot return them for the same reason: once the codes are gone, no row in there can be traced to a person. The request log is different for the seven days it exists: it holds IP addresses, so if you tell us the address you used we can find your rows in it, send you a copy, or delete them.
If you ask us to delete the account, we delete it along with the licence, its activations and any support mail on that address. That cannot be undone, and the licence cannot be activated again afterwards. Devices that are already activated keep working, because the plug-in stops only for a signed answer, never for a missing one.
your rights
You can ask for a copy of what we hold, ask us to correct it, ask us to delete it, ask for it in a portable form, or object to us holding it. You can also complain to your national data protection authority.
Write from the address on the account to support@aquirosa.com. We answer within thirty days, usually sooner.
security
The site is served over HTTPS and the database is not reachable from the internet. Licence files are signed with a private key that only the server holds. The plug-in carries the public key, so it can check a signature but cannot create one. Card details never reach our hardware.
changes
This page shows the date it last changed. If we add a processor, or start collecting something that is not listed above, we will update this page first and email account holders if the change affects them. The terms cover the rest.