Privacy Policy

1. Who is responsible

CodeBucket OÜ, Pajustiku tee 1, Tallinn, Harjumaa 11912, Estonia is the controller for organizer accounts and this website. Contact: support@votumio.com.

For event content (participants' answers, cards and names) the organizer of the event decides what is collected and why; we process it on the organizer's behalf, under the data processing terms in the Terms of Service.

2. What we collect

Organizers: e-mail, display name, a password hash (or your Google account id if you sign in with Google), language and theme preferences, the events you create and images you upload. If you sign in with Google, we receive your e-mail, name and Google account id from Google. When you sign up, we also note where your visit started: the referring website (its domain only), a campaign tag in the link, if any, and the first page you opened.

Participants: no account. A random token identifies your browser; we store only its hash. If the organizer asks for names, the name you enter. Your answers, cards and votes.

Payments: handled by Paddle. We receive Paddle customer, subscription and transaction ids and the status of your plan — never card details.

Technical data: your IP address is used briefly in memory to limit abuse and is not stored in our database. Our hosting provider keeps technical request logs, which include IP addresses, for up to 30 days for security and operations.

3. Why and on what basis

Organizer accounts: to create and run your account and provide the service you signed up for — performance of a contract (Art. 6(1)(b) GDPR). Billing and tax records are kept by Paddle as the law requires (Art. 6(1)(c)). Where your visit started is used only in our own aggregate statistics about which channels bring new users — our legitimate interest (Art. 6(1)(f)).

Event content, including participants' answers, names, cards and votes: processed on behalf of the organizer, who decides the purpose and the legal basis (see section 1). We do not use it for purposes of our own.

Security and abuse prevention, for organizers and participants alike: short-lived IP-based rate limits and the hosting provider's request logs. Here we are the controller, and the basis is our legitimate interest in keeping the service secure and available (Art. 6(1)(f)).

4. Cookies and local storage

We only use what the service needs to work: a session cookie, a security (XSRF) cookie, and a participant cookie limited to one event; your language and theme are kept in your browser. No analytics or advertising cookies. Paddle's checkout loads only when you start a purchase and may use its own cookies to prevent fraud.

5. Who receives data

Our hosting provider Railway Corporation (United States, servers in the Netherlands, EU), acting on our behalf; Paddle.com Market Ltd (United Kingdom) as Merchant of Record for payments; Google, only if you sign in with Google. We do not sell data. Transfers to the United Kingdom are covered by an EU adequacy decision. Railway and Google are certified under the EU–US Data Privacy Framework, and transfers to them in the United States rely on it; Railway's data processing agreement also includes the EU Standard Contractual Clauses as a fallback.

6. How long

Event content: deleted automatically 5 days after the event ends (90 days with an event pass; with Pro, while you are subscribed and 30 days after); the event's title, place and dates stay in the organizer's list until they delete the event. Drafts: until the organizer deletes them. Events left open are ended after 24 hours. Account data: until you delete your account. Hosting request logs: up to 30 days. Backup copies, if any, are overwritten within 30 days, and deleted data is not restored from them. Payment records: kept by Paddle as tax law requires.

7. Your rights

You can ask for access, correction, deletion, restriction, portability and object to processing. Delete your account yourself on the Account page — this immediately erases your events and files. Reports can be exported as PDF or PPTX.

Participants should contact the organizer of the event; we will help the organizer answer. You can also complain to a supervisory authority, for example the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, www.aki.ee).

8. Security

HTTPS, hashed passwords and participant tokens, access checks on every action and a strict content security policy.

9. Children

Organizers must be at least 16. When participants are younger (for example in schools), the organizer is responsible for any consent that is needed.

10. Changes

We will announce material changes in the app. Questions: support@votumio.com.

11. Required data and automated decisions

An e-mail address and a password, or a Google account, are needed to create an organizer account. Participants need no account; a name is asked only if the organizer requires it.

We do not make decisions based solely on automated processing and we do not profile you.