Security and data
Where your imagery goes
For whoever signs off before your team installs a plugin: what leaves QGIS, how we protect it, and the DPA to sign.
Last updated 8 October 2026
Read the full privacy policyWhat leaves QGIS
What each mode sends
The plugin checks your licence when QGIS starts, and asks before the first upload of imagery or project data.
Semi-Auto on your own machine
No imagery. The model runs on your CPU. The plugin still checks your licence and sends diagnostics.
AI Segmentation in the cloud
A Cloud AI click sends a small square of imagery around the point. An Automatic run sends the tiles of the zone you drew, the word you typed, up to 8 example boxes, the zone outline and its coordinates. The polygons you keep come back to us too.
AI Edit
The area you select, your prompt and any reference images, with the area's extent, coordinate system and basemap name. Generation runs on Google Vertex AI.
AI Agent
Your request, any attached image, your saved instructions, and a description of the open project: file path, extent, CRS, each layer's name, fields, feature count and extent, one sample row for the first eight layers, recent Processing runs and QGIS warnings. Layer contents and files stay on your computer.
What we never receive
- Your project file and your other layers.
- From AI Edit and AI Segmentation: layer names, file paths or the URL of your imagery source (the basemap field keeps only a provider name and host). AI Agent sends layer names and the project file path, as listed above.
- Imagery in the diagnostics. They carry errors, versions, operating system and features used, tied to your account, and one switch turns them off in all three plugins.
Security
Key security measures
Each line matches our code or our contracts, and changes when they do.
Data location
Database, files, AI Segmentation and AI Agent stay in the European Union: Paris for the database and files, Belgium for AI Segmentation, West Europe and the EU data zone for AI Agent. AI Edit generation runs on Google Vertex AI's global endpoint, under the EU-US Data Privacy Framework.
Encryption
TLS 1.2 or higher on every connection. Data at rest is encrypted by the provider (AES-256 on Supabase, Google Cloud and Azure).
Access
Only two of the three co-founders hold production access, with two-factor authentication on every provider console. No contractor, offshore support or shared account.
Deletion
You delete your account from the dashboard. It stays recoverable for 15 days, then every row, file and email contact is erased and the erasure is verified.
Data export
Your results already live in QGIS on your computer. Account and usage data are exported in JSON on request within 30 days.
Breach notification
A personal data breach is reported to the CNIL within 72 hours of discovery and to affected customers without undue delay.
Pro: your history, for as long as you choose
On Pro, only you see your history and nothing you send trains a model. AI Agent conversations are the exception: we keep them 30 days and our team may read them to fix failures, unless you choose 0 days. You choose how long the rest stays, or that no copy is written. Enterprise contracts can add zero data retention.
Data processing agreement
A DPA you can sign before paying
Pre-filled under Article 28(3) GDPR with TerraLab as processor. Complete the controller block, sign it and send it to our privacy contact. Its sub-processor list points to our sub-processors page, so it stays current without a new signature.
What we do not have
Ask us for these and the answer is no
We are a French company of three co-founders. We cannot provide:
- A SOC 2 report or an ISO 27001 certificate.
- An on-premise or private-cloud install of the plugins: cloud detection and generation run on our servers. Semi-Auto is the free offline path; detection on your own servers is a separate custom project.
- Single sign-on: you sign in with an email link.
- A public status page, yet.
Who to write to
Questions or a security questionnaire
Write to yvann.barbot@terra-lab.ai and a founder answers in writing. We fill in your questionnaire, and can sign your own DPA form instead of ours. We have no data protection officer, which the GDPR does not require at our size, so this address is the controller contact.
yvann.barbot@terra-lab.aiWho you are contracting with
- TerraLab, société par actions simplifiée, share capital 1,000 euros
- SIREN 104 501 861, RCS Paris B 104 501 861
- Intra-EU VAT FR43104501861
- 173 rue de Courcelles, 75017 Paris, France
- President and publication director: Yvann Barbot