A short overview of how the products handle accounts, data, and privacy. Aimed at venue buyers, mobile DJs, and anyone evaluating the platform during beta.
NexaDeck runs on your computer and works with your local karaoke library — your music files do not leave the machine unless you explicitly opt into cloud sync. NexaLive collects audience song requests, singer names, and queue state for the duration of an active show. We collect account information (email, locale, role) for sign-in and a small amount of operational telemetry for crash reporting and uptime monitoring.
Account sign-in is handled by Abydonian, which acts as the OAuth 2.0 authorization server for the rest of the platform. Passwords are hashed; sessions use signed JWT tokens. Admin access is gated by role and reviewed manually during beta.
Account data, license records, and audience-request state live in a managed PostgreSQL database. All web traffic is served over HTTPS via Let's Encrypt certificates managed by Caddy. Backups are taken on a regular cadence and stored separately from the production database.
We treat audience-side data (singer names, request times) as transient show state — it is not used for advertising, never sold or shared, and is purged on a rolling schedule. The privacy policy and cookie usage are documented under /legal. EU-based testers can request export or deletion of their account by contacting us.
During beta, security and uptime issues are tracked alongside product bugs. If you discover a vulnerability, please report it privately rather than opening a public issue. We aim to acknowledge reports within two business days.
Reach out if you need a more detailed answer for a venue procurement review, or to disclose a security finding.
Contact us