by Innoscout
Menu

Privacy

What data Innovote processes, why, with whom, and how long. In short: we keep what is needed to run your events.

Who is responsible

Innovote is operated by Sol Inventum OÜ, a private limited company registered in Estonia (registry code 14665482, VAT number EE102137570), Sepapaja tn 6, Lasnamäe linnaosa, Tallinn, Harju maakond, 15551 Estonia. Managing board member: Alexander Duggleby. Contact for everything on this page, including data protection requests: help@innovote.io.

There are two roles. For the data of your own organizer account Sol Inventum is the controller. For the data of an event, meaning its voters, votes, comments, bookmarks and entries, the organizer who runs the event is the controller and Sol Inventum is the processor that stores and handles it on the organizer's behalf. If you voted in an event or applied to one, the organizer is your first contact for questions about that data; we help the organizer answer them.

Organizers must have a lawful basis for adding voters and entries, and must tell them how their data is used. Innovote lets an organizer link its own terms and privacy policy and ask voters to agree before they vote or apply.

What data we process

Organizer accounts

  • Your email address and your password. The password is stored as a salted hash, never as plain text.
  • While you change your email address: the new address and a one-way hash (SHA-256) of the confirmation link, until the link is used or replaced. The link stops working after 24 hours; an expired one is no longer used and is removed the next time any account asks for an email change, or with the account.
  • The end date of the Own brand add-on (or of an earlier paid plan) of your account and counters for failed sign-ins. Accounts created before November 16, 2026 may also hold the campaign parameters (such as utm_source) of the link that brought you to the sign-up form; new accounts store none.
  • Your events: name, settings, logo and images you upload, entries, voters and co-organizer links, with the time each co-organizer link was last used to sign in.
  • If an event is in the public list of past events: its name, its logo, the month of its last vote and the number of its entries, voters who voted and votes are public on innovote.io. The organizer or a co-organizer decides this with the setting “Show this event in the list of past events on innovote.io” of the event (on for events of free accounts created from November 16, 2026, off for older events, never for Own brand; a copy of an event keeps that event's setting), and an event is listed only after it was switched off with at least 2 entries and 3 voters who voted. Entries, voters, votes, results, the voting link and the organizer’s email address are never shown. For the event name and logo the organizer is the controller.
  • We receive a notice by email at help@innovote.io when an account is created (with its email address) and when an event is created (with the account ID and the event name, not the email address).
  • If you use Contact us on the Plan and billing page, your message reaches us by email at help@innovote.io with your account's email address, account ID and plan. The app stores nothing of it except a counter that allows three messages an hour.

Voters

  • Depending on the event: an email address (self-registration, the voter receives a personal link by email), or a username and a PIN that the organizer creates. The organizer can see the PINs of the voters of an event.
  • Votes (scores or the chosen entry), comments, bookmarks, and the email address a voter types to have their bookmarks mailed.
  • The time a voter agreed to the organizer's terms or privacy policy, when the organizer requires it.
  • The time of the voter's last sign-in, which the organizer and the co-organizers of the event see.

People who apply with an entry

  • The name of the entry, an email address, an optional link and description, and an optional video that is uploaded to Cloudinary. The organizer and the co-organizers of the event see all of it. Voters see the name, description, link and video of an entry, not the email address.

Technical data

  • To limit abuse we keep counters for sign-in attempts, mails and sign-ups. Most of them are keyed by a one-way hash (SHA-256) of the email address or username, not by the address itself.
  • Our own error log: when the application fails, it stores the error with the request (address, form fields, query string, cookies and headers) in the application database, kept there until it is purged by hand (the application does not delete it on a timer). Passwords, PINs, tokens, sign-in and anti-forgery cookies and the cookie and authorization headers are replaced before an error is saved.
  • Operator logs: an audit log of what our operators do in the admin area (who, what, which account or event, the values before and after, the time, and the network address of the request shortened to its first 24 bits for IPv4 or 48 bits for IPv6), and a log of each request made with a read-only access token that an operator creates for analysis (time, address requested, result and the shortened network address).
  • Web server logs can contain technical request data such as IP address, browser, the address requested and the time.

Why we process it

  • To provide the service: sign-in, running events, collecting and counting votes, sending the mails described below, and support. For organizers this is the contract between you and us; for voters it is the organizer's purpose, on the organizer's instructions.
  • To keep the service secure and prevent abuse: rate limits, sign-in backoff, error logs and operator logs. This is our legitimate interest.
  • To support organizers and run the service: our operators can open the entries, voters (never their PINs), results and comments of an event, read-only, for support and for operating the service. Each such look, and each change an operator makes to an account, is written to the audit log. This is our contract with the organizer and our legitimate interest.
  • To understand how the service is used and to improve it: we analyze the names, criteria titles, settings and counts of events (not the entries or voters) internally, for example to see which criteria are common. This is our legitimate interest.
  • To show ended events in the public list of past events, when the organizer leaves the setting of the event on. This is the organizer’s choice under our contract with the organizer, and our legitimate interest in showing that Innovote is used.
  • To understand how the public site is used, with privacy-friendly analytics (see below). This is our legitimate interest.

Who else handles the data

We use these service providers. We do not sell personal data and we do not show ads.

  • Microsoft Azure hosts the application (Azure App Service) and the database (Azure SQL).
  • Postmark sends the mails of the service: account and password links, email change links and notices, voter sign-in links, bookmark lists, test links, your Contact us messages and the notices to us.
  • Cloudinary stores and delivers the files that organizers and applicants upload: logos, favicons, share images and application videos. The browser uploads directly to Cloudinary. A voter's browser, and the browser of anyone who opens the list of past events, loads these images from Cloudinary, so Cloudinary sees that visitor's IP address. The application does not delete these files when an event or an account is deleted or a file is replaced: they stay at Cloudinary until we delete them on request, so write to help@innovote.io to have them removed.
  • Fathom provides privacy-friendly web analytics on innovote.io (see below). Read its privacy policy.
  • Video hosts such as YouTube and Vimeo, only when an organizer or applicant links a video: the video plays in a frame from the host that the link points to, so that host receives the viewer's request and has its own policies.

The application itself sends no telemetry to a monitoring service.

Innoscout

Innovote is free because it is made by Innoscout, the startup application platform. Innovote links to Innoscout: on the public pages of innovote.io, and on the organizer pages, the voting pages, the winner reveal and our mails unless the account that owns the event has the Own brand add-on. These links carry referral parameters in the address (such as ?ref=innovote) so that Innoscout can count the visits that came from Innovote. If you follow one, your browser opens innoscout.com, which can see that you came from Innovote, as any website you follow a link to can. Innovote shares no data with Innoscout and sets no cookie for it. Innoscout’s own privacy policy applies on its website.

Analytics

On innovote.io we use Fathom Analytics on the public pages, the organizer and account pages and the voting pages. It counts page views and, on the public pages and the organizer pages, clicks on the sign-up buttons and on links to Innoscout, as named events. For a click Fathom receives the same data as for a page view: the page address, the referring page and the time zone. It does not use cookies for this purpose. It is not loaded on pages whose address contains a sign-in secret, such as a voter's personal link or a co-organizer link, and it is not loaded on self-hosted installations.

Cookies

The cookies we set, what they do and how long they last are listed on the cookies page.

How long we keep data

Apart from the operator logs below, the application does not delete data on a timer. It keeps data until it is removed:

  • Event data (entries, voters, votes, comments, bookmarks) stays until the organizer removes it. Deleting an event on its Settings page removes its entries, voters, votes and bookmarks. Removing a voter removes that voter's votes and bookmarks.
  • Your account stays until you delete it under Account, Delete account (your email address and your password are asked again). This removes the account and, at the same moment, every event it owns with its entries, voters, votes, comments, bookmarks and co-organizer links, and ends every session of the account. Voters and co-organizers of those events can no longer reach them. It does not remove the files uploaded to Cloudinary, entries in our error log or database backups: they stay until they are purged or the backup period ends. If you cannot sign in any more, write to help@innovote.io.
  • Password reset links are valid for 24 hours and a used or replaced link stops working.
  • Backups. Azure SQL keeps automatic backups for a period set in Azure.
  • Error log: kept in the application database until purged by hand; errors saved before the filters of November 2026 may still hold form values and cookies, which the owner decides whether to purge.
  • Operator logs: the audit log is kept for 2 years and the log of requests made with an access token for 90 days; the application deletes older rows as new ones are written.
  • Logs and mail copies are kept by Azure and Postmark under their own settings.

Your rights

You can ask for access to your personal data, its correction or deletion, a restriction or an objection to its use, and a copy of it in a portable form. Organizers can export their results and voters from the app. If you are a voter or an applicant, contact the organizer of the event first. You can also write to help@innovote.io. You may complain to a data protection authority, in Estonia the Estonian Data Protection Inspectorate, or the authority where you live.

Changes

We update this page when the service changes and show the date at the bottom.

Last updated: November 16, 2026.