PingStuff
  • How It Works
  • Pricing
  • Tools
Sign In

DraftComplete draft prepared for legal review — these terms have not yet been reviewed by counsel and may change before they become final.

Privacy Policy

What we collect, why we collect it, how long we keep it, and the choices you have over your data — in plain English.

Status: draft for legal review · Last updated 3 August 2026

1. Who we are and what this covers

PingStuff checks whether websites and servers are healthy and alerts their owners when something goes wrong. This policy explains how we handle personal data when you visit pingstuff.com, run a free check, or use the monitoring service.

PingStuff is operated by 9950931 Canada Inc., carrying on business as PingStuff.com, 2240 University Ave E., Waterloo, Ontario N2K 0A9, Canada. Our servers are hosted by Vultr in Chicago, USA. That means your data is processed and stored in the United States, even if you are in Canada, the EU, or elsewhere — it is subject to US law while it is there. If cross-border processing is a problem for you, please don’t use the service.

2. What we collect

We collect the minimum we need to run the service. Here is the full inventory — if it isn’t listed here, we don’t collect it.

  • Your account. Your email address (required), and optionally your first name and an organization name. Sign-in is a passwordless magic link sent to your email — we never store passwords because there are none.
  • Alert contacts you add. A label, an email address, and optionally a phone number for each person you want alerted. Phone numbers are verified with a one-time code; the code is stored hashed, never in plaintext, and the number of attempts is capped.
  • What you monitor. The website URLs and hostnames you choose to monitor.
  • Check results. Technical metadata from checking your own monitored sites: DNS, TCP, TLS, and HTTP results — status codes, timings, certificate metadata, redirect chains, response headers, and a small excerpt of the response body that we keep to help diagnose errors. To be clear: this is data about your site’s health, collected because you asked us to check it.
  • Anonymous free checks. If you run the free instant check without an account, we keep the URL you checked and a snapshot of the result so we can show you a shareable report. These are automatically deleted after 7 days. We also keep a separate, longer-lived usage record of which website was checked and the result — with no IP and nothing that identifies you — for up to 90 days, so we can understand aggregate use of the free checker.
  • IP addresses and sign-in records. We use visitor IP addresses transiently for rate limiting. When you sign in, our authentication system also records the full IP address and browser user-agent string of that sign-in with your session, as a security measure — these are kept while your account exists and are deleted with your account. Where we keep longer records — the access log for shared reports and our abuse-prevention ledger — we store only a coarsened form (the surrounding network — /24 for IPv4, /48 for IPv6 — not your full address). And when you consent to SMS alerts, we keep the IP address recorded at the moment of consent as proof of that consent.
  • Email and SMS message logs. Which messages we sent, to whom, and whether they were delivered — and, for SMS, the texts you send to us (commands and any other texts you send). For SMS this includes the message body in both directions — except verification codes, which are never logged. These logs are automatically deleted after 13 months.
  • Billing (when paid plans are live). Payments are processed by Stripe. We never see or store your card number — we store your subscription status, quantity, and billing period, the Stripe identifiers for your customer and subscription records, and the raw billing-event records Stripe sends us, which we keep so we never process the same payment event twice and can investigate billing questions.
  • Product analytics and error tracking. Server-side product events (PostHog, when enabled), redacted so they never contain full customer URLs; and error tracking (Sentry), which is active and receives error reports and the diagnostic context attached to them. There are no analytics cookies or tracking scripts in your browser — see our Cookie Statement.

3. Why we use it

We use the data above for exactly four things:

  • Providing the service — running your checks, showing your dashboards and reports, and sending the outage, recovery, digest, and certificate-expiry alerts you set up.
  • Support — answering your questions and investigating problems you report.
  • Security and abuse prevention — rate limiting, blocking abusive use of the free checker, and keeping tenants isolated from each other.
  • Legal compliance — for example, keeping SMS consent records and responding to lawful requests.

And what we don’t do: we show no ads, we never sell personal data, and we send no marketing messages of any kind — every email and text we send is operational, triggered by something you set up.

4. Who we share it with

We share data only with the service providers (subprocessors) we need to operate — hosting, email delivery, SMS delivery, payments, analytics, and error tracking. The authoritative, always-current list is our Subprocessors page. We do not share your data with anyone else, with one exception: legal demands, which we handle as described in our Law Enforcement Requests policy.

5. How long we keep it

