Data Retention — MyQueue

Last updated: 15 May 2026

This notice describes how long queue-related data typically remains in MyQueue when operated by PiHub Systems (“we”). It aligns with owner-controlled archiving in the product.

Related: Privacy Policy (/legal/privacy-policy), Terms (/legal/terms-of-service).

1. Principles

• Data is kept only as long as needed to operate the queue, meet billing/legal obligations, and resolve disputes.
• Venue owners have tools to remove certain historical queue rows (see §3).

2. Active queue data

While a visitor entry is waiting, called, skipped, or otherwise not permanently closed, related records are retained in active processing so staff consoles and displays function correctly.

3. Completed (“done”) entries — archive behaviour

When staff marks an encounter done, the entry remains stored until:

• The owner runs Archive old done (or equivalent API), which deletes completed entries older than a chosen age; defaults suggested in-product are often ~90 days, and the API typically accepts an owner-selected window within 7 to 3650 days, or
• The venue/account is terminated and deletion timelines in §5 apply.

Important: Until archived or deleted, done rows may still contain name, optional phone, age/area, and timestamps. Owners should run archive periodically if they wish to minimise historical exposure.

4. Billing and account records

Invoices, subscription status, Razorpay references, and owner account metadata may be retained for statutory and tax periods (commonly multiple years under Indian tax law unless counsel advises otherwise—replace this sentence after accountant confirmation).

5. Termination

After subscription ends or account closure:

• Queue operational data shall be deleted or anonymised within 90 days unless law requires retention.
• Backups may persist for a limited technical window before expiry.

6. Logs and security

Security and application logs may be retained for 90 days for abuse investigation (exact window configurable operationally). Structured logs should avoid full phone numbers where feasible.

7. Visitor requests

Individuals exercising rights should contact support@pihubsystems.com. Where data was collected at a venue, we may coordinate with that venue.

8. Changes

Updates will be posted here with a revised date.

Disclaimer: Draft template — align retention periods with counsel and accounting advice.