Privacy Policy

01. Our Stance on Privacy

Prism AI is designed with an offline-first, client-authoritative privacy paradigm. As an orchestration framework built under a Bring Your Own Credentials (BYOC) pattern, Prism AI never processes, proxies, or relays model-provider API traffic through any Prism-hosted server. All inference calls go directly from your device to your chosen model provider (OpenAI, Anthropic, Google Vertex AI, etc.) using your own credentials.

02. Information We Collect & Process

Because Prism AI executes code sandboxing and prompt-handling on your own environment, we preserve your privacy by eliminating model payload and credential ingestion.

• API Keys & Credentials: User API keys are stored strictly in hardware-backed storage (Android Keystore on mobile) or local browser storage during web previews. They are never transmitted to or stored on any Prism AI Labs server.
• Direct Model Communication: All prompts and inference requests are sent directly from your device to your selected model provider. Prism AI Labs servers never proxy, inspect, or log model traffic.
• Execution Compute: Code and build execution happens on your own device (via Android Virtualization Framework pKVM) or inside your own GitHub Codespaces allocation — never on Prism-hosted compute.
• Prism AI Server Scope:Prism AI Labs' own servers only handle account/session orchestration state, planning metadata, and anonymous usage or crash analytics — never model traffic or credentials.
• Early Access Directory: When you voluntarily submit your application to the active build list, we preserve your submitted contact details (such as email and context answers) strictly to process admission lists safely.

03. Secure Sandbox Execution

The execution matrices utilized in Prism AI actions run inside isolated local processes (AVF pKVM) or your own GitHub Codespaces environment. There is no Prism-hosted execution compute fleet. Any diagnostic output or intermediate code state remains strictly on your device or user-owned compute allocation.

04. Data Retention and Safety

Under no circumstances do we trade, distribute, or broker your organizational parameters, code repositories, or LLM inputs. Your credential inputs are retained exclusively in hardware-backed Android Keystore or local storage, with zero outbound replication hooks to Prism servers.