YOUR INFORMATION

Privacy policy

Last updated: October 18, 2026

This policy covers iVote at ivote.abelbwm.com. For privacy questions, support, or requests concerning your information, contact the iVote operator at abel@abelbwm.com.

Information used to run a room

iVote processes room names, participant names and identifiers, estimates, voting settings, custom questions and options, and room activity. Names may be generated when you leave them blank. This information lets participants join the same room, estimate together and review results.

Room information is shared with people who can access the room link or code. The interface hides estimates until the host reveals them; this is a presentation feature, not a guarantee that votes cannot be accessed technically before a reveal. Do not put passwords, secrets or sensitive personal information in a room.

Optional Jira connections

When a host connects Jira, iVote receives OAuth access and refresh tokens and information about the authorized Jira sites. Tokens are kept on the server and are not included in room messages. iVote sends your searches to Atlassian and retrieves issue information and editable estimation fields using the permissions you grant.

Adding an issue to a room shares its key, summary, description and link with room participants. A confirmed estimate update sends the chosen field and value to Jira. iVote also keeps a limited history of saved estimates in the room. Jira access remains subject to your Jira permissions and Atlassian’s policies.

You can disconnect Jira in the room. This removes the connection and imported Jira room data from the running server. To revoke the authorization itself, remove iVote from your Atlassian connected apps. Disconnecting does not undo changes already saved in Jira.

Browser storage and cookies

iVote stores room identity, the last room, theme preferences and tour progress in browser storage. It uses a host cookie, lasting up to 24 hours, to authorize room controls, and a short-lived OAuth state cookie, lasting up to 10 minutes, to protect the Jira connection flow. Cached application files support loading the app.

You can clear cookies, site storage and cached files in your browser. Doing so can remove your room identity and access to host controls.

Services that process information

The hosting infrastructure processes network information such as IP addresses and request details to deliver the service. Server diagnostic logs can include room information and imported issue content. Hosting and log retention are managed separately from the live room data; restarting a room server does not necessarily delete existing logs.

Fonts are delivered by Google Fonts, which receives connection information when your browser requests them. If you connect Jira, Atlassian processes the authorization and Jira API requests. See Google’s privacy policy and Atlassian’s privacy policy for their practices.

Retention and your choices

The current iVote server stores live rooms, Jira connections and saved-estimate history in process memory. Restarting the server clears that live data. Deleting a room removes it and its connection from the running server. Browser storage remains until you clear it. Records already saved in Jira remain in Jira under your organization’s retention settings.

Use iVote without Jira if you do not want to grant Jira access. Only import issues you are allowed to share with the room. For access, correction or deletion requests, email abel@abelbwm.com with enough context to identify the relevant room; do not send access tokens or passwords. We may need to verify your relationship to the information before acting. Applicable privacy rights depend on your location.

Changes to this policy

Changes will be published here with an updated date. Review this page when deciding what information to share with iVote.