Cookie Policy

Updated: October 29, 2026

This Cookie Policy explains browser storage on the Votelyra static demonstration and the approach intended for a connected service. The current build does not include analytics, advertising trackers, session accounts, or server-set authentication cookies. It uses local storage for limited interface functions.

What this demonstration stores

Local storage may hold your cart items, quantities, plan options, promotion-code selection, cookie-banner choice, trial selection, and newsletter demonstration value. These records use the votelyra_ prefix. They remain in this browser and do not synchronize across devices. Clearing site data removes them. The mock checkout clears the cart and promotion selection after its success screen.

Accept and Decline

The cookie banner offers Accept and Decline. Accept records your choice so the banner does not reappear on every page. Decline also records only the choice needed to remember that you dismissed the banner. Essential cart operations can still use browser storage because you explicitly add products or change quantities. Neither option enables advertising or analytics in this build.

Essential production storage

A live service may need essential cookies for sign-in sessions, CSRF protection, load balancing, fraud prevention, and remembering security preferences. Duplicate-vote safeguards may also use cookies, but they have limits: users can clear storage, switch browsers or devices, and use different email accounts. Such safeguards must never be described as guaranteeing one unique human per vote.

Voter information

Voter emails are used only for the vote and never sold. Email verification is a separate mechanism from browser storage. It should be limited to invitation and vote-administration purposes, with clear notices and suitable retention. This demonstration does not send voter emails or operate verification.

Optional technologies

No optional analytics or advertising technology is currently installed. If a production operator later adds it, the operator should update this policy, identify the provider and purpose, state retention, and request consent where required. Consent tools must make rejection as accessible as acceptance and must not use preselected advertising choices.

Managing browser data

You can clear local storage through your browser’s site-data settings. Blocking all storage may prevent the cart and preference banner from working as intended. Browser controls differ, so consult the help documentation for your browser and device. Using private browsing may remove data when the session closes.

Third-party payment pages

If a production checkout redirects to or embeds fmzpay, fmzpay may use its own necessary security and fraud-prevention technologies under its own notices. Card details should be handled by fmzpay rather than stored by Votelyra. No fmzpay payment component is active in this storefront.

Updates and contact

Material changes to storage practices should be reflected in an updated policy and, when required, a renewed consent choice. Verified operator contact details are not currently listed. The inquiry form is a non-transmitting mock and should not be used to send personal-data requests.