[ Legal ](https://clemant.co/legal) Privacy statement ================= What Clemant keeps about you, why it may, who sees it, how long it stays and what you can ask. Draft. Not yet reviewed by counsel and not in force. 02 For everyone who uses Clemant ----------------------------- Document 1 of 2 Clemant is where people join a group claim against a company. This statement says what Clemant keeps about you, why it may, who sees it, how long it stays and what you can ask. It applies to the site, the emails Clemant sends and your own pages under [My claims](https://clemant.co/my). Who we are ---------- Clemant is run for Steddle B.V., which is being incorporated in the Netherlands. Steddle is the controller of your account and of what you tell Clemant. Write to about anything in this statement. To be completed: the entity that acts for Steddle B.V. until it is incorporated, with its Chamber of Commerce number and address. When a foundation or law firm takes a claim on and you say yes to it, that party becomes the controller of its own register of the people in the claim, and Steddle keeps that register for it under its instructions. Steddle stays the controller of your account and of what you told Clemant before that, so for those you deal with Steddle. The claim's page names the party, and you are asked before anything goes to it. What we hold, and why we may ---------------------------- - **Your account.** Your email address, your name if you give it, your language and, if you sign in with a Steddle account, its reference. We need these to let you sign in and to tell you about the claims you join (art. 6(1)(b) GDPR). - **Joining a claim.** That you joined, when, the country you live in and the words that were on the screen when you did. Joining is your own declaration that it happened to you too. We keep it to run the claim and to show, if a court asks, how the group came together (art. 6(1)(b) and (f) GDPR). - **What happened to you.** The answers you give to a claim's questions, the documents you add and what you write in the chat. You decide when to add them. We use them to check your answers are complete and to prepare the claim (art. 6(1)(b) and (f) GDPR). - **A claim you start.** The company you name, what happened and who it happened to. A person at Clemant reads it before anyone else sees it. - **News about a claim.** Only if you tick the box for it. That is your consent, and you can take it back with the link in every email (art. 6(1)(a) GDPR). - **Proof of what you agreed to.** Every declaration and consent goes into a ledger that cannot be changed afterwards: what, when, the exact words shown, and the network address and browser it came from. We keep it on our legitimate interest in being able to prove what you agreed to (art. 6(1)(f) GDPR), which is what the GDPR requires of us (art. 5(2) and 7(1)). - **Signing in.** The links we email you, and while you are signed in, the network address and browser of your session. We need them to keep your account yours (art. 6(1)(f) GDPR). Clemant sets no tracking or advertising cookies and uses no analytics. The cookies it sets keep you signed in and remember your language. What becomes public ------------------- A claim shows how many people joined, never who: the count, the countries and how many joined each week, counted from a copy that holds no name, address or answer. A claim you start becomes public only after a person at Clemant has read it, and it names a company, never you. Who else sees it ---------------- - **People at Clemant** who review claims and help the people in them, as far as their work needs. - **A foundation or law firm taking a claim on**, only after you say yes to that party. You can take that back. - **Companies that work for us**: the provider that hosts Clemant, the provider that stores the documents you add, and Resend, which delivers our email. They may use your details only to do that work for us. Resend delivers our email from the United States, so your email address and the text of our messages go there. - **An AI model**, where a claim's chat is run by one: what you type in the chat goes to the model's provider, with the claim's questions and a reference number for your registration, to write the next question. Your name, your email address and the answers you already gave are not sent. The model writes questions; it takes no decision about you, and no decision about your claim is made by software (art. 22 GDPR). - **Authorities**, where the law obliges us. To be completed: the hosting and storage providers by name and where they keep data, and the safeguard Clemant relies on for the transfer to Resend (art. 46 GDPR). Email from us ------------- We email you the links you ask for to join, start a claim or sign in, and once a reminder when a claim you joined is waiting for your answers. News about a claim comes only if you asked for it, and every news email has a link to stop it. If an email bounces or is marked as spam, we keep a one-way code made from that address so that we do not write to it again. The code still counts as your data, and we cannot read the address back from it. How long we keep it ------------------- - Sign-in links are deleted a day after they expire. - Your account and what you told us stay until you leave Clemant or ask us to erase them. - When you erase your account, we delete your name, your email address, your answers, your documents and what you wrote in the chat, and the network address and browser on your declarations and consents. - While a claim you joined is running, we keep the record that you joined, without your contact details, because the claim may need it in court (art. 17(3)(e) GDPR). To be completed: how long the ledger rows about a claim stay after it ends, and when an account nobody signs in to is deleted. Your rights ----------- You can see and download everything Clemant holds about you, and ask us to erase it, on [Privacy and my data](https://clemant.co/my/privacy). While a claim you joined is running we keep the record that you joined, without your contact details; everything else goes. You can leave a claim at any time, and stop news emails with one link. You can also ask us to correct what is wrong, to limit what we do with your details, or object to how we use them: write to and we answer within a month. If you think we handle your details wrongly, you can complain to the Autoriteit Persoonsgegevens. Security -------- Who you are is kept in a database of its own, apart from the claims. Your name, your email address, your answers and what you write in the chat are encrypted, and the documents you add are checked for viruses before anyone opens them. The public numbers come from a copy that holds no personal details. If something goes wrong that puts your details at risk, we tell the Autoriteit Persoonsgegevens and, where it matters to you, you. ### Your Steddle account You sign in to Clemant with a Steddle account: one account for every Steddle product, kept at [account.steddle.com](https://account.steddle.com). It holds your name, your email address, the language you chose, the public key of any passkey you register, and which Steddle products you have signed in to, with when you first and last did. There is no password. When you sign in, your Steddle account tells Clemant your name, email address and language, and whether you signed in with a passkey or a link by email, identified by reference and never the credential itself. Clemant keeps its own copy of those details. It does not learn which other Steddle products you use. In your Steddle account you can change your name or email address, and the change reaches every product you have signed in to. You can leave Clemant, which deletes your account here; sign out of every product at once; or delete your Steddle account, which deletes your account in every product you have signed in to. What stays of your use of Clemant after you leave is described in the rest of this policy. Changes ------- When this statement changes, the new version is on this page. When a change affects what you agreed to, we ask you again. [ Every document ](https://clemant.co/legal)Questions: