Last changed 24 Sept 2026

Privacy notice

What beform does with your data in this portal, and what you can ask for.

Written by beform, not by a lawyer

These pages describe what the software actually does. No lawyer has reviewed the wording, so read it as a plain account of the processing rather than as legal advice. Anything on it that matters to you is worth asking about at hi@beform.ai.

What this notice covers

app.beform.ai, the portal you sign in to, and nothing else. The beform website has its own notice for the website and its demo, and every public showroom has its own notice for the people who visit it.

Privacy notice on www.beform.ai

Who is responsible

crue GmbH, the company named in the imprint, decides why and how everything described here is processed, which makes it the controller for it under the Swiss Federal Act on Data Protection and under the GDPR. Write to hi@beform.ai about anything on this page.

What is yours and not beform's

The photographs, requests and contact details your own visitors leave in your showroom belong to you. You decide why they are collected and what happens next, so you are the controller for them and beform only processes them on your instructions. Your showroom has its own privacy page that tells your visitors so. This notice is about your account, not about them.

What is processed, and why

  • Your account

    Your email address, the name and picture you add if you add them, the language you work in and the role you hold. Without it there is no sign-in, and no way for your colleagues to see who changed what.

  • Signing in, and keeping the account safe

    The one-time codes beform sends you, a second factor if you set one up, and the sessions open in your browser. Sign-in attempts are counted for a short window so an account cannot be guessed at, and what is stored against that count is a keyed hash of the network address rather than the address.

  • Your company

    The name your company is set up with, its legal name, its billing address and country, its VAT number, the language and currency it works in, and who belongs to it in which role.

  • What you put into the portal

    Your brand settings, your areas and style directions, your catalogue, and the photographs you upload in Studio together with the visuals formed from them.

  • Billing

    What you booked, what you were charged and whether it was paid. The payment itself runs at Stripe, and beform never sees a card number.

  • What you signed

    For every agreement signed from your account: the exact text that was on the screen and its fingerprint, the name you typed, the signature you drew, your confirmed email address, the time, and a fingerprint of your address and browser. The address itself is never stored. This is what makes a signature provable afterwards.

  • What you write to beform

    The messages you send from the support screen, and anything you attach to them, so that somebody can answer.

  • The assistant panel

    If you type a question into the assistant, that question and the answer go to the model provider named below. Nothing is sent until you type something, and beform trains no model on it.

  • Assistant use

    When you ask the assistant in beform, or an assistant you connected reads your account, beform records who it was, when, which assistant, which tool and whether it worked, and for the assistant in beform the token counts the model reported. Not your questions, not the answers and not what was searched for. The owners and admins of your organization can see this for everyone in it, by name; everyone else sees only their own. beform receives daily counts without names. When an assistant is connected, or beform disconnects one, the person who connected it and the owners and admins are told by email.

  • Running the service

    A record of what happened in your organisation: who changed what and when, how much was rendered, and the faults the software ran into. This is what makes it possible to answer a question about the account and to notice something broken.

On what basis

Most of this is processed because the contract between your company and beform needs it, or because answering you before there is one does. Some of it, such as the counters that stop an account being guessed at and the record of what happened, rests on beform's own legitimate interest in running a service that works and can be accounted for. Billing records are kept because accounting law requires them. Where something rests on your consent, you are asked for it and you can take it back.

Who else sees it

beform sells nothing to anybody and shares nothing for advertising. These companies process data so that the product can run, each under a contract and only for beform:

  • Supabase, Inc.: the database, the file storage and the sign-in behind the whole product. The database and the files are in Zurich.

  • Cloudflare, Inc.: a weekly copy of the files, stored in the EU (Cloudflare R2) and locked against deletion for 30 days. The copy of a deleted file is removed within 90 days.

  • GitHub, Inc.: runs that weekly copy on its own servers, including in the USA. The files pass through while they are copied and are not kept there.

  • Vercel, Inc.: the hosting. The application and its server functions run in Frankfurt.

  • Resend: the email beform sends you.

  • Stripe: your card payments. Stripe decides for itself what it does with a card, so for that part it is not acting on beform's instructions.

  • OpenAI and Google: the image models that form a visual from a photograph. They receive the photograph and the instructions, and nothing about you.

  • OpenAI (gpt-4o-mini): the model behind the assistant panel. It receives what you type there, and nothing else.

Where it is

The database and the file storage run in Zurich, Switzerland. The application and its server functions run in Frankfurt, Germany. Email is sent from Ireland, and the email provider keeps its account and logs in the USA. The models of Google and OpenAI process what they receive on their own infrastructure, including in the USA. Files are also copied every week to a separate provider in the EU (Cloudflare R2), locked against deletion for 30 days. The copy of a deleted file is removed from there within 90 days.

How long it is kept

Your account and your company's records are kept while the account is open. Photographs and visits in your showroom follow the retention you set in the portal: a photograph from a visitor who never sent a request loses its file once that time is up. A request you put in the bin is removed for good thirty days later. Billing records are kept for as long as accounting law requires.

What you can ask for

You can ask what is held about you, have it corrected, have it deleted, have its processing restricted, object to processing that rests on a legitimate interest, and get a copy of what you gave in a form you can take elsewhere. Where something rests on your consent, you can take that back, which does not undo what was done before. Write to hi@beform.ai.

You can also complain to a data protection authority: in Switzerland the Federal Data Protection and Information Commissioner, and in the EU the authority where you live or work.

Cookies, and what the browser keeps

There is no analytics, no advertising and nothing that follows you around in this portal. What is kept in your browser is the product working:

  • The sign-in cookies Supabase sets. Without them you would be signed out on every page.

  • BEFORM_LOCALE, a cookie holding the language you chose, for a year.

  • beform_ref, a cookie holding the referral code somebody arrived on while an account is being opened, for thirty days.

  • beform.assistant.size, kept by your browser alone, remembering how large you left the assistant panel.

If this changes

The date at the top of this page is the day the wording last changed.