prxy.monster / privacy

Privacy

prxy.monster processes requests so the configured module pipeline can run before and after the provider call. The four canonical hashes plus the receipt metadata always persist (they are the audit trail). Plaintext request and response bodies do not persist by default.

What may be retained

Receipt metadata — identity, provider, tokens, cost with pricing-table provenance, pipeline metadata, four canonical sha-256 hashes, signature. Per call.
Sealed payload blobs — only when payload_capture: encrypted_at_rest is opted in for that api_key. Sealed under your X25519 public key; we cannot read them.
Cache entries — when cache modules are enabled. Per-user scoped. Bypassed under encrypted_at_rest and none payload modes.
Reviewer-promoted patterns — when a reviewer in lair promotes a memory candidate. Tenant-scoped.
Compressed / archived context — when ipc, rehydrator, or compaction-bridge are enabled.
Account, billing, and usage metadata needed to operate the hosted service.
Anonymous sandbox session counters — anon_key_hash, ip_hash, request counters. Bare anon tokens never persist.

Full row-by-row matrix at /data-retention/.

Controls

Set payload_capture: none on your api_key to disable capture beyond receipt hashes. Cache is bypassed.
Set payload_capture: encrypted_at_rest with your X25519 pubkey to seal payloads under a key only you hold. Configure browser-side at lair /dashboard/admin/api-keys.
Disable cache modules in your pipeline to prevent cache retention.
Disable patterns to prevent pattern injection. (Outcomes can still be submitted; candidates simply do not promote.)
Use local mode (prxy-monster-local, MIT) when state must stay on your hardware.
Request hosted account deletion at [email protected]. A self-service deletion endpoint is planned but not currently documented as live.
Revoke a stored BYOK provider key any time via DELETE /v1/byok/:provider.

What we do not

No foundation-model training on customer requests, completions, or outcome notes.

No selling of customer data to third parties.

No silent retention of plaintext bodies. hash_only is the default.

No retention of bare anonymous-sandbox tokens.

No telemetry from prxy-monster-local. Local is local.

Telemetry

The hosted service records operational and usage metadata needed for billing, abuse prevention, debugging, and reliability. Local mode has no prxy.monster telemetry.

Subprocessors

See /subprocessors/ for the current list.

Last updated: 2026-05-07