agoráconversations
§ operations

Data handling

Residency, retention windows, deletion on cancellation, and request erasure.

agorá stores three things: subscriber data (account, billing, MCP URLs), run records (the structured log of each conversation), and model invocation metadata. None of it leaves the runtime region you select.

01

Residency

  • US (default) — runtime and storage in us-east.
  • EU on request — runtime and storage in eu-central. Subscribed at provisioning time per workflow.
  • Practice-scale subscribers can pin all workflows to one region by default.
02

Retention

  • Run records: 90 days rolling on Pro. Halved to 45 with BYO keys.
  • Subscriber data: kept while the subscription is active; deleted within seven days of cancellation.
  • Billing data: kept seven years per tax obligations; the rest is purged.
03

Erasure requests

Customer-side erasure requests come through your client, not through agorá — agorá does not see the customer's identity, only the structured fields the workflow collected. If a workflow collected an identifier, deleting that subscriber's run records purges the field. The DPA spells out the process.