Skip to main content
View product

Account deletion

Request account or organization deletion

Use authenticated privacy controls when possible. This public intake is for a locked-out person or someone who uninstalled a client; it never confirms account state before verification.

  • Version 2026-07-17-draft.1
  • Effective date: Pending Texas counsel approval
  • SHA-256 92905dd8257ba4af20fed35766d417c547290d55b4b208cbf3277aa18c6b8a83

Review and release 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.

Open the immutable archive route for this version → · View all archived documents

1. Before requesting deletion

  • If you can sign in, use the authenticated personal or primary-Owner privacy control and complete recent MFA.
  • Check mobile synchronization and confirm important work reached HaloPSA before removing local app state.
  • Do not send passwords, MFA or recovery codes, API credentials, card data, HaloPSA ticket contents, or unredacted screenshots.
  • A personal deletion cannot complete while you remain primary Owner of an organization; automated ownership transfer is not available.

2. Public deletion intake

The form below sends a routing request to the local QueueRove deletion-intake endpoint. Submission is not identity verification, does not prove that an account exists, and does not itself delete, export, suspend, or change any data. QueueRove uses the same generic receipt behavior whether or not supplied details match a record.

You may instead email support@itecsonline.com with the subject QueueRove privacy request. Email possession and correspondence alone are not deletion authority.

This public form is non-enumerating. Submission does not verify identity, confirm an account, or delete data. Do not include secrets or HaloPSA records.

3. What happens after intake

  1. QueueRove returns or sends a generic receipt without confirming whether an account or organization exists.
  2. An authorized workflow verifies identity and, for an organization request, primary-Owner authority and recent MFA.
  3. The request moves through Requested, Identity Verified, Approved, Scheduled, and Completed, Canceled, or Denied states with audit evidence.
  4. Approved deletion has a 7-day cooling-off period and may be canceled until destructive execution begins.
  5. The completion notice separates deleted, anonymized, retained with reason, provider-controlled, and outside-QueueRove categories.

4. Scope and exclusions

Deletion covers eligible QueueRove-controlled identity, organization, membership, assignment, and administration data. It does not authorize deletion of another tenant's data, customer-controlled HaloPSA records, device-local state, legally retained financial/contract evidence, or records controlled by another provider. Backup expiry follows the documented 35-day cycle with deletion tombstones reapplied after restore.

5. Response and completion targets

Initial response target: 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. Completion target: 28 days after identity verification. These are targets, not guaranteed resolution times; lawful holds or permitted extensions may apply.

6. Mobile deletion remains a separate gate

This website resource does not prove that Apple or Google account-deletion entry points, device erasure behavior, store disclosures, or mobile entitlement are complete. Those requirements must be verified against each signed native release before submission.

Questions may be sent to support@itecsonline.com with the subject “QueueRove privacy request”.