Security & Privacy Architecture
TRACE is designed around explicit data boundaries, portable artifacts, and visible uncertainty. This page describes commitments and planned controls without inventing certifications.
Raw source code stays strictly on machine (0 bytes transmitted)
Only signed metadata & .trace artifacts allowed across boundary
Ephemeral view of project memory; Git remains sole authority
sourceCodeIncluded: falseRaw file contents and private buffers are excluded at the parser AST boundary.
codeSnippetsIncluded: falseContext snippets and inline code extracts are redacted from synchronized payloads.
Secrets & Prompts RedactedAPI keys, credentials, and raw model conversations are forbidden from .trace outputs.
Operational boundaries
Precise mapping of operational behavior versus explicit non-claims across every system layer.
Local analysis executes entirely within the project environment. AST symbol extraction, conflict scanning, and deterministic checks run without requiring source-code upload to TRACE Cloud.
Zero required source-code transmission. Raw repository files, uncommitted buffers, and local environment variables never leave your machine.
Cloud coordination requires explicitly configured repository and model-provider boundaries. Only signed summaries, conflict digests, and approved .trace records are processed.
Retention, deletion policies, and third-party model provider behaviors are documented and auditable before production claims are made.
Credentials, tokens, prompts, raw source duplication, and private model conversations must not be written to .trace artifacts. Server-side secrets are kept outside browser and repository bundles.
Automatic runtime secret remediation or unverified DLP guarantees are not claimed; developers remain responsible for local credentials.
Future phases introduce tenant authorization, tamper-evident audit logs, safe Markdown sandboxing, secret scanning, prompt-injection hardening, and quarantine workflows.
SOC 2, ISO 27001, HIPAA, or formal regulatory compliance certifications are not claimed.
TRACE does not currently claim SOC 2, ISO 27001, GDPR certification, zero retention, compliance guarantees, or a completed enterprise security program. Operational boundaries reflect verified software invariants, not external regulatory attestations.
TRACE does not currently claim SOC 2, ISO 27001, HIPAA, GDPR certification, or a completed enterprise security audit.
External LLM model providers may retain temporary logs according to their enterprise terms unless self-hosted or network-isolated.
AST parsers and tree-sitter bindings operate on untrusted input; sandboxing and memory limits are enforced but zero-day immunity is not claimed.
TRACE will never implement individual developer rankings, keystroke logging, time tracking, or productivity scoring.
If you discover a security issue, vulnerability, or potential leak in the TRACE specification or implementation, please report it responsibly through our GitHub Security Advisory channel.