Data and privacy ​
CodeLotse Cloud processes the content of your repositories on behalf of your organisation. Quavon UG (haftungsbeschränkt) is your processor under the data processing agreement. This page summarises where the data lives, who else receives it, and how you take it with you or delete it.
Where your data lives ​
The service runs in one EU region, at the hosting provider netcup in Germany. The database, the job queue, backups, logs and the application all run there. There is no second region and no replication outside the EU.
Who receives data ​
| Recipient | Why | Data |
|---|---|---|
| netcup | Hosts the servers, the database and the backups (sub-processor) | Everything stored for your organisation |
| Your model provider | Runs the model calls with your key; your own processor, not a sub-processor of Quavon | The prompts and answers of the features you use |
| Your code host (GitHub) | You use it directly | What your installation of the GitHub App exposes |
| Mollie | Payments and invoices | Billing details, payment data and amounts |
| VIES (European Commission) | Checks your VAT ID | Country code and VAT ID |
Quavon sends owner confirmation and payment reminder emails from its own mail server in the EU. The current list of sub-processors is an annex of the DPA, at app.codelotse.com/legal/dpa.
The Cloud does not run your code: there are no sandbox runs. It sends no product telemetry. The public status page contains no data about any organisation.
Within your organisation, the same controls as in the self-hosted edition apply, for example the privacy settings of reviewer suggestions and the requests of individual people for access to or deletion of their data, which an administrator handles.
Export your data ​
On the Hosted service page, Download export gives you everything stored for the organisation as compressed JSON lines, one line per row, with a final line that counts the rows per table. Keys, tokens and other secrets are left out. If the final line is missing, the download was cut off; start it again.
Delete the organisation ​
On the Hosted service page, under Delete this organisation, type the organisation name to confirm and choose Delete organisation.
- At once: model keys and connection secrets are removed, processing stops and no renewal is charged.
- For 30 days: an administrator can choose Cancel deletion. The data is kept, but removed keys and connections must be set up again.
- After 30 days: the GitHub App is uninstalled and all data of the organisation is deleted.
Some records are kept after the deletion because the law or accountability requires them: invoices and billing details for the statutory retention period, and the audit log. Backups expire on their own schedule.
Uninstalling the GitHub App on GitHub does not delete the data by itself; delete the organisation here as well.