Skip to content

Privacy

Privacy Policy

How RealUptime LLC collects, uses and safeguards the information you provide, including the cookies and analytics the site uses and the categories of companies that process data for us.

Effective October 4, 2026

RealUptime LLC Privacy Policy

RealUptime LLC (the “Company”) is committed to maintaining robust privacy protections for its users. Our Privacy Policy (“Privacy Policy”) is designed to help you understand how we collect, use and safeguard the information you provide to us and to assist you in making informed decisions when using our Service.

For purposes of this Agreement, “Site” refers to the Company’s website, which can be accessed at https://realuptime.io, including its subdomains.

“Service” refers to the Company’s services accessed via the Site, in which users can publish status pages, monitor the uptime of websites and servers, track errors in their software, and look up outages of third-party services.

The terms “we,” “us,” and “our” refer to the Company.

“You” refers to you, as a user of our Site or our Service.

By accessing our Site or our Service, you accept our Privacy Policy and Terms of Use (found here: https://realuptime.io/terms), and you consent to our collection, storage, use and disclosure of your Personal Information as described in this Privacy Policy.

I. Information we collect

We collect “Non-Personal Information” and “Personal Information.” Non-Personal Information includes information that cannot be used to personally identify you, such as anonymous usage data, general demographic information we may collect, referring/exit pages and URLs, platform types, preferences you submit and preferences that are generated based on the data you submit and number of clicks. Personal Information includes your email address, and the other information listed in this section that identifies you, which you submit to us through the registration process at the Site or while using the Service.

1. Information collected via technology. To activate the Service you do not need to submit any Personal Information other than your email address. To use the Service thereafter, you do not need to submit further Personal Information, although you may choose to, which may include: your name, a phone number for text alerts, the details of your team members, and billing details when you buy a plan. However, in an effort to improve the quality of the Service, we track information provided to us by your browser or by our software application when you view or use the Service, such as the website you came from (known as the “referring URL”), the type of browser you use, the device from which you connected to the Service, the time and date of access, and other information that does not personally identify you. We track this information using cookies, or small text files which include an anonymous unique identifier. Cookies are sent to a user’s browser from our servers and are stored on the user’s computer hard drive. Sending a cookie to a user’s browser enables us to collect Non-Personal information about that user and keep a record of the user’s preferences when utilizing our services, both on an individual and aggregate basis. For example, the Company may use cookies to collect the information listed under Cookies and tracking below.

The Company may use both persistent and session cookies; persistent cookies remain on your computer after you close your session and until you delete them, while session cookies expire when you close your browser. For example, we store a persistent cookie to keep you signed in, and one to remember your answer about measurement. Every cookie we set, what it holds and how long it lasts is listed under Cookies and tracking below.

2. Information you provide us by registering for an account. In addition to the information provided automatically by your browser when you visit the Site, to become a subscriber to the Service you will need to create a personal profile. You can create a profile by registering with the Service and entering your email address and confirming it, and choosing how you sign in. By registering, you are authorizing us to collect, store and use your email address in accordance with this Privacy Policy.

3. Children's privacy. The Site and the Service are not directed to anyone under the age of 13. The Site does not knowingly collect or solicit information from anyone under the age of 13, or allow anyone under the age of 13 to sign up for the Service. In the event that we learn that we have gathered personal information from anyone under the age of 13 without the consent of a parent or guardian, we will delete that information as soon as possible. If you believe we have collected such information, please contact us at support@realuptime.io.

What we collect, in detail

  • Account and team information: email addresses, names, password hashes, passkeys and authenticator-app secrets, the account ID, email, and name from a Google, GitHub, or Apple sign-in, team invitations, and single sign-on or directory-provisioning records if your company uses them.
  • Monitor names, target URLs, status-page content, settings, and regional check results.
  • Error events your applications send to RealUptime Errors, which can include stack traces, request metadata, releases, and tags your code attaches. What an event contains is decided by your code and your project's scrub rules; treat it as data you control and we process (see the DPA).
  • Information reported by the Monitor server agent you install: hostname, operating system, CPU, memory, disk, network, and load; where enabled, the names of processes, containers, and services and database metrics; and, only if you configure a log source, short snapshots of recent log lines, which can contain whatever your applications logged.
  • Browser-check steps you configure, and the screenshots and failure traces those checks capture.
  • If you turn on an AI summary feature (issue summaries in Errors settings, or incident insights in the dashboard), the data for the issue or incident being summarized: for an issue, its already-scrubbed stack trace, breadcrumbs, tags, and release; for an incident, its timeline, affected monitors and regions, error counts, and the status of vendors you watch. The summary is stored with the issue or incident.
  • Problem reports on the public outage tracker. We store the report category and region and a one-way daily-salted hash used only for rate limiting; we do not store the reporter's IP address, and raw reports are pruned after 7 days (aggregate counts are kept).
  • API-key hashes and integration settings, such as a Slack webhook you choose to provide, daily API and MCP usage per key, and, for a key with no network restriction, the network it was last used from.
  • Subscription and transaction identifiers from our payment processor when you use a paid plan, the country on your billing address, and any referral or promo code used at signup.
  • Support requests and discount-program applications you send us, including your name, company details, and message.
  • Email addresses or phone numbers of people who subscribe to a public status page, the addresses a status-page owner imports (each gets one confirmation email and is deleted if it never confirms), email addresses of people who subscribe to outage alerts or ask for product updates from our site, and which page each request came from.
  • Phone numbers account members add as their own on-call alert channel.
  • If campaign attribution ran for your visit (see "Cookies and tracking") and you then created an account, the campaign tag from the link you arrived through, the referring site's hostname, and the page you landed on. This is kept with the account record so we can tell which listings and campaigns are worth continuing. It records the link, not you, it is never updated after the account is created, and it is not used to profile you or shown to anyone outside our own team.
  • Basic request, device, diagnostic, and security logs produced by the service and hosting provider, including your IP address. How long we keep it depends on why: an IP address used only to rate-limit sign-in, signup, and subscription attempts is discarded within about two days; the IP address, browser, and approximate country of each signed-in session are kept until about 30 days after the session ends; the IP address recorded with a status-page or outage-alert subscription is kept while the subscription exists; the security audit log keeps them as described under Retention and deletion; and for an API key with no network restriction we keep the network it was used from (the first three parts of an IPv4 address) for 400 days after its last use, so we can warn the owner when a key is used from somewhere new.
  • Usage statistics for our site and the signed-in dashboard, from an analytics tool we run on our own servers: the page and its title, the referring site, your screen size and language, and the browser, operating system, device type, and approximate location (country, region, and city) the tool works out from your connection. Your IP address itself is not stored. Visits from the same connection and browser are grouped under a code that changes every month, so we can count visitors without recognizing you after that. On the dashboard, page titles are recorded as a fixed title and identifiers in addresses are replaced, so no monitor, server, project, or status-page name is recorded. It also counts events such as a completed signup or a setup step being started. It sets no cookie, stores nothing on your device, is never tied to your account, and does not run on customer status pages. The web analytics described under "Cookies and tracking" is replacing it, and we can switch it off at any time; once it is off, it records nothing. See "Cookies and tracking" below.

Payment-card details are entered with and processed by our payment processor; RealUptime does not receive the complete card number. We do not run advertising trackers.

Cookies and tracking

Some cookies are strictly necessary for something you asked for, and are always set when you use that feature:

  • A session cookie, set when you sign in, that keeps you signed in. It holds a random token checked against our server on each request, never your identity. The same cookie keeps you signed in on realuptime.io and its subdomains, including dashboard.realuptime.io, and lasts up to 30 days.
  • Short-lived sign-in security cookies, set only when you start a Google, GitHub, or Apple sign-in, that protect that exchange against cross-site request forgery. They are deleted as soon as the sign-in finishes.
  • Administrative cookies used only by our own staff for internal tooling.
  • A preference cookie, named ru_consent, that remembers your answer about measurement for 180 days, set only when you answer. Your color theme is remembered in your browser the same way.

The rest are measurement. Each one says where it is used: our public site (realuptime.io, www, and docs), and for the web analytics identifier also the signed-in dashboard (dashboard.realuptime.io). None is used on customer status pages:

  • ru_attr, on the public site, for 30 days, when a visit arrives through one of our tagged campaign links: the campaign parameters, the referring site's hostname, and the page you landed on. It holds no identifier of you or your device. If you go on to create an account, the campaign tag is copied onto the account record, as described under "Information we collect".
  • ru_cid, on the public site and the dashboard, for 13 months: a random identifier our web analytics provider uses to group your page views and events. It is one cookie for both, so the same identifier follows you from the public site into the dashboard.
  • ru_outages_touch and ru_agent_docs_touch, on the public site, for 30 days, and ru_organic_return_tracked, on the public site, for one day: the date you last viewed an outage page or the server-agent install guide, or that a return visit was counted today. They hold no identifier; we use them to count return visits.
  • Two values kept in the browser tab until you close it: one, on the public site and the dashboard, groups that tab's page views for web analytics, and one, on the public site, records that an outage page was already viewed in it.

Web analytics measures which pages and campaigns are working and how our own customers use the product. Our own server sends our web analytics provider, keyed to the ru_cid identifier:

  • From the public site: the pages you view (the address without its query string, and the page title), the campaign or the site that brought you, if any (that site's hostname only, never its page or address), and our funnel events there (such as a completed signup).
  • From the dashboard, once you are signed in: the dashboard pages you view and the product steps you take there, such as your first visit to the dashboard, starting or leaving a setup form, creating your first monitor, or choosing a plan. For a page it receives the address with every identifier in it replaced and no query string, under one fixed title; for a step, its name and fixed labels such as which product, which form, or which plan. It never receives the name, address, or content of a monitor, server, project, status page, or anything else in your account.

We do not load the provider's script in your browser, and we do not send it your IP address, your device, or your browser details. Nothing from a customer status page, a private link, or our internal tools reaches it.

When measurement runs. If you are in the European Union, the European Economic Area, the United Kingdom, or Switzerland, or we cannot tell where you are, none of the measurement above happens unless you agree: a banner on the public site asks, and nothing is set or sent until you choose Allow. Ignoring the banner is treated the same as declining, including when JavaScript is disabled. Your answer covers the dashboard too; the dashboard shows no banner of its own, so if you have not answered, nothing is measured there. Everywhere else, measurement runs from your first visit, on the public site and the dashboard, without a banner, and you can turn it off at any time with the control on this page. Declining, wherever you are, deletes the measurement cookies from your browser and stops web analytics for it, on the public site and the dashboard.

Separately, our own analytics tool, described under "Information we collect", sets no cookie and stores nothing on your device, so it does not depend on this choice. To avoid counting one action twice, the site keeps short flags in the browser tab that hold only "1" and are cleared when you close it. We also count how often the banner is answered yes and how often no, as a running total that carries no identifier and is not linked to your visit.

We use no advertising, marketing, or cross-site tracking cookies. Blocking cookies in your browser is fine for reading the site, but account features cannot work without the session cookie. If our cookie use changes, we will ask for consent before setting anything that needs it.

II. How we use and share information

Personal Information. Except as otherwise stated in this Privacy Policy, we do not sell, trade, rent or otherwise share for marketing purposes your Personal Information with third parties without your consent. We do share Personal Information with vendors who are performing services for the Company, such as the servers for our email communications who are provided access to user’s email address for purposes of sending emails from us. Those vendors use your Personal Information only at our direction and in accordance with our Privacy Policy.

In general, the Personal Information you provide to us is used to help us communicate with you. For example, we use Personal Information to contact users in response to questions, solicit feedback from users, provide technical support, and inform users about promotional offers.

We may share Personal Information with outside parties if we have a good-faith belief that access, use, preservation or disclosure of the information is reasonably necessary to meet any applicable legal process or enforceable governmental request; to enforce applicable Terms of Service, including investigation of potential violations; address fraud, security or technical concerns; or to protect against harm to the rights, property, or safety of our users or the public as required or permitted by law.

Non-Personal Information. In general, we use Non-Personal Information to help us improve the Service and customize the user experience. We also aggregate Non-Personal Information in order to track trends and analyze use patterns on the Site. This Privacy Policy does not limit in any way our use or disclosure of Non-Personal Information and we reserve the right to use and disclose such Non-Personal Information to our partners, advertisers and other third parties at our discretion.

In the event we undergo a business transaction such as a merger, acquisition by another company, or sale of all or a portion of our assets, your Personal Information may be among the assets transferred. You acknowledge and consent that such transfers may occur and are permitted by this Privacy Policy, and that any acquirer of our assets may continue to process your Personal Information as set forth in this Privacy Policy. If our information practices change at any time in the future, we will post the policy changes to the Site so that you may opt out of the new information practices. We suggest that you check the Site periodically if you are concerned about how your information is used.

Why we use information

For readers subject to the GDPR, each purpose below names the Article 6(1) legal basis it relies on, since the basis has to be identifiable per purpose rather than asserted once for the whole service (Art. 6 GDPR).

  • Operate monitoring, public status pages, alerts, APIs, and account features. Necessary to perform the contract you signed up for. Basis: contract, Art. 6(1)(b).
  • Send status-page or product-alert messages to a subscriber, by email or SMS. Sent because that address or phone number is on a subscription list the subscriber joined, or confirmed after a status-page owner imported it, whether or not they hold a paid account. Basis: contract, Art. 6(1)(b).
  • Send a welcome or product-update email to someone who asked for updates from our site. This is a distinct purpose from the status-page alert above: it is requested marketing rather than an alert tied to a specific status page. Basis: consent, Art. 6(1)(a), since it is sent because you asked, or, for an existing lead we already have a relationship with, legitimate interest, Art. 6(1)(f), in telling you about the product you use.
  • Process subscriptions and respond to billing or support requests. Basis: contract, Art. 6(1)(b), and, for records tax and accounting law requires us to keep, legal obligation, Art. 6(1)(c).
  • Authenticate users, enforce plan limits, prevent abuse, rate-limit sign-in and subscription attempts, and investigate failures. A narrow-purpose use of data such as the IP addresses described above, kept only as long as stated there, proportionate to the security risk it addresses. Basis: legitimate interest, Art. 6(1)(f), in keeping the service secure.
  • Generate the AI summaries you turn on. Basis: contract, Art. 6(1)(b).
  • Send onboarding emails about setting up your account. Every one carries an unsubscribe link. Basis: legitimate interest, Art. 6(1)(f), in helping you use what you signed up for.
  • Run the referral and discount programs you join or apply to. Basis: contract, Art. 6(1)(b).
  • Improve reliability and comply with valid legal obligations. Basis: legitimate interest, Art. 6(1)(f), and legal obligation, Art. 6(1)(c), as applicable.
  • Understand and improve onboarding and product usage, using the usage statistics described above. This does not identify you and does not affect the service you receive. Basis: legitimate interest, Art. 6(1)(f), in understanding how the site and product are used.
  • Set the measurement cookies and run the web analytics described below. Basis: consent, Art. 6(1)(a). In the EU, the EEA, the UK, and Switzerland we do neither without it.

Service providers

We use a small number of providers to operate RealUptime, each handling only what its job requires:

  • Hosting and database infrastructure in the United States and the EU, with monitoring probes in Canada, the UK, Japan, Singapore, Australia, and Brazil, including replica hosts and encrypted-backup storage. This is where your data lives and runs.
  • A transactional email provider that delivers sign-in, alert, and status-update messages, so it processes recipient addresses and message content.
  • An SMS provider, for status pages that offer text alerts and for the on-call numbers account members add for their own alerts, which processes those phone numbers and the content of the alerts sent to them, and receives STOP/START replies.
  • A payment processor that handles subscriptions and payments. Card details are entered with the processor directly and never reach us.
  • A network and storage provider that serves DNS for realuptime.io, carries traffic to our main site, dashboard, API, and MCP endpoint, routes inbound email to our mailboxes, and stores encrypted backups and browser-check screenshots.
  • An AI provider, used only for accounts that turn on an AI summary feature, which receives the data for the one issue or incident being summarized.
  • A company email provider that holds the messages you send to our support and other addresses.
  • A web analytics provider for our public site and for use of the signed-in dashboard, which receives the records described under "Cookies and tracking": a random cookie identifier, the pages viewed, our funnel events, and campaign data for a visit that arrives through a tagged link. From the dashboard it receives only page addresses with their identifiers replaced, a fixed page title, and step names with fixed labels, never the content of your account. It never receives anything from a status page, and it follows the regional rule described there.
  • Operational tooling: source-code hosting for our deployment pipeline and a paging service that alerts our own on-call operator. Neither holds customer records; both can receive operational alert text about our systems.
  • A public domain-registration (RDAP) lookup service, which receives the domain names you ask us to watch for expiry, and nothing else.

These providers process data on our instructions, and may do so in countries other than your own. Signed-in account owners can see the named list of processors of customer data in account settings, and anyone evaluating the service can request it by email; see the Data Processing Agreement. If you connect Slack, PagerDuty, or a webhook of your own, alert information is sent where you direct it; those are your integrations rather than our providers. We may also disclose information when required by law, to protect the service or its users, or as part of a business transfer. We do not sell personal information, and we do not share it for advertising.

Text messages (SMS)

Where a status page offers text alerts, you can subscribe with your phone number. By subscribing you agree to receive automated text messages from RealUptime about that page: a one-time confirmation of your subscription, then notices when a service you follow goes down, recovers, or has scheduled maintenance. Message frequency varies with the incidents on the pages you follow. Message and data rates may apply. Reply STOP to cancel at any time and HELP for help. Consent to receive text messages is not a condition of any purchase.

Account members can also add their own phone number as an on-call alert channel. We then send automated alert texts, or calls, to that number when a monitor they configured goes down or recovers, and record their consent. The same frequency, rates, STOP, and HELP terms apply, and removing the channel in settings stops them.

Your phone number and your consent to receive text messages are used only to send those messages. No mobile information is sold, and no mobile information is shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent are never shared with any third party; every other category of sharing described in this policy excludes them. The SMS provider listed under "Service providers" processes phone numbers and message content only to deliver the messages and to receive your replies.

Public status pages

A public page can expose the page name, component names, incident text, monitoring state, latency, regions, and timestamps. Do not place secrets, private endpoints, personal information, or confidential incident details on a public page.

III. How we protect information

We implement security measures designed to protect your information from unauthorized access. Your account is protected by your account password and we urge you to take steps to keep your personal information safe by not disclosing your password and by logging out of your account after each use. We further protect your information from potential security breaches by implementing certain technological security measures including encryption, firewalls and secure socket layer technology. However, these measures do not guarantee that your information will not be accessed, disclosed, altered or destroyed by breach of such firewalls and secure server software. By using our Service, you acknowledge that you understand and agree to assume these risks.

Security and international processing

We use technical and operational safeguards appropriate to the current service, but no internet service can guarantee absolute security. RealUptime and its providers may process information in countries different from your own. When we transfer personal data out of the EU, the EEA, the UK, or Switzerland, we rely on the European Commission's Standard Contractual Clauses (and the UK Addendum) or the provider's Data Privacy Framework certification. Email us for a copy.

Security incident notification

If we become aware of a security incident involving personal information, we will investigate, take steps to contain and remediate it, and notify affected customers and authorities where required by law. For personal-data breaches covered by the DPA, we notify the account owner without undue delay and in any case within 72 hours of becoming aware, subject to the limits and exceptions in applicable law.

IV. Your rights regarding the use of your personal information

You have the right at any time to prevent us from contacting you for marketing purposes. When we send a promotional communication to a user, the user can opt out of further promotional communications by following the unsubscribe instructions provided in each promotional e-mail. You can also indicate that you do not wish to receive marketing communications from us in the email settings in your account of the Site. Please note that notwithstanding the promotional preferences you indicate by either unsubscribing or opting out in the email settings of the Site, we may continue to send you administrative emails including, for example, periodic updates to our Privacy Policy.

Your choices and rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal information, to object to or restrict certain processing, and to complain to your local data protection authority. We apply the following to everyone, not only to people in a particular country.

  • Export. Account owners can download their account, monitors, status pages, incidents, subscribers, and API keys (metadata only, never a hash or plaintext) as JSON from account settings, without asking us.
  • Deletion. Account owners can delete their account from account settings; if you signed up without a password, set one under Security first. This cancels any subscription and removes the account and its monitoring data. Security audit entries for the account are anonymized rather than removed, as described under Retention and deletion above. Copies in our encrypted backups age out within 12 weeks, and support correspondence and billing records we must keep are not removed.
  • Status-page and product-update email. Every one of those messages carries a one-click unsubscribe link, which takes effect immediately.
  • Status-page text alerts. Reply STOP to any alert to stop receiving SMS immediately; we honor it the same way a carrier requires. Unsubscribing by email deletes the address. Replying STOP keeps the number on a suppression list so we do not text it again; to have that number erased as well, email support@realuptime.io.
  • Measurement choice. You can change your answer at any time on the control below this list, wherever you are. Turning measurement off deletes the measurement cookies from this browser and stops web analytics for it, including outside the regions where we ask first.
  • Anything else. For access, correction, or a request the dashboard does not cover, email support@realuptime.io. Requests are handled by a person against a written checklist, not by an automated system, and we aim to respond within 30 days. We will ask you to verify control of the account email before acting on a request.

US state privacy rights

If you live in California or another US state with a comprehensive privacy law, the rights above apply to you under those laws too, including the rights the CCPA and CPRA call access, correction, deletion, and portability. RealUptime does not sell personal information and does not share it for cross-context behavioral advertising, so there is nothing to opt out of under “Do Not Sell or Share”. To make a request, use the self-serve controls in account settings or email support@realuptime.io; we verify requests against the account email and never charge for them or treat you differently for making one. An authorized agent may submit a request for you with proof of your permission.

Retention and deletion

Account and configuration data is retained while needed to provide the service. Raw per-check monitoring results are our own measurements of your endpoint, six fields recording what our probes saw and when, and we keep them for up to three years on every plan, free included. What your plan governs is how far back you can see and export them in the product: 30 days on Free, and 90 days on Growth and Scale. Older results are hidden from those views rather than deleted, and moving to a plan with a longer window reveals them. Response snapshots, the copy of what a page actually returned, are held far more briefly because that content is yours and your visitors', not our measurement: 30 days for a snapshot taken while a check was failing, and 7 days for one taken when it recovered. Daily and hourly uptime and latency summaries derived from raw results are kept longer term to support the history shown on status pages. Error events are retained by plan: 14 days on Free, 90 days on Growth, and 180 days on Scale, then deleted. Raw server-agent metric samples are retained for 7 days, with longer-term rollups kept for history. Raw outage-tracker problem reports are pruned after 7 days; only aggregate counts remain. Operational logs may be kept for a shorter period based on troubleshooting and security needs. Some records may be retained when required for security, billing, or legal reasons.

Two kinds of account are deleted automatically. An account whose email address is never confirmed is deleted 30 days after signup; it gets one reminder with a fresh link about a day after signing up. A free account with nothing set up (no monitors, status pages, error projects, or server agents) that nobody has signed in to for a year gets an email saying it will be deleted in 30 days, and is deleted then unless someone signs in. Accounts with a paid plan or billing history are never deleted this way. Deletion works the same as deleting an account yourself, described under Deletion below.

The security audit log is the one record we keep indefinitely. It records what happened on an account and when: sign-ins, setting changes, billing events, and any time a member of our staff accessed the account. Those entries cannot be edited or deleted, by us or by anyone else, which is what makes them worth having. Because we cannot delete them when an account closes, we anonymize them instead: the email addresses, IP addresses, and device information they carry are replaced with a fixed placeholder, and what remains is the bare record that an event of that kind happened at that time.

Other periods: copies of emails we send are kept for 90 days. A subscriber a status-page owner imports who never confirms is deleted after 30 days, and a phone number that never confirms after 24 hours. Browser-check screenshots are kept 14 days and failure traces 30 days, and those of a deleted check or account are removed within about an hour. Daily API usage records and the network an API key was used from are kept 400 days. Support requests and program applications are kept after an account closes so we can answer follow-ups. Encrypted backups age out within 12 weeks.

V. Links to other websites

As part of the Service, we may provide links to or compatibility with other websites or applications. However, we are not responsible for the privacy practices employed by those websites or the information or content they contain. This Privacy Policy applies solely to information collected by us through the Site and the Service. Therefore, this Privacy Policy does not apply to your use of a third party website accessed by selecting a link on our Site or via our Service. To the extent that you access or use the Service through or on another website or application, then the privacy policy of that other website or application will apply to your access or use of that site or application. We encourage our users to read the privacy statements of other websites before proceeding to use them.

VI. Changes to our privacy policy

The Company reserves the right to change this policy and our Terms of Service at any time. We will notify you of significant changes to our Privacy Policy by sending a notice to the primary email address specified in your account or by placing a prominent notice on our site. Significant changes will go into effect 30 days following such notification. Non-material changes or clarifications will take effect immediately. You should periodically check the Site and this privacy page for updates.

VII. Contact us

If you have any questions regarding this Privacy Policy or the practices of this Site, please contact us by sending an email to support@realuptime.io.

The controller for the personal data described in this policy is RealUptime LLC, a New Jersey limited liability company, doing business as RealUptime. Privacy questions and data requests can be sent to support@realuptime.io, or by mail to:

RealUptime LLC
PMB 1078, 2230 Route 70 W STE 2
Cherry Hill, NJ 08002
United States

Last Updated: This Privacy Policy was last updated on October 4, 2026.