Subprocessors
Effective: August 2025.
Inference runs on Merki's own infrastructure. Merki does not route inference to third-party inference providers, and no subprocessor handles request data. Prompts and completions are never sent to anyone else.
The table below lists the processors that handle account, verification, and billing data. None of them sees request content.
| Subprocessor | Purpose | Data | Request content |
|---|---|---|---|
| Sumsub | Age assurance (Roleplay) and identity verification (Cybersecurity) | Check result and minimum account reference; documents stay with Sumsub | No — never sees prompts or completions |
| Payment processor, identified at checkout | Card and purchase processing | Purchase amount, reference, and payment metadata; no full card numbers stored by Merki | No — never sees prompts or completions |
Notes:
- On BYOK routes, requests go to the provider you selected, under your own agreement with that provider. That provider is not a Merki subprocessor, and it is not routing done by Merki: you chose the destination.
- Age assurance for Roleplay and identity verification for Cybersecurity are described in Age and identity. No subprocessor handles request data.
If this ever changes, customers will be notified at least 30 days before a new subprocessor is engaged, and this page will list it.