Privacy

What this site processes, and why.

Last updated 6 October 2026

Beanome is a product of Oneirico. This notice covers the public website at beanome.com and the Beanome sign-up page at signup.beanome.com, where you can create a Beanome account and workspace yourself. The Beanome application at app.beanome.com is a separate service. Pilot customers agree its terms with us; terms for accounts made through sign-up will be published, and shown at sign-up, before sign-up opens to the public. What you do inside the application — the networks you model, the questions you ask Isaac — is not covered by this notice: the application has its own.

The short version: beanome.com sets no cookies, loads no third-party fonts or trackers, and the only personal data it handles is what you type into the pilot-request form. The sign-up page sets one cookie, strictly necessary to hold your sign-up together, and handles what you type into it to create your account.

Who is responsible

The controller is Oneirico B.V., Herinkhave 18, 5655 JL Eindhoven, the Netherlands. For anything in this notice, write to privacy@beanome.com.

What is processed

WhatDataPurpose & legal basisKept
Pilot-request formName, business email, company, your message, phone and job title if you give them, plus the IP address and browser string of the submissionTo reply to your request and set up a pilot — steps taken at your request before a contract (GDPR art. 6(1)(b)); the form records that you agreed to this notice. IP and browser string are kept for abuse handling (art. 6(1)(f)). No marketing emails: we only write to you about your request.Filed as a ticket in a private issue tracker (GitHub). Deleted when the request is closed, at the latest 12 months after the last contact.
Sign-up page: your detailsFirst and last name, work email address, company, phone and job title if you give them, and the version of this notice you agreed to and whenTo create the Beanome account and workspace you ask for — steps taken at your request before a contract (art. 6(1)(b)). The company becomes your workspace’s name; the domain of your email address (the part after the @) is what the workspace claims. The page records which version of this notice you agreed to — the date at the top — and when.Held on the sign-up server only while you sign up, and at most one hour from when you opened the page. Your name, phone and job title leave it as soon as your account is made; the rest is deleted when the sign-up ends or the hour is up.
Sign-up page: one-time codeYour email address, a six-digit code and the time it expiresTo prove that you receive mail at the address, and so belong to its domain, before anything is created (art. 6(1)(b)). Sent from no-reply@beanome.com through Azure Communication Services Email (Microsoft), which stores its data in Europe. The email carries the code and its expiry and no link. The code works once, only in the browser that asked for it, for 10 minutes; five wrong tries void it.The code is never stored — only a keyed hash of it, deleted after it expires. The address and the code wait in an outbox only until the email is sent, and are deleted then.
Sign-up page: session cookieOne cookie, __Host-signup, holding a random value; on our side only a hash of it is keptTo keep the steps of one sign-up together in one browser, and to make a code typed into another browser fail. Strictly necessary for the sign-up you asked for (no consent required). Set by signup.beanome.com only, never by beanome.com.Until you close the browser, and cleared when the sign-up ends. The server forgets it after one hour.
Sign-up page: limits and recordsYour network (the IP address cut to its first three parts, or its first 56 bits for IPv6), the domain of your email address, a keyed hash of the address, and what happened at each step: code sent, refused, proven, account createdTo limit how many codes and workspaces one address, domain or network can ask for, to notice abuse, and to keep a record of how each account was made (art. 6(1)(f)). Your address is never in these records in clear: only as a keyed hash, which cannot be turned back into the address without a secret key held apart from the data.Limit counters: until their window ends, at most 24 hours. Records of refused or unfinished sign-ups: 90 days. Records of completed sign-ups: 2 years. Deleted by a daily job; database backups keep a deleted record for about 35 more days.
Your Beanome account (sign-in)Email address (also your user name), first and last name, phone and job title if you gave them, your password, and the authenticator app you set up at your first sign-inTo let you sign in to Beanome (art. 6(1)(b)). The account is made in Beanome’s own realm of our sign-in service (Keycloak), only after your address is proven. Your password passes through the sign-up service once, to the sign-in service; the sign-up service never stores or logs it. Every later sign-in asks for your password and a code from your authenticator app.For as long as you have the account. To have it deleted, write to privacy@beanome.com.
Your Beanome workspaceThe workspace name (the company you gave), your email domain, your account’s identifier and email address, and the version of this notice you agreed to and whenTo create your workspace with you as its owner, and to tie your email domain to it, so that one company has one workspace (art. 6(1)(b)).For as long as the workspace exists. To have it deleted, its owner writes to privacy@beanome.com.
Human check (Cloudflare Turnstile)IP address, browser characteristics, a short-lived tokenTo tell a person from a bot before the pilot-request form is accepted, and before the sign-up page sends a code — on its first page and on every request for a new code. Strictly necessary for the service you asked for (no consent required). Our server checks the token with Cloudflare, passing your IP address with it. Processed by Cloudflare under our data-processing agreement.Token minutes; Cloudflare’s own logs per its policy.
Service logs (Grafana Cloud)What the sign-up and sign-in services and the network in front of them write to their logs: the time, the address requested and your browser string; when a sign-in fails, also the user name tried (your email address) and the network address it came fromTo run the services, find faults and notice abuse (art. 6(1)(f)). The sign-up service itself never writes your IP address or email address to a log.14 days.
Hosting (Cloudflare)IP address, requested URL, browser string, in server logsTo deliver the site and the sign-up page and defend them against abuse (art. 6(1)(f)). Cloudflare Pages serves beanome.com; every request to the sign-up page reaches us through Cloudflare’s network.Cloudflare’s standard log retention.
Traffic statistics (Cloudflare Web Analytics)Page URL, referrer, browser and country, aggregatedTo know which pages are read. Cookieless; no fingerprinting, no identifier is stored on your device, and nothing is shared with advertisers (art. 6(1)(f)).Aggregated only.
Appearance preferenceThe value light or dark in your browser’s local storageTo remember your choice of light or dark appearance. Stays in your browser; never sent to us. Strictly necessary for a setting you chose.Until you clear site data or switch back to “system”.

