Archived Privacy choices
Choose the request path that can act
QueueRove account data, local mobile state, and HaloPSA records have different authorities. Start with the system that controls the data.
- Version 2026-08-02.1
- Effective date: August 2, 2026
- SHA-256
3dc99fa18cedf37e4c40f42aadef09cfa7c86b9695fde17ce06a1f0f40549e06
Archived version
This is the current published version of this document. Material changes receive a new immutable version, a new content hash, and an archive entry.
The content hash is derived from the versioned structured source rendered on this page. Material changes receive a new version, an archive entry, and, where required, reacceptance.
View the current stable route → · View all archived documents
1. Request map
| Data | Authority | Request path |
|---|---|---|
| QueueRove identity, profile, memberships, grants, assignments, legal acceptance, sessions, or privacy history | ITECS Outsourcing, LLC through verified QueueRove workflows | Authenticated privacy controls, or /account-deletion if locked out |
| Organization profile, membership, billing projections, customer-visible audit, or organization deletion | Primary Owner through verified QueueRove workflows | Authenticated Owner privacy controls |
| Support, security, privacy correspondence, or identifiable website logs | ITECS Outsourcing, LLC | Dedicated QueueRove category through support@itecsonline.com |
| iPhone or Android credential, cache, queue, or local state | Device user/administrator and the installed app | Follow in-app or support guidance after checking synchronization |
| HaloPSA tickets, customers, notes, photos, time entries, or user records | The organization controlling the HaloPSA environment and HaloPSA | Contact that organization's HaloPSA administrator |
2. Personal QueueRove requests
- Use authenticated account settings when access is available; sensitive export and deletion actions require recent MFA.
- If locked out or the app was uninstalled, use the public Account Deletion intake. The response remains non-enumerating until identity is verified.
- State whether you seek access, correction, export, or deletion and provide only the minimum non-secret context needed to route the request.
- Complete the identity-verification step. Email possession or a support message alone is not authority to disclose or mutate account state.
3. Organization requests
Only the primary Owner may request an organization export or deletion. Recent MFA, explicit confirmation, and typed organization name are required. A user who is primary Owner cannot complete personal deletion until the separately governed ownership process is resolved.
4. Device-local mobile data
Check visible synchronization state and confirm important work in HaloPSA before signing out, resetting, clearing, uninstalling, or replacing a device. Pending work may exist only on that device. Follow the controls and warnings in the app, or request version-specific guidance without sending secrets or customer records.
Lost or compromised device
Ask the HaloPSA administrator to revoke or rotate affected credentials and use organizational device controls. A QueueRove privacy request cannot remotely protect a device you no longer control.
5. Website and cookie choices
QueueRove uses only essential identity, session, invitation, security, and checkout cookies for enabled features. QueueRove does not use analytics, advertising, tracking pixels, or other non-essential cookies and therefore does not present a marketing-cookie banner.
6. Timing and limits
The initial privacy or deletion response target is 2 business days. Business hours are Monday through Friday, 8:00 a.m. to 5:00 p.m. Central Time, excluding U.S. federal holidays. This is a response target, not a resolution SLA. The deletion completion target remains 28 days after identity verification, subject to lawful holds or permitted extensions.
Related resources
Questions may be sent to support@itecsonline.com with the subject “QueueRove privacy request”.