privacy

Last updated 31 August 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.
  • There is no analytics on this site, no tracking pixels and no advertising. The only cookie we set is the one that keeps you signed in, which does not need consent, so there is no cookie banner.
  • Two things on this site are loaded from elsewhere: the typeface it is set in, which every page fetches, 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 is served from here.

what we hold

your email address

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.

the purchase

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.

activated devices

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.

your session

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.

the activation hand-off

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.

mail you send us

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 code, if you were given one

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.

what we do not collect

  • We do not run analytics, count page views, record sessions or use advertising identifiers. 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.

Paddle

The merchant of record for every purchase. They take the payment, hold the billing and tax data, and tell us a transaction completed.

Resend

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.

our hosting provider

Runs the web server and the database the account lives in, on a rented virtual machine.

our font host

Serves the typeface this site is set in. Your browser fetches it directly, so they see your IP address and browser on each page you load.

We do not sell data.

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.

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.

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.