This policy explains what Lumavote (“we”, “us”) collects from hosts (people with accounts who run sessions) and participants (people who join a session with a code or link), and what we do with it.
Hosts: email address, display name, and — if you sign in with Google — the basic profile Google shares for sign-in. Plus the content you create: sessions, questions, uploaded images, session settings.
Participants: the responses you submit in a session, a per-session identifier, and — only when the host enables email confirmation or single-use voting links — the email address you enter for that session. Participants never get a Lumavote account.
Everyone: the technical minimum to run a website — IP addresses in server logs and the cookies described below.
We set only functional cookies: a session cookie for signed-in hosts and a short-lived participant token that ties a browser to a voting session. No advertising or cross-site-tracking cookies.
Our product analytics is cookieless: it stores nothing on your device — no cookies, no local storage — and counts page views using a privacy-preserving identifier our analytics provider derives on its servers and rotates daily. It does not follow you to other websites. Pages that participants use — joining and answering a session, single-use voting links, shared reports and the presenter screen — are excluded from it entirely.
To operate the Service: running sessions, computing results, sending the transactional emails a session needs (verification codes, voting links, reminders), billing, and keeping the Service secure. We also measure how the Service itself is used — which pages are read, and which steps hosts take (creating a session, opening it, changing plan) — to decide what to build and fix. Those measurements carry counts, ids and settings, never the text of a question, a document you upload, or an answer anyone submits. We do not sell personal data and we do not use participant responses for advertising.
AI processing: when a host uses AI features (question generation, grading of open-text answers), the relevant question and response text is sent to a large-language-model provider acting as our processor, to produce the result. We send the text the feature needs and nothing else — never your account profile — and the provider may not use it for its own purposes, including training.
Lumavote is the controller of the personal data described here. We decide what is collected and why, we answer requests about it, and we are accountable for it. The infrastructure we run on — hosting, database, file storage, email delivery, realtime infrastructure, product analytics and AI model providers — acts only as our processor: on our instructions, for the purposes above, with no right to use your data for anything of their own.
Two exceptions where a company is not merely our processor, and you should know: Paddle is the merchant of record for paid plans, so it is the seller on your receipt and it — not we — receives the payment details you enter at checkout. And if you choose to sign in with Google, Google authenticates you under its own terms.
Processing may take place outside your own country. A current list of the processors we use is available on request from support@lumavote.com.
Host content is kept while the account exists. Session data belongs to the host who ran the session; hosts can delete sessions and their data, and participant-identifying data can be removed while keeping aggregate totals. Deleting your account removes your personal data except what we must keep for legal or accounting reasons (e.g. invoices).
You can request access to, correction of, or deletion of your personal data, and you can object to or restrict processing, by emailing support@lumavote.com. If you are a participant, the host who ran your session is the controller of the session's contents; we will help route your request to them where that is the right channel. Unsubscribe links in our emails work without an account and do not expire.
Data is encrypted in transit, access to production systems is restricted, and secrets are managed outside the codebase. No internet service can promise perfect security; if we learn of a breach affecting your data we will notify you as the law requires.
We may update this policy, and material changes are announced to hosts. Privacy questions: support@lumavote.com.