Signing up for Beanome

Signing up on signup.beanome.com takes four steps: you give your name, work email address and company (and, if you like, your phone and job title) and confirm that you have read this notice; we email you a code; you type it in; you name your workspace and choose a password. Your account and workspace are made only at the last step. If you stop part-way, neither exists — only the records in the table above, which hold your address as a keyed hash, never in clear.

A work address is needed. Addresses at free-mail and disposable-mail providers are refused before any email is sent. Nothing about your address is looked up — whether it already has an account, whether your company already uses Beanome — until you have typed the code.

Your email domain stands for your company. A new workspace claims the domain of its owner’s address, so a company has one workspace. If your domain is already claimed, you are told that your company already uses Beanome — never the workspace’s name or who is in it — and you may ask to join. A join request passes your email address to that workspace’s administrators, who decide; nothing is granted until they do. If you already have an account, you are sent to sign in instead.

Where it is kept. The sign-up service and its own database, the sign-in service (Keycloak) and the Beanome application with its database run on Oneirico’s Kubernetes cluster in Microsoft Azure’s Germany West Central region (Frankfurt), and their backups are kept in the same region. The sign-up database serves the sign-up and nothing else. Your account is in Beanome’s own realm of the sign-in service, apart from any other product’s.

The code email. It comes from no-reply@beanome.com, an address that only sends: replies are not read. For anything about your data, write to privacy@beanome.com. The sign-up service emails you only the codes you ask for.

What is not done

Where the data goes

Cloudflare, Inc. hosts the site, carries the traffic to the sign-up page, runs the human check and the traffic statistics. GitHub, Inc. stores pilot requests as private issues. Both may process data in the United States; transfers rest on the EU–US Data Privacy Framework and the Standard Contractual Clauses in their agreements with us.

Microsoft runs, on Azure in Germany West Central, the cluster that holds the sign-up service, your Beanome account and the Beanome application, and sends the sign-up code through Azure Communication Services Email, which stores its data in Europe. Microsoft may reach data from outside the EU to support and secure its services; such transfers rest on the EU–US Data Privacy Framework and the Standard Contractual Clauses in Microsoft’s data protection addendum.

Grafana Labs keeps the service logs in its Grafana Cloud region in Germany (Frankfurt). As a US company it may reach them from the United States; that rests on the EU–US Data Privacy Framework, under which Grafana Labs is certified, and the Standard Contractual Clauses in its data-processing agreement with us.

Your rights

Under the GDPR you may ask for access to, correction or deletion of your data, ask us to restrict or stop processing, receive a copy in a portable format, and object to processing based on legitimate interest. Write to privacy@beanome.com; we reply within a month. You may also complain to the supervisory authority in your country — ours is the Dutch Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl).

Changes

When this notice changes, the date at the top changes with it. Material changes are announced on this page.