Four activities, described one at a time.

The controller is Binse Analytics, a registered business in Ireland. The address and registration details are on the legal notice.

For anything about personal data, including a request to see or delete what we hold, write to privacy@binselytics.com. It reaches the same person as every other address on this site.

There is no data protection officer. A one-person business does not need one, and pretending to have one would be worse than saying so.

This site runs no analytics. No page-view counter, no tag manager, no tracking pixel, no heatmap, no session recorder, no A and B testing tool, no chat widget and no advertising script. There is no form anywhere on the site, so there is nothing to submit and nothing to capture.

The two small scripts this site runs store nothing. They open a footnote and draw the progress thread in the left margin, and they work entirely inside the page you are looking at.

The fonts are served from this site rather than from a font service, so reading a page here does not announce you to a third party. That is enforced rather than intended: the build refuses to publish if the string that would fetch a font from elsewhere appears anywhere in the output.

The site is served by our hosting provider, currently Cloudflare Pages. Like any web server, it receives the internet address your request came from, together with the page you asked for, because that is how a page is delivered and how abuse is stopped. We have switched on no analytics product of our own there. The site sends a Content-Security-Policy header that names everything a page is allowed to load, and on every page except the price page that list contains nothing outside this site at all.

No cookies, no local storage, no session storage, no database in your browser, nothing. Close the tab and there is no trace of your visit on your machine or on ours.

That is also why there is no consent banner. Irish law, Regulation 5(3) of S.I. 336/2011, asks for consent before anything is stored on or read from your device unless it is strictly necessary for the page you asked for. Nothing is stored here at all, so there is nothing to consent to. A banner on a site like this one would be advertising tracking that does not exist.

One exception, named so that the paragraph above stays true. The price page loads one script from the payment provider, so that the checkout can open over the page instead of sending you to another site. If you open that checkout, you are dealing with the payment provider: what it stores on your device, and what it does with what you type into it, is covered by their privacy notice rather than by this one.

What we hold. Your email address, whatever you chose to put in the message, anything you attached, and our reply. If you are asking about a licence, that usually includes your computer code, and sometimes your order reference or licence key.

Why. To answer you. If you are a customer, that is part of performing the contract. If you are not a customer yet, it is our legitimate interest in replying to someone who wrote to us, and yours in getting an answer.

How long. Support email is kept while it is still useful for supporting you, which usually means for as long as you hold a licence and a reasonable period after it, and is then deleted. Anything that is part of the record of a sale is kept for as long as Irish tax law requires business records to be kept.

Who else sees it. The email provider that hosts the mailbox, because that is what hosting a mailbox means. Nobody else. There is no support desk system, no ticketing tool and no CRM, because the mailbox is read every working day.

Payment is taken by our payment provider and merchant of record (currently Lemon Squeezy). They are not processing data on our behalf; they are the merchant of record and their own controller for the payment. Their privacy notice governs what they collect at the checkout, and it is linked from the checkout itself.

We never see your card details. They do not pass through this site and they do not reach us in any form.

What reaches us from a sale. Your name, your email address, an order reference and what you bought. That is what a licence has to be issued against, and it is the legal basis of performing the contract you entered into.

The licence key. The payment provider makes the licence key at the checkout and sends it to you with the receipt. They keep it with the rest of their customer record of the sale: your name, your email address, the order, the key, and each activation made with the key, which is described in the next section. That record is held by them, as merchant of record, and their privacy notice covers it. This site plays no part in delivering the key and receives nothing when it is delivered.

Nothing has been sold yet, so the paragraphs above describe what will happen rather than what has happened.

What the app sends depends on which kind of key was entered on its licence screen. Neither kind carries anything about your work: no file names, no data, no user name, no company name, no list of what you have built. Each request also names the app and its version, and reaches the other end from your internet address, as any request does.

A Lemon Squeezy licence key, the kind a purchase through our payment provider comes with. When the key is entered, the app sends the key and an instance name, which is the computer code described below, to api.lemonsqueezy.com. After that it sends the key and the id Lemon Squeezy gave that activation: in the background once the last confirmation is more than 7 days old and the app is in use, and when you press Release this computer. The reply includes the name on the order, and the app keeps it on your computer to show who the copy is licensed to. No server of ours is involved. Lemon Squeezy keep each activation against the key, with its instance name, as part of their record of your purchase.

A key from the key bank, for a shop that hands out keys from a list rather than making its own. The app sends the key, the computer code, the name of the product and the version of the app to our activation service at activate.binse.app, when the key is entered and again about once a week while the licence renews itself.

What the computer code is. A one-way hash of the Windows machine identifier, written as BIN-XXXX-XXXX-XXXX. It cannot be turned back into the identifier. It is personal data all the same, because it identifies a computer that belongs to a person, and it is treated as such here.

