Ping and Bump

Privacy

What Ping&Bump holds, and how to make it stop.

Written from the code. Where a fact needs a lawyer, it says so at the bottom instead of guessing.

What it holds

  • Your account. An email address, and the account identifier Google or Microsoft returns if you sign in with one. There are no passwords in Ping&Bump. Sessions are cookies.
  • Your work, inside a company workspace. Whatever the sources your admin connected can read: tickets, pull requests, documents, messages in the channels they included. It becomes one card per person, with the citations behind it. That card is how Ping&Bump decides who fits a question. It holds no productivity score and no activity count.
  • Questions and who they went to. Each question is stored with who asked it and where. Each ping is stored with who it went to and what they pressed: answered, took it, not my area, busy, or no reply. After 30 days the person is removed from the ping and only the question's outcome stays. None of it is shown per person, to anyone, admins included.
  • Answers. Every answer is kept with who gave it. It is available across the workspace, unless the question came from a private channel or was marked private by the asker. A private-channel answer stays with that channel’s members; an answer marked private stays with the asker and whoever answered. The author can edit or withdraw it on their page.
  • The pilot form. Your name, work email, company, and what you wrote about the last question that waited. We keep it so Mihkel can write back.

Where it runs

The database is in Paris and the server functions run in Dublin, both in the EU. The model is the exception: a question and the evidence behind it go to whichever provider can serve it, and we don't control where that is. The provider keeps them only under its own terms, which are on the sub-processor list, and none of them allow training on your text.

Who else sees it

The database host, the hosting provider, and the model gateway with the providers behind it. Slack, because that is where questions are asked and answered. Jira, GitHub and the other sources only if your admin connected them; a workspace that connects none sends them nothing.

The site counts page views with Vercel Web Analytics, which sets no cookie. There is no session recording, no tag manager and no advertising pixel.

What you can do

  • See what Ping&Bump holds on you in a workspace. Your card is a page you open.
  • Stop being findable from your card. Nobody can be pinged who can't be found.
  • Ask for everything to be deleted, by writing to the address below.

What isn't settled yet

The lawful basis for each kind of processing, how long each thing is kept beyond the 30 days above, and the transfer mechanism for model inference. Those need a lawyer and aren't written yet. If one of them decides whether you can use Ping&Bump, ask and you'll get the real answer.

Mihkel Hõbemägi, Nõmme, Tallinn, makes Ping&Bump. Questions and deletion requests: hello@pingandbump.com. See also Security and Terms.