Where your data is processed
Service infrastructure location, model inference countries, PIPA posture.
PleumRouter's service infrastructure (servers and databases) runs in the Seoul region of South Korea. Model inference, however, happens on each model vendor's infrastructure and may be located overseas. This page separates the two — where your account and usage records live is a different question from where your prompts go.
Frequently asked questions#
Where are PleumRouter's servers and databases?#
In the Seoul region of South Korea. The frontend runs on Vercel (icn1), the database on Supabase (ap-northeast-2), and the API servers and Redis on Alibaba Cloud (ap-northeast-2). Account data, usage records, consent history and the billing ledger are therefore stored domestically as their primary location.
Where does model inference happen?#
It depends on the model. The processing country follows the table in Article 5 of the Privacy Policy. Even a model from a Korean company may run on overseas infrastructure. Upstage Solar, for example, is processed on US infrastructure. The recipient, country, training-use flag and retention period for each provider are published in full in the same table.
Can I require inference to stay inside Korea?#
Not today, and we do not claim otherwise. There is no option to restrict routing to models that infer only on domestic infrastructure. If you need to reduce cross-border transfer, per-API-key PII masking — which strips detected personal data before the request leaves — is the practical option.
What does PII masking actually cover?#
It is a per-API-key option that replaces detected personal data in text before the request reaches the provider. See the PII masking document for its scope. We do not claim it masks everything.
What else leaves the country?#
Email delivery (Resend, US), bot mitigation (Cloudflare, global edge), usage analytics (Google Analytics, US) and error tracking (Sentry, US) are processed overseas. Any other overseas transfer follows Article 5 of the Privacy Policy. Error messages, URLs, user identifiers, API request bodies and prompts are not sent to Sentry.
Summary#
| Data | Processing location | Source |
|---|---|---|
| Account, usage records, consent history, billing ledger | Domestic (Seoul region) | Privacy Policy Art. 4 |
| Prompt and response bodies (model inference) | May be overseas, per model | Privacy Policy Art. 5 |
| Email, security, analytics, error tracking | Overseas (US, global) | Privacy Policy Art. 5(5) |
Source: /privacy · /docs/pii-masking · 2026-11-03
This page is a developer-facing summary of the Privacy Policy. The Privacy Policy is the legally binding text and prevails where the two differ.