Who Sees My Answers?

Who sees my answers?

Short answer: nobody sees your name next to your answers. Not your boss, not your team leader, not the admin team. Your organisation sees patterns across your team, never "Sarah rated Copilot 2/5 on Tuesday".

This is deliberate. It's what makes the answers worth collecting in the first place.

What admins and team leaders actually see

Your organisation's Owners, Admins and Group Leaders can look at dashboards and reports that show:

• Averages. "The team rated Copilot 4.2/5."
• Totals. "142 hours saved across the team this month."
• Trends. "Satisfaction with Claude has risen from 3.8 to 4.4 over 8 weeks."
• Comments. The free text you leave, word for word, with no name attached.

That's it. There's no "responses by person" view. There's no CSV export with names in it. The system doesn't even send your name to the admin's browser when they load the reports page. The data isn't there.

Can I see my own answers?

Yes. Log in to The GAiGE at any time and your personal dashboard shows your own pulses and responses, the tools you rate highest, and your personal hours-saved estimate. That's your data; you can always see it.

Who can't see your answers

• Your team leader. Team-level aggregates only. They can spot patterns ("three people in Marketing don't feel confident with Jasper"), but not which three.
• Your colleagues. Their dashboards show their own data, not anyone else's.
• Anyone outside your organisation. Your data never leaves your organisation's account in The GAiGE. We don't sell it, share it, or compare it across companies.
• The GAiGE staff. We have access to logs and aggregate data for support, but we don't read individual pulse responses, and we don't build profiles of individuals.

When you're asked something just once

Some pulses are one-offs. Instead of coming round every week, they open, you answer once, and they close. Organisations use them to take a starting picture: what AI people already use, what would help most, what's getting in the way.

They work a little differently, so here's what to expect.

You're asked once, and then you're done. The moment your answer reaches us, that pulse stops being offered to you. That holds even if you reinstall your browser or move to a new laptop.

You'll be reminded, and the reminders get closer together. If the organisation has set a date it needs answers by, the pulse comes back about weekly while that's more than ten days off, every few days inside ten, and daily in the last stretch. Never more than once a day, whatever the arithmetic says. A one-off with no date sits on the middle setting, so nothing can ask you daily indefinitely.

The words don't change as the date gets nearer. The frequency does the work. There's no countdown, no "last chance", nothing red.

The reminders come to you, and only to you. Nobody is emailed about whether you've answered. Your manager isn't told, and there's no list anywhere of who hasn't answered yet.

You can always leave. Every screen offers a way out: snooze it for a few hours, choose Later, or just close it. Close a one-off half way through and it goes back in the queue rather than being used up, and it tells you so. You're never held in a questionnaire.

On some one-offs you can't skip an individual question. Where an organisation has turned skipping off, the "Skip question" button is gone from the questions that need an answer. Optional questions keep it, and the open "tell us in your own words" questions are always optional. Leaving the whole pulse for later is always available. The two are different on purpose: a half-answered starting picture is a hole nobody goes back and fills, but nothing about this should ever trap you mid-task.

What your organisation sees at the end

Three things, and none of them is a name.

• How many people have answered. A percentage and a count ("26 of 42 people"). Not which 26.
• How each question was answered. Charts of the spread, and a 0-100 reading for the scale question.
• What people wrote. The open answers, grouped with other answers that said something similar, most common first. Each group can be opened to read the answers underneath it, word for word.

A question needs five answers before any of it appears. Below that the report says how many people have answered and shows nothing else. The same floor applies to teams: a team where fewer than five people have answered shows its name and stops there, and a team the pulse reaches fewer than five people in is left out of the list entirely.

Two things worth being straight about

Your words are read. On a one-off, the open answers are the whole point, so they will be read closely and quoted, exactly as you typed them. Your name isn't attached, and a heading in that report is always something a real person wrote rather than a summary we've invented. But write knowing it will be read, which is the same advice as the caveat below.

In a very small team, a count is close to a name. "Five of six have answered" doesn't say who the sixth is, but in a team of six it doesn't hide much either. Nothing about what you said is exposed by that number, and there's still no list of who has and hasn't answered anywhere in the product. It's a limit of arithmetic, not a gap in the promise, and it's worth knowing about if you're in a small team.

One caveat: free-text comments

When you leave a free-text comment ("any other comments?"), your name is not attached. But if the comment itself identifies you, there's nothing we can do about that.

Example of a safe comment:

"Copilot's autocomplete is great for boilerplate but keeps suggesting deprecated APIs in our Python 3 codebase."

Example of a comment that identifies you:

"As the only person on the procurement team who uses Jasper, I find it frustrating…"

If staying unnamed matters to you, keep the comment about the work, not about your specific situation. When in doubt, err on the side of brevity.

What about negative or critical answers?

Including negative responses (low ratings, "I lost time because of it", blunt free text) is explicitly fine and won't be used against you. Since admins don't see who said what, they can't retaliate even if they wanted to. The whole point of the pulse is to surface signal, and the negative responses are often the most important.

Is this actually anonymous?

Not quite, and it's worth knowing the difference. The database still stores which pulse response came from which user. That's how your personal dashboard works, and how we make sure you aren't asked the same one-off twice. But nobody in your organisation ever sees that link. It's a technical fact, not a reporting fact.

If the nuance matters to you (say you're in a regulated industry), ask your admin to show you the Reports page. They can demonstrate that there's no way to filter or group by individual user.

If my company needs per-person signal

They can do it the open way: put one person in their own group. Group-level reports would then effectively show that individual's data, but the admin has to actively create that group, so it isn't a hidden feature. You'd be able to see you were in a singleton group on your own profile.

The default is aggregated. Per-person is possible, but it has to be deliberate.

Related: What's a pulse? · Will my answers affect my performance review? · What data is collected and how it's used