Langrove

Privacy policy

This covers the Langrove console and service. Our website, langrove.build, has its own notice about visits to it. Apps that companies build on Langrove belong to those companies: if you use one, that company decides how your data is used. Last updated 11 October 2026.

Who we are

ToTheMoon (Pty) Ltd, a company registered in South Africa (no. 2024/203943/07), runs Langrove and decides how this data is used.
Our Information Officer, under South Africa's privacy law, is Jacques Winterbach. Write to privacy@tothemoon.build about anything on this page.
The agreement for using Langrove is in our terms of service. How we handle personal information on a company's behalf is in our data processing agreement.

When you sign in and ask for access

What we collect: your work email address, your name and company if you give them, and a record of when you sign in.
Why: to create your account, decide whether to approve your company, and contact you about setting it up. Our legal basis: you asked us to take these steps before any agreement with us.
Giving us these details is up to you, but without a work email we can't set up access.
How long: while you have an account. If your company isn't approved, or you don't go ahead, we delete your details after 12 months, or sooner if you ask.
If you email us, we use your message and address to reply, and keep them as long as dealing with it needs.

When your company uses Langrove

Your account: your work email, your name, the companies and projects you belong to and your role in each, how you signed in (an email link, Google, Microsoft or a passkey) and when, and which version of our terms you accepted and when. For a passkey we keep only its public key, never anything that could sign in as you.
What you build: the apps, settings and changes you and your AI tools make in the console, and when each was made, so your team can see the history and undo a change.
The console's AI assistant: when you ask it something, your message and the parts of your project it needs go to Google's Gemini service to produce the answer.
AI tools you connect, such as Claude or ChatGPT, receive what they read through Langrove under your own account with that provider, and its privacy terms apply.
Your apps' data lives in the AWS account your apps run in: your company's own, or one we create and run for your company. Your company decides what goes in and why. For that data we act only on your company's instructions, as its operator (its processor, under the GDPR). We open it to run what your company built, to apply changes it asks for, and when your team looks at it in the console.
Sign-in emails for your apps: if one of your company's apps signs people in with an emailed link or code and has no sender of its own, we send that email for it. The address and the message pass through our servers and Amazon's email service to be sent.
Why: to provide Langrove under our agreement with your company, and to keep it secure and working. Our legal basis is that agreement, and our legitimate interest in running a safe service.
How long: while your company uses Langrove. When it leaves, we delete your account and its records within 30 days, unless the law requires us to keep something. What happens to your company's apps and data is set out in our terms.

Cookies and browser storage

The console's cookies keep you signed in and protect its forms against forgery. Sign-in can't work without them, so they need no consent. They last until you sign out or they expire.
Interface choices stay on your device. The console remembers things like pinned projects and panel sizes in your browser's storage.
A random id for each open tab is sent with the console's requests, so it can tell your tabs apart. It identifies the tab, not you, and is forgotten when the tab closes.
We don't use advertising or analytics cookies in the console.

Our hosting and email providers: Amazon Web Services, to run the console and the AWS accounts we run for companies, to send emails, and to run the AI models some Langrove features use; and Laravel Vapor, which deploys our servers on Amazon Web Services. They act only on our instructions.
Google, if you sign in with Google or use the console's AI assistant.
Microsoft, if you sign in with Microsoft.
The full list of these providers, what each does and where, is in our data processing agreement. We'll update it before we add one.
Where it's kept: in Europe, which is outside South Africa and protected by the GDPR. Our servers, and the AWS accounts we run for companies, are in Ireland; one search feature uses an AI model in Frankfurt. Our providers may also handle it elsewhere, including in the United States. When they do, they're either certified under the EU-US Data Privacy Framework or bound by contract terms the EU and UK approve (standard contractual clauses).
We don't sell your data, use it for advertising, or make decisions about you by automated means alone.

If something goes wrong

We protect your information with the measures in our data processing agreement.
If a security breach affects your personal information, we'll tell South Africa's Information Regulator and you as soon as we reasonably can, as the law requires, with what happened and what you can do. Where we hold it for your company, we tell your company first, so it can tell you.

Your rights

You can ask for a copy of your data, and ask us to correct it, delete it, limit how we use it, or hand it to you in a form you can take elsewhere.
You can object to anything we do because of our legitimate interests. You can also withdraw your consent at any time.
Write to privacy@tothemoon.build and we'll answer within one month.
You can also complain to a data protection authority. Ours is South Africa's Information Regulator, at POPIAComplaints@inforegulator.org.za. If you live in the UK or EU, you can also complain to the authority there.
These rights come from South Africa's privacy law (POPIA) and, if you're in the UK or EU, the GDPR.
When what we collect changes, we update this page and the date at the top.