Privacy
Last updated 31 August 2026.
Fluxmon sends a message to a person and waits for an answer. If nobody answers, it sends the message to the next person. To do that it needs the message, the list of people, and a record of who answered. This page says what it keeps, why, and for how long.
The service at fluxmon.com is run by JHB Holding AS. Fluxmon is also open source, and anybody can run their own copy. This page describes the copy at fluxmon.com only.
Who is responsible for what
Fluxmon holds two kinds of personal data, and the responsibility is not the same for both.
For your data as an account holder — your sign-in identity, your API key, the feedback you send — JHB Holding AS is the controller, and the rights below are exercised against us directly.
For the data you put into Fluxmon about other people — the addresses you configure as destinations, what you write in a missive, and the record of who acknowledged it — you are the controller and we act on your instructions. Two things follow. If somebody you message asks to see or delete what Fluxmon holds about them, that request is yours to answer; we will help, but we cannot decide it for you. And if you use Fluxmon to process other people's personal data, the GDPR requires a written data processing agreement between us — ask for one at privacy@fluxmon.com.
What is stored
Your account
When you sign in with GitHub or Google, Fluxmon keeps the identifier that provider gives it, your name, and your email address. It never receives or stores your password. The email address is used to show you who you are signed in as, and to decide whether you are an administrator of the deployment.
What you configure
Your destinations, escalation chains and message templates. A destination is an address: an email address, a Slack channel, a Teams channel, or a webhook URL.
Your missives
The subject and body of each message you send, its deadline, every delivery attempt, and how each attempt ended — acknowledged, refused, timed out, or failed. If a person acknowledged it, Fluxmon records who and when. This record is the product: a missive that cannot be shown to have been answered has not been answered.
Credentials you connect
Fluxmon operates no mail relay and no chat app of its own, so it delivers through the ones you connect: an SMTP password, a Slack webhook URL, a Slack bot token, a Teams workflow URL. These are encrypted with AES-GCM under a key derived from the deployment's session secret, and are decrypted only in memory, only to send a message.
Why we are allowed to hold it
| Purpose | Lawful basis |
|---|---|
| Running your account, delivering your missives, keeping the receipt | Performance of the contract with you |
| Keeping the service secure, preventing abuse, fixing faults | Our legitimate interests |
| The feedback and waitlist entries you choose to submit | Your consent, which you may withdraw |
| Data about the people you message | Your instructions, with you as the controller |
Slack
If you install the Fluxmon app in a Slack workspace, Fluxmon stores the workspace's Slack identifier and name, the bot token Slack issues (encrypted, as above), and the Slack user identifier of whoever ran the install.
The app asks for three permissions and no others:
- chat:write and chat:write.public — to post a message to a channel, and to edit a message it posted when the missive is escalated, acknowledged or failed.
- commands — to receive the /fluxmon command.
Fluxmon does not read your messages. It holds no permission to read channel history, and asks for none. What it receives from Slack is limited to what a person sends it directly: the text of a /fluxmon command, or the fact that somebody pressed a button on a Fluxmon message. In either case Slack tells Fluxmon the workspace identifier, and the Slack user identifier and display name of the person who acted. That name is recorded against the missive, because "who acknowledged this" is the answer the product exists to give.
Disconnecting a workspace on the Backends page deletes the stored token and the workspace record. It does not uninstall the app from Slack — only somebody in that workspace can do that, in Slack.
Who else sees it
Fluxmon sells nothing to anybody and shows no advertising. Your data is passed on in exactly one circumstance: when a missive is delivered, its subject and body are sent to the destination you chose, through the provider that serves it — your mail relay, Slack, Microsoft, or a webhook endpoint you nominated. That is the delivery you asked for. Those providers handle that data under their own terms.
Administrators of this deployment can see aggregate counts and the feedback people submit. They do not have a view of your missives.
Where it is stored
On a single rented virtual server in Germany (Hetzner, Nuremberg), in a PostgreSQL database on that machine. Traffic to the site is encrypted with TLS.
When data leaves Europe
The database does not. Three things can still send data outside the EEA, and each of them is your choice rather than ours: signing in with GitHub or Google tells that provider you signed in, and connecting Slack or Teams as a backend necessarily sends the missive to them so they can deliver it. Those transfers rely on the EU–US Data Privacy Framework where the provider is certified under it, and otherwise on the European Commission's standard contractual clauses. To keep everything in the EEA, do not connect them.
How long it is kept
Plainly: until you delete it, or until you ask us to. Fluxmon runs no automatic deletion today. Deleting a destination, a chain or a backend removes it immediately. Missives and their delivery records stay, because they are the audit trail of who was told what and when.
To have your account and everything attached to it erased, write to privacy@fluxmon.com. Deleting an account deletes its destinations, chains, templates, backends, Slack installation, missives and delivery records.
Your rights
You can ask for a copy of what is held about you, ask for it to be corrected, or ask for it to be erased. Write to privacy@fluxmon.com. Most of it is also available to you directly through the API with your own key — see the front page.
You can also ask us to restrict what we do with it, object to processing we base on our legitimate interests, or have it handed to you in a portable form. We answer within a month. If you are unhappy with the answer you may complain to the data protection authority where you live or work — in Norway that is Datatilsynet, datatilsynet.no. We would rather you told us first.
Children
Fluxmon is a developer tool and is not directed at children. Do not create an account if you are under 16. If you believe a child has given us personal data, tell us and we will delete it.
Cookies
One cookie holds your signed-in session, and a second, short-lived one protects the sign-in redirect from being forged. There are no analytics cookies and no third-party cookies.
Changes
If this page changes in a way that affects what is collected or who sees it, the date at the top changes with it.
Questions: privacy@fluxmon.com.