Privacy Policy

1. What We Collect

The Clawdence execution engine, running inside your cloud environment or in a dedicated single-tenant instance, processes the following categories of data on your behalf:

• -Slack messages in channels where Clawdence is invited. We read inbound prompts and post status updates.
• -Jira / issue tracker content including ticket titles, descriptions, and acceptance criteria provided as requirements.
• -Source code repository - read access to the target repository for context ingestion; write access only to isolated Git sandbox branches created by Clawdence.
• -API credentials - your BYOK API keys (OpenAI, Google, Grok etc.) stored encrypted at rest using AES-256.
• -Account and billing information - name, company, email address, and pilot agreement details.

2. No Training on Your Data

Clawdence does not use your source code, Slack messages, Jira requirements, or any other customer data to train or fine-tune any foundational AI model - ours or any third party's. Your data is used solely to execute the tasks you assign within your isolated customer environment. When you use BYOK API keys, your requests are sent directly to your chosen LLM provider under their enterprise API terms, which explicitly prohibit training on API inputs by default.

3. How We Use Your Data

Data is used exclusively to operate the Clawdence workflow: decomposing requirements, generating and executing code, running tests, and raising Pull Requests. We do not sell, rent, or share your data with third parties for their own commercial purposes.

4. Sub-processors

To deliver the service, your data may be processed by the following sub-processors:

• -Amazon Web Services (AWS) - hosting of the clawdence.com website and, where applicable, managed single-tenant customer instances. Self-hosted customers run the execution engine entirely within their own cloud environment.
• -OpenAI / Google / Grok - LLM inference via your BYOK API keys. Governed by your direct agreement with each provider.
• -Atlassian (Jira) and Slack - requirement ingestion and status reporting via their respective APIs.
• -GitHub / GitLab - isolated repository sandbox operations.

5. Data Retention & Isolation

Each customer operates in a fully isolated single-tenant environment inside their own cloud boundary. Clawdence does not commingle data between customers. Upon termination of a pilot, all project state, memory embeddings, and ingested context are permanently deleted within 30 days. API credentials are deleted immediately upon request or termination. Isolated repository clones created during execution are destroyed upon PR merge or rejection.

6. Security

All data is encrypted in transit via TLS 1.2+ and at rest using AES-256. API credentials are stored in an encrypted secrets manager and never logged. Access to customer environments is restricted to authorised Clawdence operations personnel on a need-to-know basis.

7. Your Rights

You may request access to, correction of, or deletion of your data at any time by contacting us at pilot@clawdence.com. We will respond within 30 days.

8. Changes to This Policy

We will notify active pilot partners of any material changes to this policy by email at least 14 days before they take effect.

9. Contact

Spectra IT Solutions LTD trading as Clawdence  ·  pilot@clawdence.com