Privacy Policy — Q-Flow
Status: Draft for legal review
Last updated: 2026-07-18
Effective date: To be determined by legal counsel
1. Introduction
Q-Flow ("the Platform") is a queue management system operated by [Organisation Name] ("the Organisation") to serve citizens efficiently. This privacy policy describes how personal data is collected, stored, accessed, and retained when citizens use the Platform.
2. Data We Collect
2.1 Citizen-Provided Data
When a citizen takes a token, the following data may be collected:
| Field | Required | Purpose |
|---|---|---|
Phone number (citizenPhone) | Optional | Queue status notifications (SMS/push) |
National ID (nationalId) | Optional | Identity verification for government services |
Name (citizenName) | Optional | Display on token and staff queue |
2.2 Automatically Collected Data
| Data | Purpose |
|---|---|
| Push subscription tokens (browser endpoint, encryption keys) | Delivering push notifications |
| Token metadata (status, timestamps, queue position) | Queue management and analytics |
| Feedback (rating, comment, suggestion) | Service quality improvement |
| Language preference | Bilingual display (English / Nepali) |
2.3 Data We Do NOT Collect
- Email addresses
- Payment information
- Biometric data
- Location / GPS data
- Browsing history beyond Platform usage
3. How Data Is Stored
3.1 Encryption at Rest
All personally identifiable information (PII) — phone numbers and national ID numbers — is encrypted using AES-256-GCM (Advanced Encryption Standard, 256-bit key, Galois/Counter Mode):
- Algorithm: AES-256-GCM
- IV: 12-byte cryptographically random IV per encryption
- Key derivation: Server environment variable
ENCRYPTION_KEY, hashed with SHA-256 - Storage format:
iv_hex:auth_tag_hex:ciphertext_hex
Encrypted fields are never stored alongside plaintext. Phone numbers are also stored as a SHA-256 hash (citizenPhoneHash) for lookups without decryption.
3.2 Database
- PostgreSQL with Prisma ORM
- Hosted on [infrastructure provider — to be filled by legal/ops]
- Encrypted backups at rest
- Connection encrypted via TLS
3.3 Push Subscription Data
Browser push subscription endpoints and encryption keys are stored in the PushSubscription table. These are used solely to deliver queue status notifications and are automatically cleaned up when subscriptions expire.
4. Who Can Access Your Data
| Role | Access Level |
|---|---|
| Citizen | Own token status only (via token ID / QR code) |
| Staff | Tokens assigned to their counter — including name, phone (decrypted), queue position |
| Manager | All tokens in their department |
| Admin | All tokens in their organisation |
| Super Admin | All organisations — platform-level management |
All data access is logged. Decrypted PII is only visible to staff at the counter serving the citizen. Phone numbers and national IDs are masked in UI views where full display is not required for service delivery.
5. Data Retention
5.1 Token Data
Token records (including associated PII) are retained for a configurable period after the token is finalised (service completed). The default retention period is 90 days after finalisation, after which token records and associated PII are automatically purged.
See PII Retention Policy for full details on the auto-purge schedule.
5.2 Push Subscriptions
Push subscriptions are automatically removed when:
- The subscription expires or becomes invalid (HTTP 410 Gone)
- The citizen disables notifications
- The associated token is purged
5.3 Feedback
Feedback data (rating, comment, suggestion) is retained for the same period as the associated token record.
5.4 Logs
Application logs containing PII are rotated and deleted within 30 days. Audit logs (access events) are retained for 12 months for security purposes.
6. Your Rights
Under Nepal's data protection best practices and this policy, citizens have the right to:
- Access — Request a copy of all personal data held about them
- Deletion — Request immediate deletion of their personal data
- Correction — Request correction of inaccurate personal data
- Opt-out — Decline to provide optional PII fields; disable push notifications at any time
To exercise these rights, citizens may contact the Organisation's designated data protection officer at [contact email — to be filled].
7. Push Notifications
Push notifications require explicit opt-in via a button click. Citizens are never pre-enrolled in push notifications. Citizens may disable notifications at any time from the token status page.
Push notifications are used only for queue-related status updates (e.g., "Your turn", "Token transferred", "Service complete"). No marketing or promotional messages are sent.
8. Cookies and Local Storage
The Platform uses local storage (not cookies) to store:
- Cookie consent preference — Whether the citizen consented to push notifications
- Language preference — Display language selection
No third-party analytics cookies or tracking cookies are used. No advertising networks have access to Platform data.
9. Changes to This Policy
This policy will be updated as Nepal's data protection framework evolves. Material changes will be communicated via the Platform. Citizens are encouraged to review this policy periodically.
10. Contact
For questions about this privacy policy or to exercise your data rights:
- Organisation: [Name — to be filled]
- Data Protection Officer: [Name / email — to be filled]
- Platform operator: Atech Agency
This is a draft document for legal review. It does not constitute legal advice and should be reviewed by qualified legal counsel before publication.