01
Your answer carries no name
A response is stored with the scores and text you enter — and nothing that points back to you. No name, no email, no member id. There is deliberately no column that says who wrote it.
If you've been asked to answer a Pulsings check-in, this is the honest, plain-language version of what the person running it can and can't see. The short answer: they see how the team is trending, never who said what — and that's enforced by how the data is built, not just a promise on a page.
Answer honestly. Nothing you write is stored against your name, and the organizer only ever sees the team’s patterns — never a single person’s response.
A privacy policy is a promise. These are the mechanics underneath — the reasons the promise holds even if someone wanted to break it.
01
A response is stored with the scores and text you enter — and nothing that points back to you. No name, no email, no member id. There is deliberately no column that says who wrote it.
02
We record that an invite was used so nobody gets nagged twice — but that record lives separately from your answers and is never joined to them. Who finished and what was said are two lists that never meet.
03
Responses are dated, not timestamped to the second. The order answers arrived can't be lined up against who happened to be online when, so nobody can reconstruct a sequence.
04
If fewer than 3 people answer a cycle, the organizer sees only a count — no scores, no themes, no quotes. The content isn't withheld behind a warning; it simply isn't assembled, so a small group can't be singled out.
05
Comments are stripped of names, emails, and other identifiers, then synthesized into themes across everyone — never shown to the organizer as a raw, attributable list.
06
Your data stays in the EU, and the AI and email providers we use operate under zero-retention, no-training terms — your words aren't kept by them or fed into a model.
The anonymity that earns your team’s candour applies to you too: there is no admin override, no “just this once” unmask. What you get back is a synthesized read — trends over time, themes, and the concrete changes your team asked for. That constraint is exactly why the answers are worth reading.
No. Answers are stored with no link to the person who gave them, and the organizer's view only ever shows aggregates — trends, themes, and the changes the team asked for. There is no screen, export, or query that reveals a single person's response, because the connection between you and your answer is never written down in the first place.
Free-text answers are scrubbed of names, emails, handles, and numbers, then synthesized into themes across the whole team. The organizer sees the pattern and, at most, a representative anonymized quote — never a raw list of comments that could be matched to people by wording or detail.
Especially then. Below 3 responses a cycle shows nothing but a count — the scores, themes, and quotes are never generated. At two responses, one person could subtract their own answer to infer the other's; 3 is the floor that defeats that, and it isn't configurable.
No. A response is not tied to an IP address, a cookie, or any device identifier. We don't store a stable id we could use to recognize you across cycles, which is also why we ask you not to submit twice — we honestly can't tell if you have.
That's the one disclosed exception, and you're told about it before you use it. An urgent note is reworded and stripped of identifying detail before the organizer sees it — and if it can't be de-identified, it's dropped rather than shown. It exists so a genuine crisis isn't lost to anonymity, and it's always your choice to write one.
No. Because responses are dated rather than second-stamped and hold no identity, there's no timeline to correlate. Whether you answer first or last, on Monday or Friday, the stored answer looks the same and points to no one.
Start a recurring anonymous pulse in minutes. Your first two cycles are free, and no credit card is needed to begin.