› I want powerful AI. My proprietary code must not become training data.
Zero Data Retention · Strong models. Clear conditions.
Your context does its job. Then model processing ends.
Lurus Code processes source code and request context with Zero Data Retention. The context is used to handle the request, not retained for later model use.
- → No training on customer data by Lurus or connected model providers.
- → ZDR applies by default to every offered model and provider route.
- → Choose the model route and review the provider and processing region.
ZDR concerns model processing, not local session history or account and billing records. Embeddings and external tools have separate data flows to review.
Use Claude as a model. Choose its provider route through Lurus.
› Our team needs to approve the data route before sharing repository context.
GDPR & processing routes · Strong models. Clear conditions.
Make the data route part of your model choice.
Choose a model with its provider and processing region in view. The DPA, privacy policy and relevant sub-processors give your reviewers the basis for assessing your use case.
- → EU-hosted and US/global model routes are identified separately.
- → ZDR and no training apply to every offered model route.
- → Review agent permissions and external integrations before rollout.
The published sub-processor annex lists EU/EEA routes. Contact our privacy team for the applicable documentation for US/global processing.
Use Claude as a model. Choose its provider route through Lurus.
› Which infrastructure assurance can our security team actually review?
ISO/IEC 27001 · Strong models. Clear conditions.
An information-security standard. A defined hosting scope.
The published hosting-infrastructure commitment states ISO/IEC 27001 certification. For your vendor review, ask for the relevant evidence and its applicable scope.
- → The assurance concerns hosting infrastructure.
- → Application controls and model-provider routes remain separate review areas.
- → Request the relevant scope and evidence before organizational approval.
This is not a claim that the Lurus Code application holds a separate product certification. This demo performs no audit or verification of a certificate.
› What does the C5 assurance cover — and what should we ask for?
C5 attestation · Strong models. Clear conditions.
Cloud-hosting assurance, with scope you can inspect.
The published infrastructure commitment states C5 attestation for the hosting environment. Its scope matters more than a badge: obtain the relevant evidence for your review.
- → C5 applies to the stated hosting-infrastructure assurance.
- → Review hosting, model processing and agent actions as distinct boundaries.
- → Ask the privacy team to coordinate the relevant infrastructure evidence.
Hosting attestation is not a separate certification of Lurus Code or a blanket attestation for all connected model providers. This is an explanation, not a live compliance test.