Legal
Zephex is a stateless proxy. Tool call content passes through memory and is never written to disk, logged, or stored. This page details exactly what happens to your data at each stage.
Client (your editor) │ ├─ TLS 1.3 encrypted connection │ ▼Zephex Edge (Vercel / AWS) │ ├─ API key validated (SHA-256 hash comparison) ├─ Rate limit checked (Upstash Redis) ├─ Usage counter incremented │ ▼MCP Proxy (AWS ECS, Fargate) │ ├─ Tool arguments parsed ├─ Tool executed in isolated context ├─ Result assembled in memory │ ▼Response returned to client │ ├─ Tool input/output discarded from memory ├─ Only metadata logged (tool name, timestamp, status) └─ No code, no prompts, no outputs persistedThe entire tool call — from receiving your arguments to returning the result — happens in a single request/response cycle. There is no queue, no background job, and no intermediate storage. Once the HTTP response is sent, all tool-related data is garbage-collected from process memory.
| Data | Stored? | Where | Duration |
|---|---|---|---|
| Your source code | No | — | — |
| Tool input arguments | No | — | — |
| Tool output / response body | No | — | — |
| Your AI prompt / chat context | No | — | — |
| File contents accessed by tools | No | — | — |
| Tool name called | Yes | Supabase (encrypted at rest) | 90 days |
| Timestamp of call | Yes | Supabase | 90 days |
| Response status (success/error) | Yes | Supabase | 90 days |
| Latency (ms) | Yes | Supabase | 90 days |
| API key hash | Yes | Supabase | Until revoked |
| Hashed IP address | Yes | Supabase | 90 days |
What is logged:
What is never logged:
When you delete your account (Dashboard → Settings → Delete Account):
Data handling questions: support@zephex.dev