This instance is operated by Triple Helix LLC, Sofia, Bulgaria. For private privacy requests, contact opavotingatanas@gmail.com. Do not post personal data, credentials or privacy requests in public issue trackers.
We process account email, display name, password hashes, memberships, votes, comments, history, invitations, preferences, authentication records and operational timestamps to provide the service. Hosting and security systems may also process IP addresses and request logs. Service delivery uses data necessary to provide the requested service; proportionate security and reliability processing serves legitimate interests. Legal obligations may require additional retention. Do not enter sensitive or confidential production information.
We respect your privacy and do not use third-party analytics or advertising trackers. While accounts and workspaces exist, statistics use account/team identifiers and activity timestamps to calculate accurate usage totals; these records are not anonymous. Statistics have no automatic expiry. Account deletion removes statistics activity and voter identifiers; workspace deletion removes its detailed statistics. Only platform-wide completed-round and vote counts survive workspace deletion: no names, emails, user/team/workspace/issue identifiers, content or individual event timestamps are attached to those counters. Shared voting history, operational records and backups follow the separate deletion rules below. Team admins see their team's aggregates; the super-admin sees platform aggregates. Exports include scoped team/workspace names and totals, not individual account lists or vote content.
We do not sell personal data or use workspace content for advertising or profiling. We do not routinely inspect workspace content; operator access is limited to necessary support, maintenance, security or legal obligations. Other authorized participants see shared workspace content. Hosting and email providers process data needed to deliver the service; enabled integrations such as Jira exchange data as configured by the operator. This is not a promise that data never leaves the server.
The application and its database are hosted by Kamatera on a VPS in France, European Union. Automated registration, verification-code and service emails are sent through Mailgun using its EU SMTP endpoint (smtp.eu.mailgun.org). Google/Gmail handles correspondence sent to the privacy contact address. These providers process data necessary for their respective services. The VPS location and EU SMTP endpoint do not establish that all provider processing stays within the EU; provider-specific processing locations and international-transfer safeguards remain subject to operator review.
Authentication uses a session cookie and a browser-stored session token. Browser storage also remembers interface preferences and the selected team. The app does not include advertising trackers or third-party analytics. Necessary authentication storage supports the requested service; any operator-added non-essential tracking requires its own disclosure and consent assessment.
Live account and workspace data remain while the service provides the account/workspace; there is no automatic inactivity-deletion deadline. Deleting an owner account purges its owned trial workspaces, teams, voting history and comments from the live database. Other users keep their own accounts and unrelated workspaces. Deletion removes the original account email, credentials, sessions and memberships, but shared history elsewhere retains the former display name with (Deactivated) added. That attribution is still personal data, not anonymisation. Operational records and content referring to a person may also remain; further erasure requests require review.
App-managed database backups are scheduled every 168 hours; at most 3 completed copies are retained, expiring after 21 days. With the standard configuration this is once per week and three weeks of maximum age. Expiry is checked every minute while the app runs with backups enabled and again on startup; shutdowns, disabled backups or storage failures can delay deletion. The first or overdue snapshot is taken on startup. These copies contain database data, including authentication records, and are restricted to operators. Separate deployment archives and downloaded exports are not managed by this schedule and require operator-controlled deletion. Restores must reapply intervening privacy deletions before reopening access.
Contact the operator privately to request access or a copy, correction, erasure, restriction or objection, and portability where applicable. The operator may verify identity proportionately and protect other participants’ data. Requests are handled manually; applicable deadlines, normally one month under GDPR, apply. Retention exceptions must be explained, not assumed from this notice. You may complain to your competent data-protection authority; applicable US state rights and appeal routes depend on jurisdiction. No paid certification or blanket GDPR/US-law compliance claim is made.