Subprocessors
Version 1.3. Last updated: 14 October 2026.
Published in English, Russian and Uzbek. The English text prevails if the versions differ.
This page lists every third party that may process data on our behalf when we provide the Service. It is referred to by the Data Processing Agreement and kept current.
How we change this list
Before a new subprocessor starts processing your data, we publish it here and email the notice to the address on your account at least 30 days in advance.
You may object within 15 days, on reasonable grounds relating to data protection. If we cannot offer you a way around the change, you may end the affected subscription and we refund the unused part of your paid period.
To be told about changes, no action is needed: notices go to your account email.
Infrastructure
| Provider | What it processes | Where | Why |
|---|---|---|---|
| Hosting provider, data centre in the Kingdom of Sweden (name available on request under NDA) | all account data and all telemetry | Sweden (Stockholm) | hosting of servers, storage and network |
This is the only subprocessor that touches your telemetry. Telemetry is stored only in the Kingdom of Sweden.
We do not publish the provider's name. Its identity and contract details are available to customers on request under a confidentiality agreement: write to support@tracepo.io.
Payments
| Provider | What it processes | Where | Why |
|---|---|---|---|
| Paylov (Uzbekistan) | payment amount, currency, our internal payment identifier | Uzbekistan | accepting payments in Uzbek soum |
| Polar Software Inc. | your email address, our organisation identifier, amount, currency, subscription status | United States (Polar Software Inc., Dover, Delaware) | accepting and managing subscriptions in US dollars |
Which provider handles your payment is decided by your organisation's billing currency and nothing else: soum through Paylov, dollars through Polar.
Card details never reach us. They are entered on the payment provider's own page and we never see or store them.
Communications
| Provider | What it processes | Where | Why |
|---|---|---|---|
| GoDaddy (outbound SMTP) | recipient email address and the content of the message | United States | delivering account, billing and alert emails |
Every transactional message we send passes through this provider, including alert notifications you have configured. That means the email addresses of your alert recipients pass through it too.
Sign-in
| Provider | What it processes | Where | Why |
|---|---|---|---|
| Google LLC | your email address and the name on your Google account | United States | optional "Continue with Google" sign-in |
This applies only if you choose to sign in with Google. If you sign in with an email and password, no data reaches Google.
Alert delivery to Telegram
| Provider | What it processes | Where | Why |
|---|---|---|---|
| Telegram FZ-LLC | the text of alert notifications you route to Telegram, and the identifier and title of the chat they go to | United Arab Emirates (Telegram FZ-LLC, Dubai), with servers in several countries | delivering alert notifications to Telegram |
This applies only if you connect a Telegram chat as an alert destination. An alert notification can quote what the alert is about, such as a host name and a value.
What is not on this list
We want to be specific about what we do not use, because monitoring products often do:
- no product analytics provider;
- no session recording or replay;
- no error-tracking or crash-reporting provider;
- no advertising or marketing tracking of any kind;
- no customer-support chat widget;
- no AI or large language model provider. We do not send your data to any model, ours or anyone else's;
- no content delivery network in front of the product.
If any of that changes, it appears here first, 30 days before it starts.
Questions
"BEATAI LABS" LLC, TIN 312569409, Toshkent shahri, Mirobod tumani, Yuksalish MFY, Kuylik-3 mavzesi, 37-uy, 26-xonadon, Republic of Uzbekistan