Effective date
June 27, 2026
Privacy Policy
Privacy policy for the current Zelyo web application.
This policy describes the current data-handling posture visible in the product and codebase today. It is written to match the live architecture, while final jurisdiction-specific legal review is still pending before production launch.
Applies to
Zelyo marketing pages, merchant workspace, customer queue pages, and display surfaces.
Privacy contact
[email protected]Pre-launch legal note
This page is intended to function like a real privacy policy, but it should still be reviewed and finalized with legal counsel before a production commercial launch. Where this page and the deployed product differ, the deployed product behavior governs until the written policy is updated.
Overview
Zelyo is a real-time queue platform for venue operators and their customers. This policy applies to merchants who create or manage venues, customers who join queues without a full account, and visitors who browse the public website or contact the team.
Information we collect
Merchant flows use authentication and account information such as email address, display identity, and venue membership records. Queue flows also create operational records such as venue slug, ticket number, display name, avatar choice, queue position, queue status, and related timestamps so live queue screens, room views, and merchant controls can function.
How we use information
Zelyo uses this information to authenticate merchants, create and operate venue queues, keep customer ticket views synchronized, enforce plan limits and billing-backed entitlements, and respond to support, security, or commercial inquiries. The current product is built around operational clarity, so the data used is tied primarily to queue state, venue administration, and service continuity.
Sharing and service providers
The current application relies on Firebase services, including Authentication and Firestore, to support merchant sign-in and queue data storage. Billing and customer billing-portal actions route through Dodo Payments. This page does not claim broader advertising, data brokerage, or resale practices beyond those service-provider boundaries evidenced in the current product.
Customer queue participation
Customers can join a venue queue without creating a full Zelyo account, which keeps the public flow lighter on mobile. Even so, joining a queue still creates venue-scoped operational records, and active ticket continuity currently depends on URL-based ticket references so queue and room pages can reconnect the customer to the same live entry across refreshes and view changes.
Retention and security posture
The current repository does not publish a final data-retention schedule or make claims about audits or certifications. Operational data is stored in the current application systems for queue operation, merchant access, billing enforcement, troubleshooting, and security review as needed. Zelyo's related security page describes the current architecture conservatively and should be read together with this policy.
Choices and contact
If you have a question about queue data, merchant account information, billing-linked behavior, or a suspected privacy or security issue, contact Zelyo using the public channels already provided on the site. Sales questions can go to [email protected], product-support questions to [email protected], and privacy or security questions to [email protected] so the request reaches the right team.
Related