Archived Terms of service
QueueRove Terms of Service
These draft terms describe the approved v1 business service and its boundaries. They are technically prepared but are not counsel-approved production terms.
- Version 2026-07-17-draft.1
- Effective date: Pending Texas counsel approval
- SHA-256
4a20f2b46961f3ba9fe8256938d04ca7ecd8b2efe3816f1c8bca01bb0f64bb76
Archived draft status
Technical draft pending Texas counsel review; production collection and charging also require tax/accounting signoff and explicit launch approval.
This repository-local document is not provider, deployment, counsel, tax, or production evidence. It makes no approval or launch claim.
The content hash is derived from the versioned structured source rendered on this page. Material changes require a new version, archive entry, and the approved reacceptance process.
View the current stable route → · View all archived documents
1. Operator and acceptance
QueueRove is operated by ITECS Outsourcing, LLC. QueueRove, we, and us refer to that operator. No street address, registration detail, or legal approval is represented by this draft.
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. Service and availability boundary
The approved v1 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, Stripe redirects, mobile storage, and provider state alone are not authority.
Availability is evidence-based
Repository code and this document do not prove that authentication, email, billing, database, mobile entitlement, or any provider integration is configured or deployed. Paid enrollment and charging remain closed until the documented external gates are satisfied.
The iPhone and Android apps are intended as free B2B companion clients for an MSP-managed service. Mobile login and entitlement work, native account-deletion entry points, signed-binary disclosures, and store review remain separate release gates. The apps must not present mobile pricing, Stripe checkout, upgrade prompts, or external-purchase calls to action in this phase.
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 available in v1.
4. Pricing, billing, and licensed capacity
The approved standard catalog is 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 require human review.
When production billing is separately approved and enabled, an authorized Owner or Billing Admin may use QueueRove-controlled flows and tightly configured Stripe-hosted pages. Provider redirects or email alone do not create entitlement. Taxes, renewal terms, cancellation timing, and any refund exception shown in the final approved purchase flow will control.
No automated 50+ offer
The 50+ contact path is human-only. Submitting it does not create a Stripe object, 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, provider readiness, store status, or product capabilities.
- Do not reverse engineer except to the extent applicable law does not permit that restriction.
7. Third-party services and mobile platforms
QueueRove may depend on separately configured identity, email, billing, hosting, database, device, store, network, and HaloPSA services. Those services have their own terms, permissions, privacy practices, and availability. A repository dependency is not proof that a provider is active in production.
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. Apple's Standard EULA is the planned initial mobile distribution term; current Apple and Google policies must be rechecked for each submission.
8. 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.
9. Changes, suspension, and termination
QueueRove may change, suspend, restrict, or discontinue functionality for security, legal, operational, payment, or third-party reasons. Material legal changes require a new immutable version and the approved reacceptance gate. Subscription and deletion state changes must follow the displayed approved flow and applicable signed terms.
10. Legal limitations and proposed governing law
Warranty disclaimers, liability limits, indemnity language, remedies, and enforceability require Texas counsel review before these terms become production terms. This technical draft does not invent a liability cap or legal waiver.
The approved product plan proposes Texas law and venue in Dallas County, subject to counsel approval. This draft does not add arbitration or a class-action waiver.
11. Contact
Contact ITECS Outsourcing, LLC at support@itecsonline.com with the QueueRove-specific subject that matches the request. No unconfirmed postal address or registration detail is published here.
Related resources
Questions may be sent to support@itecsonline.com with the subject “QueueRove support”.