Privacy
Last updated 14 September 2026. This covers the Amalgative desktop applications, the web version of Amalgative Redline, and this website.
The applications contain no telemetry. They do not report your usage, your documents, your configuration or your activity. There is no analytics, no crash uploading and no background reporting of any kind.
Licence checks happen on your computer. Nothing is sent anywhere to verify a licence — it works offline, and it will continue to when licences are issued.
The name and email you may enter on first run never leave your computer. They are optional, you can skip them with one click, and they are stored only on your computer — in the application's own configuration file, or in your browser for the web version.
What the applications send
One automatic request: the update check. Amalgative Redline and Amalgative Draft ask our download server whether a newer build exists — when they start and then every four hours. That request names the product, its update channel, your operating system and processor type, and, as any internet request does, your IP address — not the version you run, not your name. It carries nothing about you, your files or how you use the software. You can turn it off in Settings; with it off, the applications contact nobody on their own. Amalgative Sequence asks only when you choose Help ▸ Check for Updates; it never checks on its own.
Installing an update is always your choice. Nothing downloads or installs until you click, and the application asks before it restarts. Updates are signed, and a build that fails the signature check is refused.
Beyond that, nothing is sent unless you use a feature that needs the internet — there are no licence servers, no telemetry and no other background requests.
When you use one of the features below, it talks to the service it names, and only then. Each one needs you to set it up or to ask for it.
The AI assistant (Amalgative Redline) sends your questions — and whatever the assistant reads to answer them, which can include text from your documents and your list of markups — to the AI provider you chose, using your own account and key. That provider handles it under its own policy. A provider running on your own computer keeps it there. We never receive it, and we never hold your key.
Sending for signature through DocuSign (Amalgative Redline) uploads the document, its name, and the names and email addresses of the signers you enter to DocuSign, after you confirm each send.
Digital signatures. Adding a trusted timestamp sends a fingerprint of the signature — not the document — to the timestamp service you set. Checking whether a certificate has been revoked, which happens only when you ask, asks the certificate authority named in that certificate.
Collaboration and shared links (Amalgative Redline and Amalgative Sequence) connect to a server you set up or choose, and send it the markups or schedule changes you share, with the name you work under. Publishing a shared link from Amalgative Sequence uploads that export to the same server.
Automation. If you turn on the connection for automation tools, the application talks to the tool you connect, on your own computer by default.
Names you work under — the author on a markup, for example — are saved inside the files you create, and travel with those files wherever you send them.
The web version of Amalgative Redline
Your documents stay in your browser. Opening a file reads it on your computer; it is not uploaded to us. Your settings, recent files, markups and working copies are kept in your browser's own storage on that computer, and clearing your browser's data for the site removes them.
The application itself is served as static files from our hosting, which keeps ordinary server logs of those requests. In a browser the AI assistant works only with a provider running on your own computer, and features that need the desktop application — DocuSign, digital signatures and text recognition — are not available.
Files you send us
If you choose to send us a file to diagnose a problem, we treat it as your confidential information and use it only to diagnose the issue you reported. We never collect the contents of your drawings, documents or files by any automatic means.
This website
No analytics, no tracking scripts and no cookies. The site is static files. Your browser stores one item locally — whether you chose the light or dark theme — and that never leaves your machine.
The update list is the only personal information the site collects, and only if you fill the form in on a product page. It is optional — downloads do not require it.
We store the address, the name if you gave one, which product you signed up from, and the date, IP address and stated purpose of your consent. We keep the consent details so we can show what you agreed to and when.
You get one email asking you to confirm. Until you click it we send nothing, and an address that is not confirmed within seven days is deleted rather than mailed. We send new-build announcements and programme news — nothing else, and we do not sell, share or rent the list.
Every email carries a one-click unsubscribe, which deletes your record rather than flagging it. The list is held on our own hosting, not by a third-party marketing service.
We count downloads, not people. Downloads are served from our own storage, and our host keeps ordinary server logs for a few days. Once an hour we read those logs and keep only totals: how many times each file was downloaded, and how many copies of each application checked for updates that day. To count a copy once per day we use a code made from its address that is thrown away as soon as the count is done — we never store your IP address, browser details or anything else that identifies you.
When you click a download button on this site, your browser tells us which product, version and button it was, so we know which buttons people use. Nothing about you is sent or kept with it.
Contributions
Voluntary contributions go through Ko-fi. Whatever you give them — name, email, payment details — is held by Ko-fi and their payment processor under their own policies. It does not reach us beyond what is needed to know a contribution was made.
If you write to support@amalgative.com or info@amalgative.com, we keep the correspondence so we can follow it up.
Your rights, and how to reach us
You can ask what we hold about you, ask for it to be corrected, or ask for it to be deleted. In practice there is very little: an email thread, if you have written to us.
Write to info@amalgative.com. Amalgative LLC, an Oregon limited liability company.