Privacy policy

What we collect

When you sign up: your email address and your name. When you create monitors: the URLs and configurations you give us. When you use the dashboard: standard server logs (IP, user agent, timestamps).

When the engine probes your services: the response status, response time, and any error text from the probe. We do not store response bodies.

What we don't collect

We don't sell data. We don't train AI models on customer monitoring data. We don't store the bodies of the HTTP responses we probe. We don't run advertising or retargeting pixels, and we don't load anything at all inside the app that watches what you do with your monitors.

Where data lives

Your application data — workspaces, users, monitors, incidents, probe results — is stored in a managed Postgres instance in the EU (AWS Frankfurt), and the app is served from Frankfurt too. Storage is one thing and processing is another, so plainly: our probe machines run in Amsterdam, Virginia and Singapore, which means the URL being checked and the response we get back are handled in the US and Singapore before the result is written to the EU database. That is what multi-continent consensus requires. Mercury sends the evidence for an incident to Anthropic in the US to write its summary. Every vendor above is a US company, including the ones storing data in Europe.

Who can see it

Only members of your workspace, your Repose admin (for support, only when you explicitly ask), and our SOC 2-targeted set of infrastructure providers (Neon for Postgres, Vercel for app hosting, Fly.io for the probe machines, Resend for email, Cloudflare for DNS, Stripe for billing, Anthropic for the Mercury incident summaries, and Slack, Discord or Teams if you connect them). Page counts on our public pages go to an analytics tool we host ourselves, not to a vendor, and it sees public pages only — never your monitoring data, and never anything behind a login.

How long we keep it

Application data: until you delete your account. Individual probe results: 30 days, on every plan. Daily uptime and latency totals, incidents and the alert decision trail: until you delete your account. The public down checker keeps the URL you typed and its three results for 24 hours; it never stores your IP address, only a salted hash of it so the rate limit can count. The alert_decision audit trail is kept forever (or until you delete the workspace) — that's what powers the "why this fired" tab.

Your rights

You can export everything you've given us (per workspace) at any time. You can delete your account and all associated data via the dashboard. We respond to deletion requests within 7 days.

Cookies

We use two essential cookies and nothing else: one for your login session, and — only if you belong to more than one workspace and switch between them — one that remembers which workspace you were last in. Both exist to make the app work and neither tracks you.

We set no analytics or advertising cookies, on any page. Our public pages — the marketing site, sign-in, sign-up, this page and the terms — load Umami, an open-source analytics tool we run ourselves at stats.repose.sh. It counts page views and a handful of button presses — “Start free”, running the live check and how it ended, submitting the sign-up form — and how fast the page loaded, without storing anything on your device and without building a profile of you. It never receives the address you typed into the check or the sign-up form, drops everything after the “?” in an address before counting it — except campaign tags like utm_source, which only say which link brought you — and doesn't count you at all if your browser sends Do Not Track. There is nothing to consent to, which is why you aren't being asked.

It doesn't run inside the signed-in app, so nothing outside the app sees the URLs of your dashboard, monitors or incidents — those addresses name your infrastructure. It doesn't run on password-reset or invite links, which carry a single-use token in the address. And it doesn't run on the status pages we host for customers: those visitors are our customers' audience, not ours.

The numbers go to our own instance and nowhere else: no analytics vendor receives them. They're stored in the EU (Frankfurt), in a database that is separate from the product's. If we ever needed something that couldn't work this way, you'd get a banner and this page would say so the same day.

Contact

Email [email protected] for anything related to data, this policy, or your rights under GDPR / CCPA.