Privacy Policy

Updated: October 29, 2026

Checkout sends your name, email, selected plan and payment amount to our server and fmzpay to create and verify your order. Order records are stored in Cloudflare KV. Card details are entered on the hosted payment provider page and are not stored by this storefront. Cart and preference data stay in browser storage.

Information the service is designed to use

A live service could process organizer account details, ballot content, plan selections, support correspondence, technical logs, and voter responses. Billing card details should be handled by a payment provider such as fmzpay and should not be stored by Votelyra. Information submitted should be limited to what is needed for the selected activity.

Voter email addresses

Voter emails are used only for the vote and never sold. Their intended purposes are delivering an invitation, supporting vote verification, and administering reminders selected by the organizer. They should not be added to unrelated marketing lists or disclosed as a standalone contact list. An organizer remains responsible for having a lawful basis to upload and use those addresses.

Cookies and local storage

The demonstration stores a cookie-banner choice and may store a cart, promotion code, or newsletter form value in local storage. This information stays in the current browser unless you clear it. It does not synchronize across devices. No analytics or advertising cookies are included in this build. A production service should document any essential authentication or security cookies before introducing them.

How information would be shared

A live service could use vendors for hosting, email delivery, payment processing, security, and support, each limited to the relevant function. Information could also be disclosed when required by law or necessary to protect users and prevent abuse. Voter email addresses are never sold. Any production vendor list and international-transfer terms should be published before launch.

Retention and security

Information should be retained only as long as needed for the vote, legal obligations, dispute handling, and security. Organizers should define ballot and voter-list retention periods. Raw exports and activity logs on Grand require particular care because they may contain sensitive operational information. Reasonable access controls, encryption in transit, and credential protection are expected; no system can be guaranteed completely secure.

Your choices and rights

Depending on location, individuals may have rights to request access, correction, deletion, restriction, portability, or objection. A voter may need to contact the poll organizer for ballot-specific data, while account holders may contact the operator for service data. Verified contact details are not currently listed, so this demonstration cannot receive or fulfill such requests.

Children and policy changes

The service is not intended for children where local law requires verifiable consent without an appropriate organizer and guardian process. Material privacy changes should be posted with a revised date and, where required, advance notice or consent. A production launch requires a complete operator identity, contact route, retention schedule, and jurisdiction-specific review.