{"document":"RealUptime Data Processing Agreement","url":"https://realuptime.io/dpa","version":"2.6","effectiveDate":"2026-11-13","subprocessors":[{"name":"Fly.io","service":"Runs the regional checking probes, and terminates encrypted connections for status pages served on a customer's own domain.","data":"Monitor configuration, target URLs, the responses probes fetch, and probe results; for status pages on a customer's own domain, visitors' requests and IP addresses in transit.","location":"United States (Ashburn, Chicago, San Jose), Canada (Toronto), United Kingdom (London), Germany (Frankfurt), Japan (Tokyo), Singapore, Australia (Sydney), Brazil (Sao Paulo): probes in each listed region; the custom-domain edge in Ashburn."},{"name":"OVHcloud","service":"Former host of the production database and two operations hosts, out of service since November 9, 2026 and kept only until they are wiped and deleted.","data":"A copy of customer data as of November 9, 2026, until those servers are wiped.","location":"United States (Vint Hill, Virginia; Hillsboro, Oregon; and one further OVHcloud data center in the United States)"},{"name":"Amazon Web Services","service":"Hosts the web application, the API and MCP server, Errors ingest, the browser-check runner, alert delivery and RealUptime ID; the production PostgreSQL database; the operations host that deploys and backs up the service; and a second offsite copy of database backups, encrypted before upload.","data":"All customer data.","location":"United States (Northern Virginia, us-east-1)"},{"name":"Resend","service":"Primary transactional email delivery (sign-in, alert, status-page, and incident messages).","data":"Recipient email addresses and message content, which can include monitor names, incident text, and status-page names.","location":"United States (sends through Amazon SES, us-east-1)"},{"name":"Anthropic","service":"AI-generated summaries, used only for accounts that turn on Errors issue summaries (per project, in Errors settings) or incident insights (per account). Not used otherwise.","data":"For an issue summary, that issue's already-scrubbed stack trace, breadcrumbs, tags, and release metadata, after both the default and any account-configured scrub rules have run. For an incident insight, the incident's timeline, affected monitors and regions, error counts, and the status of vendors the account watches. No data is sent for accounts that leave both features off.","location":"United States"},{"name":"Sent","service":"SMS delivery to status-page subscribers who opt in to text alerts and to the phone numbers on SMS notification channels an account configures, and receipt of inbound STOP/START opt-out replies.","data":"Status-page subscriber and notification-channel phone numbers in E.164 format, and the message content of alerts sent to them.","location":"United States (Standard Contractual Clauses apply to transfers out of the EEA and the UK)"},{"name":"Cloudflare","service":"Network edge and TLS termination for realuptime.io, www.realuptime.io and mcp.realuptime.io; object storage for browser-check screenshots and failure traces; DNS; offsite storage for database backups encrypted before upload.","data":"All traffic to those hostnames in transit, including sign-in, API and MCP requests and responses; browser-check screenshots (kept 14 days) and failure traces (kept 30 days); database backups as ciphertext only.","location":"Cloudflare's global network (traffic enters at the edge nearest the visitor); stored objects use Cloudflare's automatic placement and are not pinned to one jurisdiction."},{"name":"Microsoft Azure","service":"Cloud virtual machines for capacity testing and for running new versions of our services side by side with production before they replace it.","data":"During a side-by-side test: copies of requests sent to Errors ingest, heartbeat and agent endpoints (error events, agent metrics, and the keys and tokens that authenticate them); copies of read requests to the REST API and the answers they received (monitor, incident, maintenance, status page and alert channel settings, and the API keys that authenticate them); and a read-only copy of the account records those answers are built from. All of it is held in memory only, never written to disk, and deleted with the test machine within 14 days. Synthetic test traffic otherwise.","location":"United States (East US, West US 2); load-generating machines in other Azure regions carry synthetic traffic only."}]}