Privacy

uptime.ooo is operated by RoamGO LLC. Last updated 23 August 2026.

This describes what the service actually stores and sends, taken from the system itself rather than written to a template. If a behaviour changes, this page changes with it.

What we collect

Your account

• Email address, which is how you sign in and how we reach you.
• A password hash. We never store the password itself and cannot recover it.
• Workspace name, plan, and who belongs to it in which role.
• Session records, so you stay signed in, and two-factor recovery codes if you enable them.
• Any additional paging contacts you add — an email address or a phone number.

What you ask us to watch

• The addresses of the sites, APIs, and jobs you monitor, and the settings for each check.
• Any credentials you put into a check — a request header, a basic-auth login, an SNMP community. Provide a dedicated, least-privileged credential for monitoring rather than a real one.
• The results of those checks: status, response time, and any error, per region.
• Incidents, their timelines, who was paged, whether it was delivered, and who acknowledged.
• Messages you write in incident war rooms and team chat, and files you upload to them.
• Credentials for integrations you connect, encrypted at rest.

Devices and delivery

• Push tokens for phones you sign in on, so a page can reach the lock screen.
• A record of each notification sent, so an incident timeline can show whether the page landed.

Security and support

• Security events — sign-in failures, suspicious requests — which include an IP address, the path, the user agent, and the email address that was tried. These exist so an account takeover can be spotted and stopped.
• Support conversations you start, including the email address and name you give, and the IP address and user agent of the message.

Usage measurement

We count page views on the marketing site, hosted status pages, and inside the app. No raw IP address is stored for this. Visitors are counted by an opaque first-party cookie identifier; the referring site is reduced to its hostname; a country is recorded only when our network layer supplies one. There is no third-party analytics or advertising code anywhere on the site or in the apps.

What we never do

• We do not sell personal data, and we do not share it for advertising.
• We do not track you across other websites.
• We do not read your monitoring data to build a profile of you or to train anything.
• The mobile apps contain no analytics or advertising SDK.

Who else touches it

These are service providers acting on our instructions. Each receives only what its job requires.

• Hetzner — hosting and the database, in Germany.
• Vultr — the probe agents that run your checks from other regions. They receive the check to perform and return its result.
• Google Firebase Cloud Messaging — carries a push notification to an Android device. Apple's push service does the same for iPhones.
• Stripe — payment. Card details go to Stripe directly and never reach our servers.
• Twilio — SMS pages, where you have configured them.
• Destinations you configure yourself — Slack, Telegram, Discord, Microsoft Teams, PagerDuty, Opsgenie, GitHub, Linear, Zendesk, or your own webhook. Anything you route to one of these is sent there because you asked for it.

Running checks from several regions means a check result crosses borders by design. That is what regional monitoring is.

How long it is kept

• Raw check results and page-view records are kept for a bounded retention window and then dropped automatically.
• Daily rollups of uptime are kept longer, so history outlives the raw data behind it.
• Everything else is kept while your workspace exists.

Deleting it

The owner of a workspace can close it from Preferences, or from Settings in the mobile app. Monitoring and paging stop at once; everything is permanently deleted thirty days later, and the owner can cancel at any point in between.

That deletion is total: monitors and their history, check results, incidents, status pages, messages, uploaded files, stored integration credentials, page-view records attributed to the workspace, and every account left belonging to no other workspace. Records we must keep for tax and accounting are the exception, and they cannot be used to sign in or to show what you monitored.

The full account-deletion page explains it without needing to sign in.

Your rights

You can ask for a copy of your data, ask us to correct it, or ask us to delete it. Write to support@roamgo.net. Deleting a workspace yourself is immediate to start and needs no request.

Children

The service is for operating computer systems and is not directed at children. We do not knowingly collect data from anyone under 16.

Changes

If this page changes in a way that affects what we do with your data, we will say so in the app before it takes effect.