Last updated: February 19, 2026
Zero-Knowledge Architecture: All API calls go directly from your browser to the AI provider. Your API keys and prompt content never transit through our servers.
Overview
Markdown Studio's Prompt Studio feature allows you to test prompts with AI models from OpenAI, Anthropic, and Google. All three providers support direct browser API calls, meaning your data never touches our infrastructure.
Architecture — Direct API Calls (All Providers)
┌─────────────┐
│ Your Browser│
└──────┬──────┘
│ HTTPS (Direct)
│ API Key + Prompt
↓
┌─────────────────────────┐
│ Provider API │
│ (OpenAI / Anthropic / │
│ Google AI) │
└─────────────────────────┘
All providers:
- No intermediary
- Maximum security
- Your keys never touch our infrastructureOpenAI (GPT Models)
Direct: Your browser connects to api.openai.com over HTTPS. No intermediary.
Anthropic (Claude Models)
Direct: Your browser connects to api.anthropic.com over HTTPS. No intermediary.
Google (Gemini Models)
Direct: Your browser connects to generativelanguage.googleapis.com over HTTPS. No intermediary.
What We Do NOT Do
- Receive API Keys: Keys are stored locally and sent directly from your browser to the provider
- See Your Prompts: Prompt content goes directly from your browser to the AI provider
- Log or Store Data: We have no server-side infrastructure that handles API requests
- Proxy or Forward Requests: There is no intermediary between your browser and the provider
- Cache Responses: AI responses stream directly from the provider to your browser
API Key Storage
- Location: Keys are stored in your browser's localStorage only
- Encryption: Keys are encrypted using AES-256-GCM before storage
- Encryption Key: Derived from your browser fingerprint (user agent, language, timezone)
- Deletion: Keys remain until you explicitly delete them or clear browser data
Risk Assessment
| Provider | Routing | Risk Level | Recommendation |
|---|---|---|---|
| OpenAI | Direct | LOW | Safe for all use cases |
| Direct | LOW | Safe for all use cases | |
| Anthropic | Direct | LOW | Safe for all use cases |
Security Guarantees
- All communication is over HTTPS (TLS 1.2+)
- All API calls are direct browser-to-provider (zero-knowledge)
- No server-side infrastructure handles your API keys or prompts
- API keys are encrypted at rest in localStorage
- HTML content is sanitized with DOMPurify to prevent XSS
Client-Side Security Considerations
While we never receive your keys, be aware of browser-side risks:
- Client-Side Encryption: Keys must be decrypted to use them; the decryption key is stored client-side
- Browser Extensions: Malicious extensions with page access could access stored keys
- XSS Risk: We use DOMPurify to prevent this, but any XSS vulnerability could expose stored keys
- Shared Devices: Do not use Prompt Studio on shared or public computers
Transparency Commitments
- Detailed Documentation: This page documents the complete architecture
- Privacy: Full disclosure of data handling practices
- Contact Available: Questions answered promptly
Monitoring & Best Practices
What You Can Monitor
- Your API Usage: Check OpenAI/Anthropic/Google dashboards directly
- Unexpected Charges: Set up billing alerts on provider accounts
- Key Usage: Some providers show last-used timestamps
Security Best Practices
- Only use on trusted, personal devices
- Use API key restrictions when available (IP allowlists, referrer restrictions)
- Rotate keys periodically (monthly recommended)
- Monitor API usage for anomalies
- Review your provider's API key permissions
- Consider using separate keys for testing vs production
Incident Response
If You Suspect Key Compromise
- Immediately rotate your API key in the provider's dashboard
- Check your provider's usage logs for unauthorized access
- Remove the old key from Markdown Studio
- Generate a new key with restrictions (IP allowlist if available)
Questions?
If you have questions about our security architecture or need clarification:
- Review our Privacy
- Contact us through our website