Short version: check data is kept up to about 14 months so you can see year-over-year trends, anonymous checks vanish in a week, and compliance records are kept as long as the law expects. The full detail lives on our Data Retention page; here is the summary of what the system does today:

DataKept for
Raw check resultsUp to about 14 months
Aggregated statistics (hourly/daily rollups)Indefinitely (statistical, not raw data)
Anonymous free-check reports7 days, then auto-deleted
Email and SMS message logs (messages we send and texts you send us)Up to 13 months
SMS consent and opt-out (STOP) recordsIndefinitely, as legally required proof of consent and of your opt-out — kept keyed to the phone number, and unlinked from your organization if you delete your account
Audit logs24 months

When you delete your account (section 6), all of your organization’s data is permanently deleted after the 30-day grace period — section 6 lists the narrow exceptions. Copies also linger in backups until they rotate out: backups on our own server rotate after 14 days, and encrypted off-site copies are kept for up to 30 days, so purged data leaves every backup within roughly a month of the purge.

6. Your rights and choices

Most of these are built into the product, no email needed, and we honor access, correction, and deletion requests from anyone, regardless of where you live.

  • Access and portability. Download a copy of your organization’s core data — organization details, members, monitors, incident history, alert contacts, daily uptime statistics, and a subscription summary — as JSON, self-serve, any time, at pingstuff.com/app/export. The export covers your most recent records (up to 1,000 monitors, 2,000 incidents, 1,000 contacts, and 5,000 daily uptime rows) and does not include raw per-check results or message logs — if you need something it doesn’t cover, ask us via the contact form at pingstuff.com/contact and we will provide a copy of what we hold.
  • Correction. Update your name, contacts, and monitors directly in the app.
  • Deletion. The account owner can delete the account in-app. Deletion starts a 30-day grace period during which the account is inoperable and monitoring stops — you can cancel within those 30 days if you change your mind. After that, all of your organization’s data is permanently deleted, and for every member whose only organization this was, so is their sign-in identity: the user record (email, name, and verified phone number, if any), sign-in sessions, linked authentication records, and phone-verification records. A member who also belongs to another organization keeps their sign-in identity for that other organization. A few narrow things survive deletion: SMS consent and opt-out records, kept keyed to the phone number and unlinked from the deleted organization as legally required compliance proof; the global STOP suppression list, so we never text a number that opted out; where billing was used, the raw payment-processor (Stripe) event records, which are not tied to one organization; and copies in backups until they rotate out (section 5).
  • Stopping texts. Reply STOP to any SMS and all texts stop immediately — see the SMS Terms.
  • Complaints. Please raise concerns with us first — email privacy@pingstuff.com or, more reliably while our mailboxes are still being set up, the contact form at pingstuff.com/contact. If you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada or your local data-protection authority.

7. How we protect it

The full, honest description of our security posture — including what we do not have yet — is on our Security page. The highlights: passwordless magic-link sign-in (no password database to steal), strict server-side tenant isolation so organizations can never see each other’s data, a guard that stops the checker being aimed at private or internal networks, encrypted transport (HTTPS/TLS) everywhere, and nightly database backups that we have actually restore-tested. We don’t claim security certifications we don’t hold.

8. Children

PingStuff is a business tool for adults. You must be 18 or older to use it, and it is not directed at children. If we learn we hold personal data of someone under 18, we will delete it.

9. If something goes wrong

If a data breach creates a real risk of significant harm to you, we will notify you and the relevant authorities without undue delay, tell you plainly what happened and what data was involved, and explain what we are doing about it.

10. Changes to this policy

If we change this policy, we will update the date at the top. If a change meaningfully reduces your privacy, we will tell account holders by email before it takes effect.

11. Contact

Privacy questions and data requests: email privacy@pingstuff.com, or use the contact form at pingstuff.com/contact — the contact form is currently the most reliable channel.

PingStuff

Know when your website breaks. Know what to do next.

Product

  • How It Works
  • Pricing
  • Tools
  • About
  • Contact

Resources

  • Guides
  • Announcements
  • Security

Legal

  • Terms
  • Privacy
  • Trial & Billing
  • SMS Terms
  • Acceptable Use
  • Cookies
  • Data Retention
  • Subprocessors
  • Law Enforcement

SMS alerts are powered by AIUCAAS, a Canadian communications platform, over a Fibernetics carrier route.