Zero-Knowledge
Code Processing

Your source code is private. Our system is designed to protect it from upload through analysis and deletion.

[01] Temporary Processing

All code units are processed in isolated memory buffers. Once the diagnostic scan completes, the source file is immediately purged from our persistent storage (BullMQ local volumes). Retention time: < 60 seconds.

[02] No Model Training

We use proprietary LLMs configured with strict privacy parameters. Your data is NEVER used to fine-tune or retrain any foundational models. Your logic remains entirely yours.

[03] Isolated Analysis

Each analysis runs in a strictly isolated compute partition. Cross-pollination of data between users or organizations is architecturally impossible.

[04] Results Only

We only persist the *results* of the analysis (the Findings and Stability Score). This metadata contains no raw source code, ensuring your IP is never at risk in our database.

Data Retention & Lifecycle Policies

Intelligence Archive Retention

  • •Findings & issues: Retained indefinitely for analysis
  • •Architectural blueprints: Permanent retention
  • •Code snippets: Encrypted storage with access controls
  • •AI analysis results: Long-term archival

Source Code Lifecycle

  • •Ephemeral mode: < 60 seconds retention
  • •Persistent mode: Encrypted S3 storage
  • •Temporary buffers: Immediate cleanup
  • •No backups or recovery options

User Data Controls

  • •Project-level deletion controls
  • •Submission history management
  • •Intelligence archive cleanup
  • •Audit trail access for compliance

Compliance Retention

  • •SOC2 audit logs: 7 years minimum
  • •GDPR access logs: 3 years retention
  • •Security events: 2 years archival
  • •Data destruction proofs: Permanent

What Happens to Uploaded Code

1

Upload

ZIP/Repo unit is received via encrypted HTTPS and moved to local work volume.

2

Scan

Rule Engine evaluates the unit. AI models parse logic in memory. Excerpts are generated for findings.

3

Save Results

Results are encrypted and stored in the database. The original code unit NEVER enters the database.

4

Delete Source Code

Worker triggers UNLINK protocol. The ZIP file and any temporary buffers are deleted from the disk permanently.