Security
Ping&Bump never shows how much someone answers.
It finds the colleague who fits a question. No screen, export or API has a per-person count of pings, answers or declines, and no setting adds one.
The line
An admin can see
- Which sources are connected.
- Questions nobody here could answer.
- Who is in the workspace.
Nobody can see
- How many pings, answers or declines any one person has.
- How fast someone answers, or how often they said busy.
- Anything that ranks two named people against each other.
- Who a question went to before the person who answered it.
- Certifications. None today. No SOC 2, no ISO 27001, no penetration test. If that is a blocker, it is one now.
- Where data lives. The database is in Paris and the compute in Dublin. Model inference isn't pinned to a region.
- Model retention. Model calls run under each provider's own retention terms, and none of them train on your text. Zero data retention is a switch in the configuration, not a rewrite, and the pages here say which way it is set.
- Admin control of sources. Nothing is read until an admin connects a source and turns on what it may read, one project, repository or channel at a time.
- Your own card. Everyone can open the card Ping&Bump holds on them, see the evidence behind it, and stop being findable.
The DPA and the sub-processor list come with the first conversation about a pilot. Ask and we send them.