Archived Terms of service
QueueRove Terms of Service
These terms govern use of the QueueRove service, including the website control plane and the QueueRove mobile apps for iPhone and Android.
- Version 2026-08-02.1
- Effective date: August 2, 2026
- SHA-256
1dfc46e09c513b5f8c957e442b629d458d0ce235627d9431d8909ffd96b4dbe0
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. Operator and acceptance
QueueRove is operated by ITECS Outsourcing, LLC, a Texas limited liability company. QueueRove, we, and us refer to that operator. By creating an account, accepting these terms during onboarding or invitation, or using the service, you agree to these terms.
QueueRove is offered for business use by MSPs. A user must be at least 18 and have authority to bind themselves. A primary Owner accepting organization terms must also have authority to bind that organization. A separately signed agreement controls where it expressly conflicts with these public terms.
2. The service
QueueRove lets MSP technicians work HaloPSA tickets and time entries from iPhone and Android. The website control plane is the commercial and administrative authority for QueueRove accounts, organizations, membership grants, named technician assignments, licensed capacity, legal acceptance, and entitlement. Browser state, URL parameters, email possession, payment-provider redirects, mobile storage, and provider state alone are not authority.
The iPhone and Android apps are companion clients provided at no separate charge for licensed technicians of a subscribed organization. The apps connect to the organization's own HaloPSA environment to create and update tickets and record time entries. Features may vary by app version and platform, and each app is released on its own schedule.
Subscriptions are purchased and managed through the QueueRove website only. The mobile apps do not offer in-app purchases, mobile pricing, or external-purchase prompts.
3. Accounts, organizations, and administration
An Account is one Auth0-backed human identity. An Organization is one isolated MSP tenant and commercial boundary. The user must act in an explicit active organization context, and server-side authorization must approve each sensitive action.
- Users must protect authentication factors, recovery material, devices, and sessions and promptly report suspected compromise.
- Organization administrators must assign only the grants and technician access each person needs.
- Email and support messages are not authority to change roles, ownership, billing, refunds, exports, or deletion state.
- Automated ownership transfer, support impersonation, and self-service sole-owner recovery are not currently available.
4. Pricing, billing, and licensed capacity
The standard catalog is published on the Pricing page in U.S. dollars, tax-exclusive, and applies to U.S. business customers with 1–49 active technicians. One or two technicians have an organization minimum; published volume rates apply to every licensed technician in the selected band. Non-U.S. and 50+ opportunities are handled through human sales review.
An authorized Owner or Billing Admin manages subscriptions through QueueRove-controlled flows and Stripe-hosted checkout and billing pages. Provider redirects or email alone do not create entitlement. Taxes, renewal terms, cancellation timing, and any refund terms shown in the purchase flow apply to the subscription.
No automated 50+ offer
The 50+ contact path is human-only. Submitting it does not create a quote, entitlement, trial, special price, contract, or technician seat.
5. Customer and user responsibilities
- Maintain lawful authority for users, records, devices, and the connected HaloPSA environment.
- Issue least-privilege HaloPSA permissions and protect Client Secrets, access tokens, passwords, MFA codes, and recovery codes.
- Confirm queued mobile work reached HaloPSA before repeating or deleting local state.
- Keep live customer records, card data, credentials, and unredacted screenshots out of support and public reports.
- Comply with applicable employment, privacy, tax, export, recordkeeping, and industry requirements.
6. Acceptable use
- Do not access an account, organization, device, HaloPSA environment, or record without authorization.
- Do not disrupt, overload, probe, bypass, or misuse security, billing, invitation, entitlement, or tenant-isolation controls.
- Do not upload malicious code or use QueueRove to violate law, privacy, intellectual-property, contractual, or employment rights.
- Do not misrepresent QueueRove availability, affiliations, certifications, or product capabilities.
- Do not reverse engineer except to the extent applicable law does not permit that restriction.
7. License and intellectual property
Subject to these terms and payment of applicable fees, ITECS Outsourcing, LLC grants each subscribed organization and its authorized users a limited, non-exclusive, non-transferable, revocable license to access and use the QueueRove service, and to install and use the QueueRove mobile apps on devices they own or control, solely for the organization's internal business use.
QueueRove, its software, apps, design, documentation, and branding are and remain the property of ITECS Outsourcing, LLC and its licensors. No rights are granted except as expressly stated in these terms. Feedback may be used to improve the service without obligation. Third-party components are licensed under their own terms; see the Licenses page.
Apps installed from the Apple App Store are licensed under Apple's Standard End User License Agreement except where these terms lawfully provide otherwise. Apple and Google are not parties to these terms and have no obligation to provide support, warranty, or maintenance for QueueRove.
8. Third-party services and mobile platforms
QueueRove depends on separately provided identity, email, billing, hosting, device, store, network, and HaloPSA services. Those services have their own terms, permissions, privacy practices, and availability, which QueueRove does not control.
HaloPSA is a third-party service. Compatibility references do not claim partnership, certification, sponsorship, or endorsement. QueueRove does not control the customer's HaloPSA ticket or customer records, and a current HaloPSA subscription configured by the customer is required for the mobile apps to function.
9. Privacy, support, and deletion
The Privacy Policy, Privacy Choices, Account Deletion, DPA, Subprocessors, Security, and Support pages describe the applicable data and request boundaries. Identity verification and, for authenticated sensitive actions, recent MFA are required before disclosure or mutation. A support email alone cannot authorize an export or deletion.
10. Changes, suspension, and termination
QueueRove may change, suspend, restrict, or discontinue functionality for security, legal, operational, payment, or third-party reasons. Material legal changes receive a new immutable version and, where required, reacceptance. Subscription and deletion state changes must follow the displayed approved flow and applicable signed terms.
The customer may cancel through the displayed billing flow, and either party may terminate for material breach that remains uncured after notice. On termination, access ends and QueueRove-controlled data is handled under the Privacy Policy retention schedule and any executed agreement.
11. Disclaimer of warranties
To the maximum extent permitted by law, the service and apps are provided as is and as available, without warranties of any kind, express, implied, or statutory, including implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement. QueueRove does not warrant uninterrupted or error-free operation, that queued mobile work will reach HaloPSA in every circumstance, or the availability, accuracy, or conduct of any third-party service, including HaloPSA, Apple, Google, Stripe, or Auth0.
12. Limitation of liability
To the maximum extent permitted by law, neither party is liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, revenue, data, or goodwill, even if advised of the possibility of those damages.
Except for the customer's payment obligations, a party's indemnification obligations, or liability that cannot be limited by law, each party's total aggregate liability arising out of or relating to the service is limited to the amounts the customer paid for the service in the 12 months before the first event giving rise to the claim. Some jurisdictions do not allow certain limitations; in those jurisdictions these limitations apply to the fullest extent permitted.
13. Indemnification
The customer will defend and indemnify ITECS Outsourcing, LLC against third-party claims arising from the customer's data, its HaloPSA environment, its violation of these terms or applicable law, or its users' misuse of the service, except to the extent the claim was caused by ITECS Outsourcing, LLC.
14. Governing law and venue
These terms are governed by the laws of the State of Texas, without regard to conflict-of-laws rules. The state and federal courts located in Dallas County, Texas have exclusive jurisdiction over disputes arising out of these terms, unless a signed agreement says otherwise, and each party consents to venue there. These terms do not impose arbitration or a class-action waiver.
15. General terms
- These terms, the documents they reference, and any executed agreement are the entire agreement for the service and supersede prior discussions.
- If a provision is unenforceable, the remainder stays in effect and the provision is enforced to the maximum extent permitted.
- A failure to enforce a provision is not a waiver of it.
- The customer may not assign these terms without consent, except to a successor in a merger or sale of substantially all assets; ITECS Outsourcing, LLC may assign to an affiliate or successor.
- Neither party is liable for delay or failure caused by events beyond its reasonable control.
- Notices to QueueRove go to support@itecsonline.com; notices to the customer go to the primary Owner email on file.
16. Contact
Contact ITECS Outsourcing, LLC at support@itecsonline.com with the QueueRove-specific subject that matches the request.
Related resources
Questions may be sent to support@itecsonline.com with the subject “QueueRove support”.