Legal
Privacy
Last updated: 17 July 2026
What this service is
ScrumPoker is a real-time planning poker tool. You can create a room, invite teammates with a short code, vote on estimates, and export results. There are no user accounts.
What we store
- Session data — room name, display names, roles, votes, story backlog text you import, reactions, and round history for the life of the room.
- Browser preference— your name, theme, and room identity are kept in your browser's local storage so you can rejoin quickly.
- Technical logs — if error monitoring is enabled (e.g. Sentry), we may receive crash reports, performance traces, and anonymised session replays around errors. We do not intentionally collect passwords or payment details (none are used).
- Analytics — aggregate traffic metrics via Vercel Analytics (page views), without accounts.
Retention
Active rooms expire after about 24 hours of inactivity when Redis persistence is configured. Local-only deployments keep rooms in memory until the process restarts. Clearing your browser storage removes your saved name and identities on that device.
Sharing
We do not sell personal data. Room contents are visible to anyone who has the room code or invite link. Treat codes like a shared meeting password. Facilitator actions (kick, reveal, import) require a private seat credential stored in your browser — knowing another person's public ID is not enough to act as them. Infrastructure providers (hosting, Redis, analytics, error monitoring) process data only to run the service.
Your choices
Use Leave in the session panel to remove your seat from the room. Closing the tab only marks you offline — your seat may remain until the room expires or the facilitator kicks you. Ask the facilitator to kick a participant if needed. Avoid pasting sensitive personal data into story titles or names. Contact the operator of this deployment if you need a room removed sooner than the idle expiry.
Contact
Questions about this policy for the scrumpoker.com.au deployment can be raised via the feedback page. For self-hosted copies, contact whoever runs that instance.
Also see our Terms of use.