Privacy
Who is responsible
Klemma is run by [company name], [registered address], registered as [company number and register]. This company decides what personal data is used and why (the "controller").
Questions and requests about your data: support@klemma.eu.
This website
This website sets no cookies and has no analytics. Its one form is the waiting list: see below.
The waiting list
Klemma is in beta, by invitation. When you join the waiting list we store your email address, when you joined, whether you confirmed it, and the plan you were looking at if you came from the pricing page (or picked one inside Klemma). We use it only to let you in when it is your turn and to write to you about the beta.
- We send one email with a link to confirm the address; an address that is not confirmed within 7 days is removed. Once confirmed, you get one email that says what happens next.
- When you are let in, we record that your address has beta access, who gave it and when, and email you a link to set your password.
- Every email has a link to leave the list; your address is removed at once. It is also removed when you delete your account.
- The links in these emails are stored only as hashes. A count of sign-ups per network address (as a hash) is kept until the next day, to stop abuse.
Like any website, the server that delivers these pages sees the network address of each request. [Whether the hosting provider keeps access logs, and for how long, to be confirmed once hosting is chosen.]
The demo
During the beta you get an account when we let you in from the waiting list: you set a password from the link in our email. This is what is stored, and why.
| What | Why |
|---|---|
| Your email address | To log you in, to keep your projects and credits yours, and to tell you once, at most once a day, when your credits run low. |
| Your password, only as a one-way hash (Argon2id): the password cannot be read back from it | To check it when you log in. We email you when it is changed. After many wrong passwords for your account, login pauses for a while and we tell you. |
| Links to set or reset your password, and sessions, as hashes only | To check such a link and to keep you logged in. The links and session values themselves are not stored. |
| Whether your address has beta access, who gave it and when, and when it ended if it did | So only the people we let in can log in. Deleted with your account. |
| Your projects: the designs, their history, the proposals and the notes in them | This is the service: you come back to your work. |
| Whether you finished or skipped the getting-started tour | So the tour does not start again every time you log in. |
| A one-way code made from your email address (a hash: the address cannot be read back from it), and for 30 days the same kind of code of the network address you first logged in from | So the free credits are given once per person, not once per mailbox alias or per new account. |
| Feature requests you send: the text, your reason if you give one, the project you were in, and the status and note we add | To decide what to build, and to show you what became of your request. Deleted with your account. |
| For each request to the agent: its kind (for example a new design or a question), the kinds of devices in what the agent proposed, whether you accepted it, how long it took and what it cost. Not the text of the request. | To see what Klemma is used for and where it falls short, to show you under Account what your credits went to, and, counted together over all accounts, to tell you what a request usually costs before you send it. Deleted with your account. |
| What you work in (machine building, panel building, energy, building installation or other), if you choose to say | To see which kinds of companies use Klemma. You can change or remove it under Account. |
| Whether you agreed to share how you use the demo | So we only collect usage details when you said yes. |
| A project's details for its drawings: project number, customer, description, and the names you enter as drawn, checked and approved by; the revisions you issue (draft or release, and how many check warnings and generic parts were still open) | To print them in the title block of every drawing and at the top of every export. Deleted with the project. |
| Production lines you hand to the workshop, and the email addresses of colleagues you invite to one. If you are invited: the notes you add there, with your email address | So invited colleagues can open that line and add notes, and so the project's owner sees who wrote each note. Removed with the project, when the owner takes the invitation back, or when the account is deleted. |
| If you invite a colleague: their email address, when you invited them, and whether they joined, made a design or took a paid plan. If you were invited: that your account came from that invitation | To send the colleague one email, to keep one invitation per person, and to give the credits the invitation earns. The colleague sees nothing of your account but your email address in the invitation. Removed when the inviting account is deleted; the invited colleague's own deletion only unlinks the account. |
| A drawing you import to start a project (the PDF as you uploaded it), and the text read from it with where each line stands and what each page is | To build and check the project from your drawing, and to show it beside the design. You confirm you may reuse the drawing when you upload it. Read by our own code on our server, not by the language model. Articles read from its parts list (manufacturer, order number, description) are kept as your custom parts, private to your account. The drawing and its text are kept until you remove the drawing from the project, and deleted with the project or your account. The custom parts made from it stay in your library after the drawing or the project is removed, until you delete them or your account. |
| Your company logo, if you upload one (a small PNG made from it in your browser) | To print it in the title block of your drawings and on the cover of the drawing package. Replaced or removed under Account; deleted with your account. |
| A credit record: credits granted and used, with the amount of language-model work each request took and which request it was | To show your balance, to list under Account what your credits went to, and to account for use. |
| If you take a paid plan: which Stripe customer, subscription and plan belong to your account | To give you the credits you paid for. Card details and invoices are held by Stripe, never by Klemma. |
| Your place on the waiting list, with the plan you picked if any (see The waiting list above) | To let you in, and to write to you when paid plans open. You can leave the list from any of its emails. |
| Parts you make: their description, ratings, terminals and where each value comes from | To use them in your designs. A part you share with everyone is shown to all users once it is reviewed, without your name. |
| A hash of your network address with a count of login requests, removed the next day | To stop abuse of the login. |
A datasheet you upload is sent to the language model to be read and is not stored by Klemma; only the part you save from it is kept. The same goes for a PDF or a picture of an idea you upload for the agent to design from: it is read and not stored; only the design you accept is kept. A drawing you import to start a new project is different: it is kept with that project, as described in the table. Your draft (the text blocks and lines you sketch) is kept with your project, like the design.
The conversation with the agent in a project (what you type, its answers, and notes such as a proposal accepted) is kept on the server with that project, so you can continue it on another device. It is deleted with the project or your account. The first line of a request is also kept as the title of the proposal it led to.
Cookies and browser storage
- One cookie,
klemma_session, keeps you logged in for up to 30 days or until you log out. It is needed for the demo to work and is not used for tracking. [That no consent banner is needed for this cookie, to be confirmed in legal review.] - Local storage in your browser remembers which project you had open and a copy of its conversation. It stays on your device and is cleared when you log out.
- Only if you agree (asked once at your first login, and changeable under Account): how you use the demo is sent to PostHog: which buttons you click, clicks repeated in frustration, which views you open and for how long, and recordings of the screen in which every text and every input is masked, so your designs, names and part numbers are not in them. It goes with a code for your account, never your email address. PostHog then keeps an identifier in your browser's local storage. Without your yes nothing is sent and nothing is stored for this.
There are no analytics and no advertising cookies.
Legal basis
The data above is used to provide the service you asked for when you made an account, and, for the abuse counters, because of our interest in keeping the service safe and affordable. [Wording of the legal bases to be confirmed in legal review.]
Who else handles your data
These companies process data for Klemma, each only for the purpose named.
| Who | What for | What they receive |
|---|---|---|
| [hosting provider], servers in [hosting region] | Running the website, the demo and the database | Everything stored, as listed above |
| Mailjet | Sending the waiting list emails, the emails to set or reset your password, the low-credits email, invitations to a colleague, and questions to support that the help assistant could not answer | Your email address and those emails; for an invitation, your colleague's email address; for a support question, the question and where in the demo you asked it |
| PostHog (PostHog Inc., data stored in the EU) | Usage analytics, only if you agreed | Clicks, views and time spent, and masked screen recordings, with a code for your account. Not your email address, not the text on screen. [Data processing agreement with PostHog and how long it keeps the data: to be confirmed.] |
| Anthropic | The language model behind the agent | What you type to the agent, the design you are working on, and the datasheets, PDFs and pictures you ask the agent to read. Not your email address. |
| Stripe | Payment for paid plans and extra credits | Your email address, and what you enter on Stripe's payment pages |
| GitHub (GitHub Inc.) | Our development work list, for feature requests we decide to build | The text of such a request, your reason if you gave one, and where in the demo you asked it, in a private repository. Not your email address or your name. It stays there as a work item when your account is deleted. |
Do not put personal data or confidential information about other people in your designs or in messages to the agent.
[Whether any of these process data outside the European Economic Area, and under which safeguards, to be confirmed from each provider's terms.]
Your data is not sold and not shared with anyone else, unless the law requires it.
How long it is kept
- Your account, projects and credit record: as long as you have the account. An account nobody has logged in to for [period for inactive accounts] is removed.
- After an account is deleted, copies in backups are gone after [backup retention].
- Records of payments: [retention of billing records], as accounting law requires.
- A drawing you import: until you remove it from its project, or delete the project or your account.
- Counts of login requests and waiting list sign-ups per network address: until the next day.
- Waiting list entries: until you leave the list, are let in and delete your account, or, if never confirmed, 7 days.
- The code made from your email address for the free credits: also after your account is deleted, so the free credits are not given twice. It contains nothing else and cannot be turned back into your address.
[Removing inactive accounts automatically is not built yet; until it is, this happens by hand.]
Your rights
You can ask for a copy of your data, have it corrected or deleted, object to its use or ask to limit it, and receive your data in a form you can take elsewhere. Write to support@klemma.eu. You can also delete your account yourself, under Account in the demo: your projects, chats, imported drawings, own parts, credit record and waiting-list entry are deleted with it at once (the code for the free credits stays, as described above).
You can also complain to the data protection authority of your country. [Name and address of the authority for the company's country.]
Changes
This page is updated when what the demo stores changes. In force from [date].