Terms of Use

Data-processing terms version 2026-11-10. Commercial terms are not yet finalised — see §5.

1. What Kadense does with your source code

These are the terms shown and accepted at sign-up, reproduced here verbatim from the same source, so this page and that form cannot say different things.

• Your code is sent to Anthropic to be assessed. The assessment is performed by Claude. Regions of your uploaded source code, and the text of any supporting documents you attach, are transmitted to Anthropic over TLS for that purpose. Where a run sent your code is recorded on that run's own page.
• It is analysed in a single-use container in Microsoft Azure. We create a disposable container in Microsoft Azure (South Africa North region), place a copy of your uploaded files in storage attached to it, and permit it to reach Anthropic and nothing else. The container and that copy are destroyed when the run ends, and we verify and log the destruction. Microsoft Azure is a sub-processor for the duration of a run, and your code does not leave South Africa except to reach Anthropic.
• Anthropic does not train on it. Inputs and outputs are not used to train models. The retention and training terms that apply are those of the Anthropic plan this deployment runs on, and the posture in force for your assessment is recorded with that run. Kadense does not grant any additional rights over your code.
• Kadense does not keep your source code. The copy we extract to analyse is destroyed as soon as the run ends, and the deletion is logged. Your uploaded archive is held for up to 72 hours so a failed run can be retried, then deleted. After that we retain only the report — scores, findings and the evidence quotes supporting them — envelope-encrypted at rest. We never sell or share your data.
• Only upload code you are entitled to have assessed. You confirm you own this codebase or are authorised to submit it for security assessment, and that you may lawfully disclose it to the third-party processors named above for that purpose.

2. Retention

• The copy of your code we extract in order to analyse it is destroyed when the run ends, and the deletion is logged.
• Your uploaded archive is retained for up to 72 hours, so that a failed or interrupted run can be retried, and is then deleted.
• We retain the report of a run — scores, findings, and the evidence quotes supporting them — envelope-encrypted at rest. Reports are retained for 90 days by default.
• We retain account records and a tamper-evident audit log.
• We never retain your source code beyond the window above, and we never sell or share your data.

Full detail, including cookies and your data-protection rights, is on the privacy page.

3. Third-party processing

The assessment is performed by Claude, so regions of your source code are transmitted to Anthropic's API over TLS. Under Anthropic's commercial API terms those inputs and outputs are not used to train models and are deleted within 30 days by default. Credentials detected in your code are stripped before transmission. Every run records what left this platform in a per-run egress manifest that you can read on the assessment page, including the destination, the retention posture in force, the number of calls, the volume of code sent, and how many secrets were removed.

If you would rather your code went to your own provider account, Kadense supports pointing runs at your own Anthropic, AWS Bedrock or Google Vertex endpoint. In that case the retention posture is the one you have agreed with that provider, and the egress manifest for each run records it. See the trust centre.

4. Your responsibilities

• You confirm you own the codebase you upload, or are authorised to submit it for security assessment, and that you may lawfully disclose it to a third-party processor for that purpose.
• An assessment is an automated review of source code at a point in time. It is evidence, not a warranty: it does not certify that your application is secure, and it does not replace a penetration test or a human audit.
• Keep your credentials and multi-factor device secure. You are responsible for activity under your account.

5. Commercial terms — pending legal review

The clauses below are placeholders. They are listed so the gaps are visible rather than overlooked, and they must be drafted with legal advice for the governing jurisdiction before Kadense is sold commercially.

• Fees, billing and refunds — pricing, credit expiry, failed-run credit treatment, and refund conditions.
• Limitation of liability — liability cap and excluded losses. Not drafted. No limitation is asserted here.
• Warranties and disclaimers — what is warranted about the service, and what is expressly not.
• Service levels — availability, support response, and planned maintenance.
• Term and termination — notice periods, and what happens to your reports and data on termination.
• Indemnities — including the position on code you were not entitled to upload.
• Governing law and dispute resolution — jurisdiction and forum.
• Changes to these terms — notice mechanism. Note that the data-processing terms in §1–§4 are versioned, and a substantive change requires you to re-accept before continuing to use the console.
• Sub-processors — the list, and notice of changes. Anthropic is named in §3; the trust centre lists the infrastructure providers.

Contact

support@collabor8.ai

Data-processing terms version 2026-11-10. See also Privacy & cookies and the trust centre.