Who we are
Umlout is operated by umlout.com. We decide what personal data the service collects and why, which under UK and EU data protection law makes us the data controller for it. Reach us at legal@umlout.com.
What we collect
Account details
When you register with an email address we store that address, the username you choose, and a one-way bcrypt hash of your password — never the password itself. If you sign in with Google instead, we store your Google account identifier and the email address Google confirms for it, and no password exists for that account at all. You can add a first name, last name and profile picture; the picture is stored with your account and served to collaborators who share a project with you.
What you create
Boards, projects, objects, relations and comments you make, together with who owns them and who they are shared with. This is content you control: it is stored so the service can show it back to you and to the people you share it with. When you share a project with an email address that has no Umlout account yet, we store that address with the project, so the person gets access when they sign up with it.
Technical records
Our servers write an access log for each request — a timestamp, the route, the response status, a request identifier, the network address the request came from, the page that linked to it and the name your browser gives itself (its user agent). From that log we count, on our own server, how many different visitors opened the pages of this site in the last day, a visitor being one network address with one browser name; only the count leaves the server, and counting sets no cookie. We keep a single "last seen" timestamp per account so we can count how many people use the service. While you have a board open we hold a short-lived presence record, so collaborators can see each other's cursors. We also count requests per address to stop abuse of the sign-in and signup endpoints.
Two further records are kept for security. Every attempt to sign in, successful or not, is recorded with the email address it was made for, the outcome, the network address it came from and the browser's name, so that an attack on an account can be traced. Every time a browser opens a live connection to a board or a project, we record your account identifier (or an anonymous one, for a visitor without an account), the network address and the browser's name, so we can tell real visitors from a page reconnecting in a loop.
Things you send us
If you use the feedback form we store your message, your account identifier, name and email address with it, and, when you attach one, the screenshot. If you ask to be notified about a paid plan, we store the email address you give for that.
Payments
If you buy the Regular plan, the purchase is made from Paddle, which collects your payment details, billing address and tax information itself — we never receive a card number. Paddle tells us what we need to give you the plan: your Paddle customer and subscription identifiers, the subscription's status and renewal date, and the email address you paid with. We store those with your account.
API keys
Keys you generate for the MCP server are stored only as a keyed hash plus the first few characters, which is why we can show you which key is which but can never show you a key again after it is created.
Why we hold it
Account details and content are held to provide the service you asked for — without them there is no account and nothing to show you. Technical records are held for a narrower reason: keeping the service available, diagnosing faults, preventing abuse, and knowing how many people visit this site. We do not sell personal data, and we do not use your boards to train machine-learning models.
If you are in the UK or the EEA: the first is processing necessary to perform our contract with you, the second is our legitimate interest in running a secure service and knowing how many people visit it, and the analytics described below rely on your consent.
Who else sees it
We use a small number of outside services, and each one sees only what it needs:
- Google — if you choose to sign in with Google, Google tells us your account identifier, email address and name. Google's own privacy policy governs what Google does with that sign-in. Every font on this site and on a board is served from our own servers, so neither reading these pages nor opening a board tells Google anything. Google Tag Manager, which we use for analytics, is different: it loads only if you accept it, and it is the one thing on this page you can switch off. Our email is hosted by Google Workspace, so a message you send to one of our addresses is stored there.
- DigitalOcean — rents us the servers Umlout runs on. Our database, the files you upload and the access log are stored on those servers; we administer them ourselves, and DigitalOcean does not use what is on them.
- Paddle — Paddle.com is the merchant of record for the Regular plan: it sells the subscription, takes the payment and handles tax and refunds. It receives what you enter in its checkout, and from us the identifier of your Umlout account so the payment can be matched to it. Paddle's own privacy notice governs what it does with that.
- Mailgun — sends verification emails. It receives your email address and the message.
- Grafana Cloud — stores our application logs and metrics. Those logs include the technical records described above, which means request identifiers, network addresses and, for signed-in requests, your account identifier.
We disclose data to anyone else only where the law requires it.
Cookies and local storage
Your session token is not a cookie: it is kept in your browser's local storage, and clearing site data or signing out removes it. The same goes for your answer to the cookie banner — it is a single value in local storage, not a cookie.
Signing in with Google sets one cookie, umlout_oauth. It holds a random value that ties Google's answer to the browser that asked for it, so nobody can sign you in to an account of theirs. It is sent only to our sign-in address, lives at most twelve minutes and is deleted as soon as the sign-in completes. Because the sign-in cannot work without it, it does not need your consent. Signing in with an email address sets no cookie.
Apart from that cookie, analytics is the only thing here that sets cookies. We use Google Tag Manager to see which parts of Umlout get used, and it does not load at all unless you accept it. Decline and no analytics script is ever fetched; nothing about Umlout stops working either way.
You can change your mind at any time, right here:
Turning analytics off stops the script from loading again, but it cannot delete cookies Google has already set — no site can remove another one's cookies. Clear those through your browser's site-data settings.
How long we keep it
Account details, content and the subscription record are kept until the account is deleted; Paddle keeps its own record of a purchase for as long as tax law requires it to. An email address a project is shared with is kept with the project until it is removed from the project's access list. Feedback messages, their screenshots and the addresses given to be notified about a paid plan are kept until you ask us to delete them. Everything else is deleted automatically:
- The "last seen" timestamp is discarded after 24 hours.
- Presence records disappear within a minute of a board being closed.
- Abuse counters expire with their time window, at most an hour.
- Sign-in handshake records expire within ten minutes, and are deleted the moment they are used.
- Records of sign-in attempts are deleted after 90 days.
- Records of live connections to boards and projects are deleted after 30 days.
- The access log on our own servers is deleted after at most 15 days.
- Logs held in Grafana Cloud follow that service's retention for our plan.
Your choices
You can see and change your name, email address and picture on your profile page, and revoke API keys there at any time.
For a copy of your data, or to have your account and its content deleted, write to legal@umlout.com. Deletion is not yet a button you can press yourself, so we handle these by hand — we will confirm when it is done. If you are in the UK or the EEA you also have the right to object to processing, to restrict it, and to complain to your data protection authority.
How we protect it
Traffic to Umlout is encrypted in transit. Passwords are stored as bcrypt hashes and API keys as keyed hashes, so neither can be read back out of our database. Sign-in handshakes are single-use and time-limited, and the token that ends a social sign-in is never placed anywhere a server or proxy would log it.
No service can promise perfect security, and we do not. If you find a weakness, we would rather hear about it than not — write to support@umlout.com.
Children
Umlout is not directed at children and is not intended for anyone under 16. If you believe a child has given us personal data, tell us and we will remove it.
Changes to this policy
When this policy changes we update the date at the top of the page. If a change materially affects how we handle your data, we will tell account holders by email rather than relying on you to notice.
Contact
Write to legal@umlout.com for anything about this policy or the data we hold about you. We answer from the same address, so replies stay on the same thread.