Security Policy
Effective Date: September 22, 2026 | Entity: Axleta
1. Architectural Overview & Security Guarantees
Axleta's Context-Packer is built on a Client-Side First Security Model. Source code parsing, file filtering, and XML context assembly occur 100% locally inside your web browser execution thread.
- Zero Source-Code Persistence: Code fetched from GitHub repositories is processed entirely in volatile memory (RAM). Axleta servers never collect, store, transmit, or cache your codebase contents.
- Direct Route: Repository files route directly between GitHub's API endpoints and your web browser client over TLS 1.3 encrypted HTTPS tunnels.
2. GitHub Personal Access Token (PAT) Handling
Your PAT is held exclusively in volatile browser memory or temporary local storage for active session requests. PATs are transmitted exclusively to official GitHub API endpoints (api.github.com) and are never logged, persisted, or relayed to Axleta servers.
3. Data Retention Summary
| Data Category | Storage Location | Retention Period |
|---|---|---|
| Source Code & Prompts | Volatile Browser Memory | Cleared on tab close |
| GitHub Access Tokens | Session Memory | Immediate local clearing |
| User Account & Balance | Supabase Database | Duration of active account |
4. Contact & Compliance
For data privacy queries or account deletion requests under GDPR/CCPA, please contact support@mail.axleta.com.