What our activation service stores, for a key from the key bank. A hash of the key rather than the key itself, the product, how many computers the key allows, whether it is active or revoked, the date its term started and the date it ends, and for each computer that has activated: its computer code, the first and last time it activated, and how many times. A key issued to a named customer by hand also carries that name, an email address and the payment provider's order reference. That list is the whole record, and it is read from the code that writes it rather than described from memory.

What stays on your computer. For a Lemon Squeezy key, a small record of the activation: the key, the activation id, its status and end date, when it was last confirmed, the name on the order and the computer code, sealed with Windows so that only your account on that computer can read it. For a key from the key bank, or a licence issued by hand, a signed licence file holding your name, your computer code, the date it was issued and the date it expires, checked on your computer.

Why, and for how long. To issue a licence and to keep it to the number of computers it was sold for. That is performance of the contract. A record is kept while the licence is live, and afterwards for as long as Irish tax law requires records of the sale to be kept.

Two honest notes. No store is open as of 2026-09-13, so no key of either kind has been activated for a customer, and the activation service is not deployed. Today a licence file is issued by hand and sent by email, and the computer code reaches us in a message you wrote rather than in a request the app made. Neither of those is hidden in a footnote on another page.

Your workflows, dashboards, diagrams, catalogues, schedules, reports and data files live in your own Documents folder. The engine runs on your machine, on 127.0.0.1:8767, and we have no way to reach it. Nothing you open, build or export is sent to us, and there is nowhere for it to be sent to.

If you point the software at a warehouse of your own, your query goes to that warehouse under your own credentials. That is your relationship with that provider, and we are not a party to it. The software adds no cloud of its own, and it does not remove yours.

Two features can send your work off the machine, and both are in Binse Enterprise only. Neither exists in Binse, and in Binse Enterprise neither does anything until somebody turns it on. They are named here because this page has to say so when anything can leave your computer.

Sharing a diagram live works through a relay server, and there is none of ours. A machine in your own organisation runs it, against your own identity provider, so the diagram's changes, who is present, the comments and the version history go to a server of yours. We receive none of it and cannot reach it, and your organisation is the controller for whatever that relay keeps. A room can be end-to-end encrypted, and then the relay holds ciphertext it cannot read.

The AI assistant in Diagrams sends nothing until a person enters a key of their own for an AI service. After that, each instruction sends that service the outline of the page you are on, the names of the pages, what you have selected and what you type or paste in, and it may read more of the same diagram while it answers. It is never sent your files, your other diagrams, the pictures inside the diagram, or anything outside the document, and the panel prints that list before you use it. The key is kept on your computer for your Windows account and never leaves it except to that service. Because the key is yours, so is the relationship: what that service does with what it is sent is covered by its own terms and its own privacy notice, and we are not a party to it and receive nothing.

One defect, since this page is about third parties. Two of the product's own screens still fetch a web font from an outside font host, so opening them sends your internet address to that host before you have done anything. No data of yours is involved and it is not telemetry, but a request to a third party is a request to a third party. It is published in full as one of this site's receipts, the fix is to serve both fonts from inside the product, and the receipt keeps its date when the fix ships. Until then, it is listed here.

The payment provider and the hosting provider are both established outside the European Economic Area, so personal data connected with a purchase, including the confirmations of a licence key, and the connection data involved in serving a page, are processed there. Each publishes the transfer safeguard it relies on in its own data processing terms, and we rely on what they publish. We have not audited either of them, and we are not going to say we have.

Nothing else leaves Ireland. There is no advertising network, no data broker, no analytics vendor and no third-party support tool in any of this.

The two Binse Enterprise features in section seven are not an exception to that, because neither of them passes through us. A collaboration relay is a machine your organisation runs and puts wherever it puts its own servers, and an AI service reached with your own key is your arrangement with that service. Where that data goes is a question for your organisation to answer about its own relay and its own key, and this notice cannot answer it for you.

No decision about you is made automatically, and there is no profiling. There is nothing here to profile with.

You can ask for a copy of the personal data we hold about you, ask us to correct it, ask us to delete it, ask us to restrict what we do with it, object to what we are doing, and ask for it in a portable form. Where we are relying on a legitimate interest, you can object to that specifically.

Write to privacy@binselytics.com. You get an answer within one month, which is the period the law allows, and usually a great deal sooner, because the amount of data involved is small enough to look at by hand.

Deleting the activation record for a live licence means the licence can no longer be reissued or moved to another computer, and we will tell you that before doing it rather than afterwards. A record held by the payment provider is theirs to delete, and we will say how to ask them.

If you think we have handled your data badly, you can complain to the Data Protection Commission, the Irish supervisory authority, at www.dataprotection.ie. Their current address and their complaint form are on that site, which is why they are not reprinted here to go stale. You can complain to them without going through us first, although we would rather you told us and gave us the chance to fix it.