Built in Germany. Your monitoring data is stored in the EU.
UptimeEye is built and operated by a German company, so the GDPR applies to us by default — not as an afterthought. We offer support in English and German, and we keep this page honest: no certifications we don't have, no claims we can't back up.
Operated by LaunchX GmbH, Germany • Imprint • GDPR • Privacy policy
Where is your data stored?
Data at rest: European Union
All monitoring data and customer data — monitor configurations, check results, incidents, and account information — is stored in a database hosted in the European Union. Encrypted database backups are kept with AWS in Frankfurt, Germany. Log data from UptimeEye Logs is held in a separate log store in Germany that is not backed up.
Checks run from six locations, results are stored in the EU
To measure your uptime the way your users experience it, our check probes run from six locations. eu-central-1 runs on our own hosting in Germany; the other five run on AWS in the US, Singapore, Australia and Brazil. The probes only send requests to the endpoints you configure — all results are sent back and stored in the EU.
Want a monitor checked only from the EU? Use only eu-central-1. A monitor that runs only there is checked exclusively from our hosting in Germany (Hetzner): its configuration, secure variables and check responses never go to a probe outside the EU. Like all your data, it is stored in the EU; our encrypted database backups are kept with AWS in Frankfurt (eu-central-1).
Probe locations and IP addresses
Allowlisting our probes in a firewall? These are the IPv4 addresses each location sends its checks from.
- eu-central-1 Europe (Germany)
- 138.199.227.139
- 168.119.111.181
- 162.55.169.230
- 88.198.112.127
- us-east-1 US East (N. Virginia)
- 23.20.188.124
- us-west-2 US West (Oregon)
- 52.34.139.124
- ap-southeast-1 Asia Pacific (Singapore)
- 54.251.132.117
- ap-southeast-2 Asia Pacific (Sydney)
- 32.236.203.225
- sa-east-1 South America (São Paulo)
- 54.232.22.150
The addresses of the five locations outside the EU are static and stay the same when we replace a probe. eu-central-1 probes leave from one of our servers in Falkenstein, Germany; that list changes only when we add, remove or replace a server, and we announce planned changes in advance.
We publish IPv4 addresses only. Our probes connect over IPv4 whenever your host has an IPv4 address. Only a host without any IPv4 address is checked over IPv6, from the locations outside the EU; those IPv6 addresses are not static, so we can't publish them for an allowlist.
Subprocessors
We keep our list of third-party providers short and transparent. These are the services we rely on to run UptimeEye, and what data they process.
| Provider | Location | Purpose | Data categories |
|---|---|---|---|
| Clerk | United States | Authentication and user management | Name, email address, login credentials, session data |
| Stripe | United States | Payment processing and subscription billing | Workspace name (a customer record is created for every workspace, including Free), billing name and address, payment details, invoice data |
| Resend | United States | Transactional and alert emails | Email address, alert content (monitor names, status) |
| Hetzner Online GmbH | Germany (Falkenstein) | Application hosting and database (monitoring data), check probes at eu-central-1 | All application data: monitor configurations, check results, account data |
| Amazon Web Services (AWS) | United States, Singapore, Australia, Brazil | Check probes at the locations outside the EU (us-east-1, us-west-2, ap-southeast-1, ap-southeast-2, sa-east-1) — only for monitors that use those locations | Monitor configuration including secure variables, and check responses |
| Amazon Web Services (AWS) | Germany (Frankfurt, eu-central-1) | Encrypted database backups (Amazon S3) | Backup copies of all application data: monitor configurations, check results, account data |
| Google (Firebase Cloud Messaging) | United States | Push notifications to the UptimeEye mobile app, only for members who turn push on | Device push token, notification content (name and status of the monitor, task or log alert, organization name, internal IDs); no URLs, no log lines |
| OpenAI | United States | The in-app AI assistant, only when members use it and the organization has not set its own model provider | Chat messages and what the assistant reads to answer them (configuration of monitors, tasks, channels and status pages; status, error messages and timings of checks); log lines only if an admin switched on Log access; never response bodies, headers or secure variable values |
Transfers to subprocessors outside the EU are covered by Standard Contractual Clauses and, where applicable, the EU-US Data Privacy Framework. See our GDPR page and Privacy Policy for details.
Data processing agreement
We provide a Data Processing Agreement (DPA / AVV) for business customers. Email us at contact@uptimeeye.com and we'll send it over for countersigning — usually within one business day.
Request a DPAData retention
Raw check results
Detailed results of individual checks — response times, status codes, assertion outcomes — are kept for 7 days, then deleted.
Aggregated uptime statistics
Aggregated uptime and performance statistics are stored long-term, so your uptime history and status pages keep working over time.
Monitoring without the data headache
Start monitoring your APIs, websites, and cron jobs with a team that takes data protection seriously by default.
Start free14 days of Pro included, then free forever. No credit card.