Skip to content
Ping Bouncer
How it works Pricing FAQ
Sign in
← Back to the door

Privacy Policy

Last updated October 2, 2026

The short version

Ping Bouncer is a routing layer: it watches for alerts from the tools you point at it, decides where each one should go based on rules you write, and sends it on. We don't read your alerts for our own purposes, we don't sell or share data with advertisers, and we don't use anything that passes through Ping Bouncer to train models. Alert content lives in your events log for 30 days so you can see what happened, then it's deleted. The rest of this page spells out the details.

Who we are

Ping Bouncer is operated by Svelte Services LLC ("Ping Bouncer", "we", "us"). This policy covers pingbouncer.com and the Ping Bouncer app at app.pingbouncer.com. Questions about this policy or your data go to privacy@pingbouncer.com.

What we collect

Three categories, each handled differently:

  • Account data. When you sign up, our authentication provider, Clerk, collects your email address and whatever sign-in method you choose (password, Google, etc.). We store your workspace name, the routing rules you write, and the destinations you connect. We don't ask for more than that to run the service.
  • Alert data. The content of the pings you route through Ping Bouncer: the payload a source sends, which rule matched it, and where it was delivered. This is the data your own tools generate about your own systems — we're a pass-through, not the source.
  • Usage and infrastructure data. Our host, Cloudflare, logs standard request metadata (IP address, timestamps, request paths) for security and abuse prevention, the way any web infrastructure provider does. Our marketing site uses Cloudflare Web Analytics, which is cookieless and doesn't collect personal data or track you across sites.

How alert data is handled

Alert data is processed to do one thing: match it against your rules and deliver it to the destinations you've configured (Slack, Linear, incident.io, a webhook you own, or whatever else you've connected). That delivery is between your source and your destination — we move it, we don't repurpose it.

We keep a record of each alert in your events log — what arrived, which rule matched, and whether delivery succeeded — so you can audit what happened. Those records are retained for 30 days and then permanently deleted on a rolling basis. We don't keep a longer archive, and we don't copy alert content out of that log for analytics, product improvement, or any other purpose.

Nobody at Ping Bouncer reads your alert content as a matter of course. The only exception is if you explicitly ask us to look at specific events to help debug a problem, and even then we only look at what you point us to.

Who we share data with

We use a short list of subprocessors to run the service, and nobody else:

  • Cloudflare — hosting, network security, and (for the marketing site only) cookieless analytics.
  • Clerk — authentication, so we never handle your password directly.
  • Your own destinations — the tools you explicitly connect (Slack, Linear, incident.io, a webhook, etc.) only receive the alerts your rules route to them. You control that list and can disconnect a destination at any time.

We do not sell personal data or alert data, and we do not share it with data brokers, advertisers, or anyone outside this list.

Cookies

The app sets one session cookie, from Clerk, to keep you signed in. The marketing site sets no cookies — Cloudflare Web Analytics works without them. We don't use advertising or cross-site tracking cookies anywhere.

Data retention and deletion

Alert and events-log data: 30 days on a rolling basis, then deleted automatically. Account and configuration data (your workspace, rules, connected destinations): kept while your account is active. If you delete your account, we delete this data within 30 days, except where we're required to keep billing records for legal or tax reasons.

You can request deletion or an export of your account data at any time by emailing privacy@pingbouncer.com.

Security

All traffic to and from Ping Bouncer is encrypted in transit (TLS). Webhooks we send to your destinations are signed so you can verify they came from us. Access to stored data is limited to what's needed to run the service. No system is unbreachable, and we'll tell you if something changes that.

Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal data, or to object to or restrict how we process it. We honor these requests regardless of jurisdiction — email privacy@pingbouncer.com and we'll take care of it.

International data transfers

Our infrastructure providers (Cloudflare, Clerk) operate globally, which can mean your data is processed in a country other than the one you're in. We rely on those providers' own safeguards for cross-border transfers and choose providers that take this seriously.

Children's privacy

Ping Bouncer is a business tool and isn't directed at children. We don't knowingly collect data from anyone under 16.

Changes to this policy

If we change this policy in a way that matters, we'll update the date at the top and, for material changes, email account holders before they take effect.

Contact

Svelte Services LLC. For anything privacy-related: privacy@pingbouncer.com.

Ping Bouncer

Made for the people who carry the pager. © 2026 Ping Bouncer