Privacy policy
Last updated November 17, 2026
Votelantern is provided by Redwood Digital LLC, 30 N Gould St, Ste N, Sheridan, WY 82801, USA. This page lists exactly what we store, for how long, and what we don't collect. Questions: support@votelantern.com.
For the people who post on our customers' boards, the customer (the team that runs the board) decides what happens to their data, and we process it for them under our data processing agreement. For account holders and for reports sent to us, we are the controller.
Account holders (team admins)
- Email address (your sign-in and verified email addresses), a password hash (never the password), your two-factor authentication secret and recovery codes.
- Terms version you agreed to at sign-up, and when.
- Your teams: team names, who is a member, and each member's role.
- Invitations: the invited email address, the role and who invited them. Open invitations expire after 14 days.
- Emails we send you (invitations, new-post alerts and new-report alerts): the address, subject (which names the team or board) and time stay as a delivery record for 30 days after each is sent; the text is cleared once sent. An email that still fails after 5 tries keeps its address, subject and text until it is deleted, 30 days after it was queued. An invitation email waiting to be sent is dropped if the invitation is withdrawn, declined, accepted or expires first. Every email we send (these and all the others this page describes) goes through Postmark, our email provider, which keeps its own copy of each email it sends (the address, subject and text) for 45 days (Postmark's standard retention; we don't buy longer retention), then deletes it; that copy is not covered by the deletion times below.
- Account emails (codes to confirm your email address or reset your password, a notice when someone tries to sign up with your address, and security notices when your password, email address or two-factor settings change) are sent straight away rather than queued, so we keep no delivery record of them. A code waiting to be used is kept, with the address it was sent to, in that browser's session until it is used or the session expires (at most 15 days). Security notices show the IP address, browser and time of the change, so you can spot a change you didn't make. Postmark, our email provider, also keeps its own copy (your address and the whole email, including that IP address and browser) for 45 days, then deletes it; that copy is not covered by our deletion times (see Emails we send you).
- Billing: our payment provider's customer and subscription ids, the plan and its status. Card details are held by Paddle, never by us.
- Your notification settings: the business name and postal address you enter for update emails.
- A session cookie while you are signed in (up to 14 days).
- Support notes: when we change an account, team or email address in our admin tools (for example at your request), the change is logged with its time and the item's name (an email address is named by the address, a team by its name). When we set someone's sign-in email address or password there, we also record which account, which of the two and when, by account number only (never the address or the password).
- If you signed up through a "Powered by" link, which kind of link it was and which team's board it was on.
"Powered by" links
The "Powered by Votelantern" link on boards, roadmaps, changelogs, widgets and update emails carries the board owner's referrer code. We count visits and sign-ups from these links in aggregate daily totals only, with no cookies, and we don't store visitors' IP addresses or browsers with them.
People who use a board (end users)
- Email address, used to confirm who you are and for the update emails you choose. It is never shown on a board; the board's team can see it.
- On a private board that lets people in by email domain, the board's team lists the domains (for example their company's). Each time you open the board, we check that your confirmed email address is on one of them. Nothing more is stored for this.
- Name if you give one (the board shows your first name and last initial), and, if the board signs you in from the team's own app, the external id that app gave you.
- When you confirmed your email, whether you are banned, and which board terms version you agreed to at your first post, and when.
- Your posts (title, details and any extra form fields), comments, votes and follows ("email me updates"), and any board you unsubscribed from.
- Sign-in links: only a SHA-256 hash of each link's token, the name typed with the request, and when it was made and used. A link works once, for 15 minutes; the record is deleted a day after the link expires (sooner if you or the board are deleted).
- Used token ids from the team's own app (single use), kept until the token would have expired.
- Queued emails: the address and text of each email waiting to be sent. The text is cleared once it is sent; the address, subject and time stay as a delivery record for 30 days after it is sent (or until you or the team are deleted, if that is sooner). An email that still fails after 5 tries is deleted 30 days after it was queued. Postmark, our email provider, also keeps its own copy (your address and the whole email) for 45 days, then deletes it; that copy is not covered by our deletion times (see Emails we send you).
- A session cookie once you confirm your email (up to 14 days). Visitors who only read a board get no cookies.
Reports and copyright notices
- The report: what was reported, the reason, the details you wrote, and your email if you gave one (required for copyright notices). For a copyright notice, your email is shared with the board's team, so the author can send a counter-notice; for other reports only we see it. A copyright notice gets an email receipt (at most 3 a day per address), which we keep like other queued emails: its text is cleared once it is sent and its delivery record is deleted 30 days after it is sent (if it still fails after 5 tries, it is deleted 30 days after it was queued); Postmark, our email provider, keeps its own copy (your address and the whole receipt) for 45 days, then deletes it; that copy is not covered by our deletion times (see Emails we send you). Decisions are recorded with a statement of reasons, and actioned copyright reports count as a strike against the author.
- Repeat-infringer records: each copyright strike is kept with the board's team and a SHA-256 hash of the author's email address, even after the author deletes their data, so a person who returns with the same address keeps their strike count.
Waitlist
- If you join the waitlist, we keep your email address, when you joined, when we last emailed you a confirmation link and when you confirmed. Nothing else: no name, no IP address and no browser details are stored with it (to stop floods, sign-ups are counted per IP address for an hour; see Rate limits and logs). The confirmation code is stored only as a hash.
- We send one email to confirm the address (a fresh one at most once a day if you ask again), and once you have confirmed, one email when Votelantern opens. Confirmation emails are sent through Postmark, our email provider, which keeps its own copy of each email it sends (your address and the email's text) for 45 days (Postmark's standard retention; we don't buy longer retention), then deletes it; that copy is not covered by the deletion times below.
- An address that isn't confirmed within 7 days of its last confirmation email is deleted; an address we haven't been able to email yet is deleted after 90 days; a confirmed address is kept until you remove it or we close the waitlist, when we delete the whole list. A daily job deletes expired addresses, unless that job fails, which alerts us so we can run it again.
- To leave, open the link in the confirmation email and press "Remove my address", or write to support@votelantern.com.
Business contact form
- If you send the "Business: talk to us" form, we email what you typed (company, team size, what you need, your email address and your message) to our support mailbox, with your address as the reply address. Apart from the rate-limit counts and server logs described under Rate limits and logs, we store nothing else for it. The queued email's text and your address are cleared once it is sent; the delivery record (our own support address, a subject naming your company, and the time) is deleted 30 days after it is sent. An email that still fails after 5 tries keeps its text and your address until it is deleted, 30 days after it was queued. Postmark, our email provider, also keeps its own copy (your address and what you typed) for 45 days, then deletes it; that copy is not covered by our deletion times (see Emails we send you).
- The email itself then stays in our support mailbox, so we can answer your inquiry and as our business correspondence with you, for 2 years after the last message, then is deleted in our next yearly clean-out (so within 3 years of the last message), unless you ask us to delete it sooner by writing to support@votelantern.com.
- We count how often the form and the "Business: talk to us" card are shown and how many messages are sent, in aggregate daily totals only, with no cookies; we don't store visitors' IP addresses or browsers with them.
Integrations
- If a board's team turns on Slack, Microsoft Teams or webhook notifications, we store the Slack, Teams or webhook URL and a signing secret for that board.
- Delivery records hold what we send: board names, post titles and statuses, display names, vote counts, links to the post, and up to 1,000 characters of comment text (our data processing agreement lists every field). No email address, IP address or post text beyond the title is sent. They are sent to Slack, Microsoft or the customer's own endpoint, as the customer chose, and kept for 30 days. If a person deletes their data, unsent deliveries about their posts and comments are deleted and sent ones are blanked.
Abuse blocklist
- We keep an operator-maintained blocklist of SHA-256 hashes of blocked email addresses and of blocked email domains, used to refuse abuse across all boards.
Rate limits and logs
- Rate limits: we count requests per IP address, per email address or per account (for example sign-in links, posts, votes, reports, waitlist sign-ups (IPv6 addresses by their /64 network), account sign-in attempts and password resets), stored only as keyed hashes (HMAC-SHA-256), never in clear, with a count or the times of recent attempts. Failed account sign-ins are counted per IP address, and per email address together with the IP address it was typed from (IPv6 addresses by their /64 network), so a few wrong passwords that someone else types for your email address from a different IP address or network don't stop you signing in. Each email address also has a loose cap, from any IP address: after 50 failed sign-ins in one clock hour (UTC), signing in, or confirming your password while signed in, with that address pauses until the hour ends or its password is reset (this count holds a number for the hour, not the times). A count stops counting when its window ends (a minute, an hour or a day), and a daily job soon after midnight UTC deletes it, so each is kept for at most 25 hours after the last request it counts, unless that job fails, which alerts us so we can run it again. A failed account sign-in is also written, with a keyed hash of its IP address (not the address itself), to the app log below.
- Web server logs: IP address and port, time, method, site name and page path, the connection's protocol and encryption version, and the response code, size and time taken (no query strings, sign-in tokens or request headers, so no cookies, browser user agents, languages or referring pages), rotated by size (the last 10 files of 20 MB).
- App log: each failed account sign-in, with its time and a keyed hash of its IP address (IPv6 addresses by their /64 network), never the IP address itself, the email address or the password; requests for the sign-in page are in the web server logs like any other page, with their IP address. The app log is rotated by size (the last 5 files of 10 MB): the oldest file is deleted when a new one is started, so an entry is kept until its file is rotated out, which takes longer when the service is quiet.
What we don't collect
- No analytics or advertising cookies, no tracking pixels, no third-party scripts on board pages, and no profile of a person across different customers' boards (the only record used across boards is the abuse blocklist above).
- No images or file uploads on boards: posts and comments are text only.
How long we keep it, and deleting it
- We keep data while the account or board exists. A board's team can export or delete any person's data at any time, and a person can delete their own data from the board ("Delete my data" in the board's footer).
- Deleted data leaves our backups within 90 days: nightly backups are kept for up to 8 weeks, and our storage provider deletes removed copies 30 days after that. While we recover from a security incident, we may keep backup copies longer, so deleted data can stay in our backups past 90 days; we go back to the usual schedule within 30 days after the recovery ends. Backups are encrypted: the nightly backups with our own key before they leave our server, and the continuous copy of the database by our storage provider (Backblaze) at rest.
- Our sub-processors are listed on the sub-processors page.