Langrove

Data processing agreement

This agreement is part of our terms of service. It applies to personal information we process for your company when you use Langrove, and you accept it when you accept the terms. Last updated 11 October 2026.

A. Key terms

Sub-processors

You authorise us to use these sub-processors. Each is bound by data protection terms at least as protective as this agreement.

AI providers and other services you connect to your apps yourself, such as a model provider your apps' agents call with your own key, are your choice and act for you, not for us.

B. Legal terms

1. Purpose and scope

• This agreement meets the requirements of section 21 of South Africa's Protection of Personal Information Act (POPIA) and, where they apply, Article 28 of the EU GDPR and the UK GDPR.
• Terms defined in those laws have the same meaning here. If this agreement and the terms of service conflict on personal information, this agreement wins.

2. Your instructions

• We process personal information only on your documented instructions, which are the terms, this agreement, and what you and your users do in Langrove, unless the law requires otherwise. If it does, we'll tell you first unless the law forbids that.
• We'll tell you if we think an instruction breaks data protection law.
• We use the information only for the purpose in section A, and keep it confidential.

3. Security

• We keep appropriate technical and organisational measures in place for the risk involved, including those in section C, and may improve them as long as overall protection doesn't fall.
• Everyone we authorise to process the information is bound to keep it confidential.

4. Sub-processors

• You give general authorisation for the sub-processors listed above.
• We'll tell you at least 30 days before we add or replace one, by email or in the console. If you object on reasonable data protection grounds and we can't resolve it, you may end the agreement before the change, and pay only for the time before it ends.
• We stay responsible to you for what our sub-processors do.

5. Transfers abroad

• Where personal information leaves South Africa, the EU or the UK, we transfer it only as POPIA (sections 72 and 73) and the GDPR allow: to a country with adequate protection, or under binding terms such as the EU standard contractual clauses and the UK addendum, with any further measures they call for.

6. Helping you with people's rights

• Your apps and the console let you find, correct and delete the information they hold. Where that isn't enough, we'll help you answer requests from people exercising their rights.
• If someone asks us directly about information we process for you, we'll pass the request to you and won't answer it ourselves unless you tell us to or the law requires it.

7. Security breaches

• If we become aware of a breach affecting personal information we process for you, we'll tell you without undue delay.
• We'll give you what we know and you need to meet your own duties, including to the Information Regulator and the people affected: what happened, what information and how many people it affects, the likely consequences, and what we've done and will do about it. Where we don't have everything at once, we'll send it as we learn it.
• We'll take reasonable steps to contain the breach and limit its harm, and work with you on investigating it.

8. Impact assessments

• We'll give you reasonable help with data protection impact assessments and consultations with regulators, as far as they concern our processing.

9. At the end

• When the terms end, information we process for you is returned or deleted as the terms set out, and in any case deleted within 30 days of the end of any handover period, unless the law requires us to keep it.
• Information in your own AWS account stays there, under your control; we only stop having access to it.

10. Showing we comply

• On request, we'll give you the information you reasonably need to check that we meet this agreement, including answering reasonable security questionnaires.
• If that isn't enough, you or an independent auditor bound to confidentiality may audit our compliance once a year, with 30 days' notice, during business hours, limited to what this agreement covers, and without disrupting our work or other customers. A breach or a regulator's request allows more. Each side pays its own costs.

11. Liability and law

• The limits of liability in the terms of service apply to this agreement, except where the law doesn't allow them to.
• This agreement is governed by the same law, and disputes go to the same courts, as the terms of service.

C. Security measures

• Separation: each customer's apps run in their own AWS account, with their own database and storage. Test data and live data are kept apart in every app.
• Our access to your account: one AWS role, which can't change permissions, can store secrets but not read them back, and is logged in your account by AWS. Removing it removes our access.
• Encryption: connections use TLS. Stored files and databases are encrypted at rest by AWS. Secrets are kept in AWS Parameter Store, encrypted with AWS KMS. Tokens for services your apps connect to are also sealed with AES-256 under a key only your runtime holds.
• Sign-in: no passwords. People sign in with an emailed link, Google, Microsoft or a passkey, and every sign-in link works once.
• Least privilege: each part of the runtime has only the permissions its job needs. The parts that run your apps' code can't read your secrets store.
• Changes: only a person can put a release live, and recent releases are kept so one can be rolled back.
• Protection at the edge: requests reach your apps only through AWS CloudFront with rate limiting, and attempts to go around it are refused and recorded.
• Logs: the front door's request logs are kept for 30 days, in the account the apps run in.
• People: access to production systems is limited to the people who run Langrove, and each is bound to confidentiality.