SprintPoker privacy and data
What deleting a session does, how to erase one, what guests see, what is kept for sessions shared with SprintPoker for Jira, and what happens when an account goes.
Last updated
On this page
A SprintPoker session belongs to the workspace it was created in. This guide covers what deleting a session does, how a session is erased, what guests can see, and what happens to sessions shared with SprintPoker for Jira.
Delete a session
On the SprintPoker overview, a session card’s ⋮ menu has Delete Session. The session’s host or a workspace admin can delete it, and SprintPoker asks first.
- Deleting takes the session out of every list and closes its room for everyone.
- Everything recorded in the session, including everyone’s contributions, is kept. A deleted session can’t be restored from Laya.net.
- A session created in SprintPoker for Jira can’t be deleted on Laya.net: delete it in SprintPoker for Jira.
Erase a session
Erase Session, in the same ⋮ menu, removes a session and everything recorded in it for good: its issues, votes, results, comments and who took part. Only the session’s host or a workspace admin sees it, and SprintPoker asks them to confirm by typing ERASE.
- An erased session can’t be undone or restored. Only an entry in the workspace’s audit log records that it was erased.
- Estimates already saved to a board or to Jira stay where they were saved.
- For a session shared with SprintPoker for Jira, the confirmation first says how many people took part from SprintPoker for Jira. Erasing also removes the session there, and clears everything personal from the reference record SprintPoker for Jira’s backend keeps of it (see below).
- A session created in SprintPoker for Jira can’t be erased on Laya.net: erase it in SprintPoker for Jira.
What guests see
Everyone in a session, guests included, sees the other people in it by their display names. Guests see each item’s key and title, and its description only when the host shows descriptions (as Jira shows it, with its links and pictures). When the host shows them too, guests see each issue’s comments, with each author’s name, and its assignee and reporter, by name; and they see the board’s Reference Issues and Matching Issues by key and title. Guests never see email addresses, Atlassian account IDs, attachments outside a description, or the rest of the board, and the room never names the Jira site a session comes from (a link written in a description shows as written).
Sessions shared with SprintPoker for Jira
- Laya.net stores a shared session like any other session: its items (including a Jira issue’s key, summary and status, never its description, which is read live from Jira; a typed-in item’s title and description), votes, final estimates and AI hints. For each person who joins from Jira it also stores their Atlassian account ID, display name and profile picture address, as SprintPoker for Jira sends them.
- SprintPoker for Jira’s own backend, which carries the session between the two apps, keeps a reference record of each shared session so the app can list and open it: the session’s name, its participants’ display names, the Atlassian account IDs of the people who joined from Jira, and the Jira issue IDs and keys.
- Shared sessions are kept when SprintPoker for Jira is uninstalled or a site is disconnected. Nothing is deleted, and a disconnected session stays readable.
- Deleting a shared session on Laya.net leaves that reference record as it is; erasing the session clears everything personal from it.
When an account is deleted or closed
- When a Laya.net account is deleted, that person’s seats in SprintPoker sessions are renamed Former user and lose their link to an Atlassian account. Their votes and results stay.
- When an Atlassian account is closed, Laya.net removes its account ID from SprintPoker sessions and shows the person as Former Jira user. Their votes and results stay.
- Either way, the person’s name and account ID are also removed from the reference records that SprintPoker for Jira’s backend keeps of shared sessions.
Exporting results
Workspace members can Copy results or Download CSV from a session’s summary. The CSV lists each item’s key, title, final estimate, where it was saved and its rounds.
Email support@laya.net and include what you expected, what happened, and a link to the affected board or item so we can help quickly.