ez-pollster

Privacy Policy

Draft, last updated 2026-08-29. This is a beta project - this policy is plain-language and hasn't been reviewed by a lawyer.

Who operates this

ez-pollster, currently run informally by its creator, not through a registered company.

What we collect

For researchers: your email address (via Firebase Authentication), your credit balance, the surveys you create, and a hash of your MCP token (never the token itself). For respondents: the answers you submit, and - only if you set yourself up through /respond - a random respondent ID with no name or email attached. We don't require or collect a respondent's name or email at all.

Separately, we collect aggregate product analytics (page views, and counts like surveys created or responses submitted) - see "Analytics" below for exactly how.

Analytics

We use PostHog to see basic, aggregate numbers - which pages get visited, how many surveys get created, how many responses come in. This runs entirely on our own backend, not in your browser: there's no tracking script running on this site, no cookie, nothing saved on your device. Page views are counted using a one-way hash of your IP address and browser, regenerated fresh every day - it lets us say "X people visited today" without ever storing anything that identifies you, and the same visitor can't be recognized from one day to the next. We don't build profiles, don't track you across other sites, and don't use this data for anything beyond understanding whether the product is actually being used.

What we don't collect

No ads, no selling of data to anyone, no cross-site tracking or profiling, no attempt to identify respondents beyond the optional random ID above.

How we use it

Only to run the product: authenticate researchers, store and serve surveys and responses, and track credit balances. We don't use your content to train any AI model.

Where it's stored

Google Firebase / Firestore (Google Cloud infrastructure). MCP tokens and invite/promo codes are stored only as SHA-256 hashes, never in plaintext.

Sharing

We don't sell your data. We don't share it with third parties beyond the infrastructure providers needed to run the service (Firebase / Google Cloud), or if legally required to.

Security

The site is served over HTTPS and secrets are stored hashed, not in plaintext - but this is a beta with no formal security audit. Please read the prompt-injection note in the FAQ before submitting anything sensitive through a survey.

Data retention

Data is kept while your account or survey exists. There's no fixed retention period yet during beta - ask for deletion any time (see below) and we'll remove it.

Your choices

You can stop using the service at any time. To ask what's stored about you, or to request deletion of your account and its data, use the contact form on the dashboard.

Changes

This policy may be updated as the product evolves during beta.