30‑second evidence board

ANONYMITY REALITY CHECK

Most “anonymous” survey tools still track people.
Wellness Pulse doesn’t.

Scan this board like an airport security screen. If a platform collects IPs, cookies, logins, or identifiers, it is not end‑to‑end anonymous—no matter what the marketing page says.

The Ultimate Test: Ask Your Provider This Question

Government putting gun

"If tomorrow the government forces you to tell us who responded to what question, can you do it?"

Most Providers
Yes. They can match IP addresses, cookies, login IDs, and device fingerprints to reveal who said what.
Wellness Pulse
No. We cannot do it. The data simply doesn't exist—we never collect identifying information in the first place.
Evidence board: what platforms actually collect

Focus on the red dots and “NO / MIXED” badges—those are the silent identity leaks: IP logs, cookies, login links, and response‑level identifiers.

Green = architecturally anonymous · Red = trackable by design
Platform
Overall Can anyone realistically re‑identify people?
IPs & Device IP logs, device fingerprints, geo
Cookies & Tracking Analytics, cross‑session IDs
Login / ID Links Emails, SSO, per‑person URLs
True by‑design anonymity? Anonymous even if admin mis‑configures
Wellness Pulse
Architectural anonymity | QR code native
YES End‑to‑end anonymous

No Google logins, no cookies, no personal IDs, IPs hashed one‑way.

IP hashed, not stored in clear

Cannot be reversed to a person.

No cookies, no session tracking

Each pulse is a standalone event.

No logins, no per‑user links

Nothing to tie a response to a person.

YES Anonymous by architecture

You can’t accidentally turn anonymity off.

Qualtrics
Research‑grade survey suite
MIXED Depends on admin settings

Default: IPs & metadata collected unless explicitly disabled.

IPs & device info logged

“Anonymize response” must be manually enabled.

Cookies & analytics scripts

Browser identifiers can still persist.

Contact‑list links per person

Unique URLs can reveal exactly who responded.

NO Not anonymous by default

A single mis‑click in settings breaks anonymity.

SurveyMonkey
General survey tool
MIXED “Anonymous” toggle hides some data

Back‑end IP retention and metadata remain.

IPs retained in logs

Often kept for months for internal use.

Cookies & tracking pixels

Used for product analytics & marketing.

Email / SSO & per‑invite links

Creators can match responses back to invitees.

NO Not anonymous by design

Provider staff can access identifiable logs.

Google Forms
Free forms inside Google’s ad ecosystem
NO Tied into Google account & IP stack

Universities explicitly warn: not truly anonymous.

Global IP & device logging

Part of broader Google telemetry.

Cookies & account tracking

Cross‑product identifiers follow users.

“Collect emails” just one click away

Most “internal” forms run while logged‑in.

NO Built for convenience, not anonymity

Ad‑driven telemetry and account data remain.

Culture Amp, Officevibe, 15Five
Engagement & performance platforms
NO Engagement‑first, not anonymity‑first

User accounts and HRIS data sit at the core.

Device & usage analytics

Product telemetry across the employee lifecycle.

Cookies, app tracking, SSO

Continuous tracking is the feature, not a bug.

Always tied to named employee records

“Confidential” ≠ anonymous; manager views depend on identity.

NO Not structurally anonymous

The system is built to know who each response belongs to.

If a platform needs a cookie banner, it’s already collecting more than you think.
  • IP logs + device fingerprints + timestamps are enough to single someone out in a small team.
  • Per‑user survey links or SSO mean responses can be tied back to named people—forever.
  • “We don’t show you the IP address” is not the same as “we never collect it.”

How We Guarantee Anonymity

Our architecture is designed from the ground up to be truly anonymous. Even if someone tried to trace responses, there's no trail—because we never collect identifying data in the first place.

🔒
No Server Logs
Our servers don't log IP addresses. Even if someone tried to trace responses, there's no trail.
🚫
Zero Tracking Code
Our survey pages contain no tracking pixels, no third-party scripts that could identify you.
🎭
No Account Required
You never create an account. No email, no username, no way to link responses to a person.
📱
QR Code Only
Responses come through QR codes. No way to know who scanned which code or when.
🔐
Encrypted Storage
Responses are stored encrypted, separate from any identifying information (because there isn't any).
👁️
We Can't See Who You Are
Even if someone put a gun to our head, we still couldn't identify you. The data simply doesn't exist—we never collect it in the first place. It's architecturally impossible.

The Truth: What Each Platform Actually Collects

See exactly what data flows through each system. The difference is stark.

🛡️
WellPulse
Truly Anonymous
Response submitted
Stored anonymously
No tracking data collected
  • No IP addresses - We never see them
  • No cookies - Zero tracking cookies
  • No login required - Anonymous by design
  • No device fingerprinting - Can't identify you
  • No email addresses - Not collected, not needed
  • No Google login - Google tracking avoided entirely
⚠️
Most Survey Tools
Claims "Anonymous" but Tracks You
IP address logged
Cookies set & tracked
Device fingerprint created
  • IP addresses logged - Can identify location
  • Tracking cookies - Follows you across sites
  • Login often required - Links to your identity
  • Device fingerprinting - Unique device ID created
  • Email sometimes required - Personal identifier
  • Google login often required - Tracks you across Google services

See the Data Flow Difference

Wellness Pulse Data Flow

📱
You Scan QR Code
📝
Submit Response
🔒
Stored Anonymously
📊
Analytics Only

Other Tools Data Flow

🌐
Your IP Logged
🍪
Cookies Set
👤
Fingerprint Created
📊
Linked to You

This visual board summarizes how common EX & CX tools handle identifiers like IP addresses, cookies, logins, and survey links, based on their published product behavior and documentation at the time of writing. For a narrative explanation of why Wellness Pulse is architecturally anonymous—no logins, no cookies, no per‑person URLs—read “True Anonymity in Employee Feedback: Why Wellness Pulse Stands Alone.”

For detailed, vendor‑specific behavior, see each platform’s own privacy and security documentation, for example:

Disclaimer: This board reflects our best understanding of how these platforms handle identifiers as of 2025, based on their public documentation and customer reports. Features and practices may change over time. If you see anything that’s out of date or incomplete, please email support@wellpulse.org so we can update it.