Last updated: September 11, 2026
Frontminder engages the sub-processors below to help provide the Service. A sub-processor is a third party that processes personal data on our behalf under a contract that requires it to protect that data. We maintain this page so customers can review who is involved and object to a material change as described in our Data Processing Addendum.
We only share the data each sub-processor needs for its role, and we do not authorize any of them to use customer or end-user data for their own purposes.
How we select and oversee sub-processors
Before engaging a sub-processor we assess whether it offers protections consistent with this policy and applicable law, including a data-processing agreement, appropriate security measures, and clear limits on how it may use the data we send. We give each provider the minimum data its role requires, prefer providers that support encryption in transit and at rest, and periodically review the list as the Service changes. Where a provider offers regional processing options relevant to a customer’s requirements, we take those into account. This page is the authoritative, current record of who is involved; it supersedes any earlier list.
Model providers (AI generation)
| Sub-processor | Role | Data processed |
|---|---|---|
| OpenRouter | Routes chat, vision, audio, and embedding requests to language models | Prompt and message content sent for a reply |
| DeepSeek | Direct chat model provider (in the DeepSeek and hybrid modes) | Prompt and message content sent for a reply |
Which provider handles a given request depends on the workspace’s configured provider mode. Message content may be optionally masked to remove certain personal data before it is sent (an add-on feature).
Platform and delivery
| Sub-processor | Role | Data processed |
|---|---|---|
| Resend | Transactional and lifecycle email delivery (verification, password reset, usage notices, onboarding) | Recipient email address, name, and message content |
| Stripe | Subscription billing and payment processing | Billing contact details and payment status (card data is handled by Stripe, not stored by us) |
| Telegram | Messaging channel and lead-alert delivery for agents connected to Telegram | Message content and Telegram identifiers for connected chats |
| Cloudflare | Edge delivery and the public waitlist site | Network metadata such as IP address for pages served through it |
Hosting and infrastructure
| Sub-processor | Role | Data processed |
|---|---|---|
| Hosting provider (being finalized) | Application hosting, compute, and storage for the Service | All categories of Customer Content and account data at rest |
| Backup storage (being finalized) | Encrypted database and file backups | All categories of Customer Content and account data at rest |
Hosting is not finalized at the time of this draft; the provider(s) will be named here before the Service accepts production customer data.
Optional integrations
Some features are only active if a customer enables them, and they introduce additional processors only for that customer:
- Web search (optional agent tool) — a search provider receives the query text when an agent runs a web search.
- Product database feeds — a customer’s chosen catalog source, where configured.
- CRM integrations — none are enabled by default; any that a customer connects will be listed to that customer.
Changes to this list
We may add or replace a sub-processor as the Service evolves. When we do, we will update this page. Under the Data Processing Addendum, customers may object to a new sub-processor on reasonable data-protection grounds; we will work in good faith to address the concern or, if we cannot, the customer may stop using the affected feature.
Contact
Questions about our sub-processors can be sent to support@frontminder.com.