OAuth disclosure
Google Data Access
QMS QueueBill uses Google sign-in for staff identity and the limited Google Drive scope https://www.googleapis.com/auth/drive.file for optional Sheets tracking and Drive backup.
Why Google sign-in is used
Google sign-in identifies the staff Google account that authorizes optional Sheets tracking and Drive backup features. If Firebase configuration is not present in a review build, the app can show placeholder mode so reviewers can inspect the local queue flow until the Firebase app is configured.
Requested permission
The app requests https://www.googleapis.com/auth/drive.file. This scope is used so the app can create and manage only files created or explicitly opened by QMS QueueBill.
How Sheets are used
When staff enable tracking, QMS QueueBill creates or updates an app-created Google Sheet for queue status. A public_status tab can be used as a limited public mirror for QR/customer tracking. It should contain only operational queue status fields needed for tracking.
How Drive backup is used
When staff choose backup, QMS QueueBill creates app backup files in the user's Drive, including queue settings and operational queue records needed for restore. The app does not scan unrelated Drive files.
What the app does not access
- No Gmail access.
- No broad read access to all Google Drive files.
- No broad read access to unrelated Google Sheets.
- No sale of Google user data.
- No advertising use of Google user data.
Public tracker data
Customer QR tracking reads limited token status fields only. It is not intended to expose staff identity, full spreadsheet contents, Drive backup files, or unrelated Google account data.