Quevilo privacy policy

Updated 15 November 2026. This policy covers Quevilo’s private iPhone release (version 1.0, build 7 onwards), its Android release, and its encrypted guest website. Earlier Firebase-based test builds are covered by their legacy policy.

Quevilo is published by Xin Yun Tan in Singapore. Contact moon-keeper@hotmail.com for support and privacy questions.

Optional receipt printing

If you choose Bluetooth printing, Quevilo sends the service name, ticket number, issue time and assigned counter to your selected printer. Guest names and service notes are not included on these receipts. Printer selection is remembered on your phone. Bluetooth permission is used to find or connect to a printer, not to determine your location. No receipt content is uploaded for printing.

Your queue records

Operator records, including guest names, service requests, ticket history, uploaded logos and settings, are saved encrypted on the operator’s phone. The device encryption key is held in Apple Keychain on iPhone or Android Keystore on Android. Android operator records are excluded from automatic device backups; use Quevilo’s encrypted backup export for recovery. Quevilo does not send that key to the publisher or hosting service. The private app does not require an operator account and does not use Firebase Authentication or Firestore.

Guests choose whether to join. An operator may require a name; service requests are optional. Guest names and service requests are encrypted in the guest’s browser for the operator before transmission. Ticket status and counter updates are also encrypted for that guest. The publisher’s server administration access does not provide the keys needed to read these encrypted records.

Public service information and technical data

Each permanent QR uses a random service identifier and a public verification key. The service directory stores the public service name, whether names are required, whether the service is open or retired, route revisions, expiry times, event identifiers and public encryption keys. This information is not secret. Do not put guest details or confidential information in service names.

Cloudflare hosts the guest website and relay. It processes network information such as IP addresses and request timing to deliver the service and prevent abuse. The app uses rate limits based on hashed connection capabilities and IP addresses. The relay stores encrypted ticket messages, random ticket/event identifiers, hashed connection credentials and expiry information. The publisher can observe service metadata and usage, but not decrypt guest records through server access.

There is no advertising, cross-app tracking, analytics SDK, location collection or contacts access. Queue statistics are calculated from records on the operator’s device. If you email support, the email address and information you voluntarily send are used to respond; do not send guest records, backups, recovery keys or passwords.

Storage, expiry and deletion

Local records stay until the operator deletes them or removes the app. Resetting an event moves its tickets into local Past events. Operators can delete archived events after confirmation. Closing a queue does not erase its records.

Relay ticket contents expire within 24 hours of the event’s relay creation, or are removed when that relay event is ended. Minimal ended-event markers remain without ticket contents or owner credentials. The permanent service directory remains so printed QRs keep working; retiring a service disables its QR but keeps its directory entry, including its public name, identifiers and retirement state. Rename a service to a non-identifying name before retiring if necessary.

Guests’ saved ticket state and encryption keys remain in that browser’s website storage until cleared by the guest or browser. Clearing them may prevent recovery of that ticket. Guest records on the operator’s phone are controlled by that operator; contact the operator for access, correction or deletion. The publisher cannot retrieve or edit those local records.

Backups and replacement phones

Operators can export an encrypted backup to a destination they choose in the share sheet. A separate recovery key is required to restore it. Neither the backup nor that key is automatically uploaded to the publisher. Keep the key separately and save a new backup after adding services. We cannot reset a lost recovery key. A backup includes archived records and service identities; restored services start closed and old tickets remain in history.

Copies saved to Files, Photos, email or cloud storage are controlled by you and the chosen provider. Deleting records inside Quevilo does not delete exported backups or shared images. Retire use of the old phone after restoring on a replacement phone.

Limits of protection

Encryption does not protect information displayed on an unlocked or compromised device, information shared by a guest or operator, public service metadata, or a maliciously replaced guest website. This design prevents ordinary publisher or hosting-administrator access from decrypting stored guest records; it is not a promise that every possible attack is impossible.

Providers and changes

Cloudflare and support providers may process technical information outside Singapore under their own retention practices. See Cloudflare’s privacy policy. Changes to this policy will be posted here with an updated date.