Data & Privacy Statement
This statement covers the Pokerly app for Jira Cloud.
Where data is stored
Pokerly uses Forge-hosted storage (KVS) within the customer's Atlassian environment. The app does not operate external servers or make external data egress calls.
What is stored
Pokerly stores app settings (including account IDs of session managers and observers, the default Jira field, and the selected Insights method), card templates, sessions (including names, descriptions, issue keys, issue summaries and icons for queued issues, and final estimates), votes per round (account ID and selected card), presence information (account ID, display name and avatar URL, refreshed hourly), and estimation history per session and issue for Insights.
Personal data
Pokerly processes Atlassian account IDs and may temporarily cache display names and avatar URLs for session presence. The app does not store email addresses.
Retention
Deleting a session removes its associated votes and presence data. Estimation history is retained for Insights until the app is uninstalled. Uninstalling Pokerly removes its Forge-hosted application data.
Access and permissions
Jira API calls are performed as the signed-in user (asUser), so Jira permissions are respected. All data mutations are validated server-side against the user's Pokerly role.
Data sharing
Pokerly does not sell or share customer data with third parties.
About this website
This section is about the website pokerly.umaylabs.com, not the Pokerly app.
The website is static. It uses no analytics and no tracking cookies. The only thing it stores is your theme choice (light or dark), saved in your browser's localStorage.
Questions
For privacy questions, email contact@umaylabs.com.