Legal
Subprocessors
Last updated: August 21, 2026
Open Tag engages the third-party subprocessors below to help deliver, secure, and support our hosted service. We update this list as our subprocessors change.
Infrastructure & platform
| Subprocessor | Purpose | Location |
|---|---|---|
| Amazon Web Services | Cloud hosting and storage | United States |
| Cloudflare | CDN, DNS, and network security | United States |
| Slack Technologies | Workspace integration where Open Tag is tagged in | United States |
Operations & support
| Subprocessor | Purpose | Location |
|---|---|---|
| Google Workspace | Email and internal collaboration | United States |
| Stripe | Payment processing (paid plans) | United States |
| Sentry | Error monitoring and diagnostics | United States |
Model providers
Open Tag is model-agnostic. You bring your own API key for the provider you choose, and requests are sent to that provider under your account. Because you configure this yourself, the model provider you select (for example Anthropic, OpenAI, or Google) acts as a subprocessor for the content you route through it. We do not add a model provider on your behalf.
If you run an open-source model such as Llama, Qwen, Mistral, or DeepSeek on your own hardware — via Ollama, vLLM, or similar — no model subprocessor is involved at all, because the content never leaves your infrastructure.
Self-hosting
You can self-host Open Tag and reduce or eliminate reliance on our subprocessors entirely.
Questions & notifications
To ask about our subprocessors or request advance notice of changes, email privacy@opentag.bot.