Legal

Data processing summary

Last updated May 2026

Evaluation API — what you send

HTTPS POST to api.getechostack.com/v1/evaluate with Authorization: Bearer ech_dw_<secret>. Body includes input_type and input (transcript turns, form fields, or ticket text). No playbook manifest in the body — it is bound to your deployment.

What we return

Structured JSON: status, extracted fields, missing fields, next_action, and latency metadata. Your stack (or n8n/Zapier) decides what to do with the result.

Where data is processed

API runs on Railway (US region unless you have a dedicated EU deployment). PostgreSQL and auth are hosted on Supabase; confirm your project region in the Supabase dashboard. Redis (Upstash) is used for rate limits and session bridging.

Subprocessors

Infrastructure: Railway, Vercel (dashboard), Supabase, Upstash. AI inference: model provider configured for your deployment (e.g. Anthropic). We do not train foundation models on your evaluation payloads.

Security

Deployment secrets (ech_dw_) authenticate evaluate calls. Secrets are stored hashed; rotate from the deployment page if compromised. Use TLS only; do not embed secrets in client-side code.

DPA / enterprise

For a Data Processing Agreement or EU-only processing requirements, email hello@getechostack.com with your company name and expected monthly evaluation volume.

Questions? hello@getechostack.com · Back to home