Acceptable Use Policy

Acceptable Use Policy

Last updated: 2026-06-05 (added Section 1.1 — Demo / Retail Display Units guidance)

This Acceptable Use Policy ("AUP") explains how you may and may not use Phoenix Service Tool. It supplements the Terms of Service.

1. Core Rules

Phoenix Service Tool may be used only on Devices that you legally own, or for which you have explicit written authorization from the legal owner. Service-shop usage on customer Devices is acceptable when the customer has authorized the requested Operation.

1.1 Demo / Retail Display units

Phoenix Service Tool can convert manufacturer demo / retail-display firmware ("Demo Mode", "Live Demo Unit", "Retail Mode") to standard consumer firmware. This is a legitimate feature: retailers routinely sell ex-display Devices into the consumer market after their display cycle ends, and those Devices need to be converted to normal user firmware to be usable.

You may use this feature only on Devices you legitimately acquired through proper retail decommissioning channels, typically a retailer's official "ex-display" sale or equivalent. Servicing a unit that was removed from a store display without authorization (theft, employee diversion, etc.) is treated the same as servicing any other stolen Device under Section 2.1 below, and is grounds for the same enforcement.

If you're a technician converting a customer's Device, ask them where they acquired it and decline the work if the answer doesn't add up. The burden of source verification rests with you.

2. Prohibited Activities

You agree not to use the Service to:

2.1 Service stolen, lost, or unauthorized Devices

  • Bootloader unlock, FRP removal, or Mi Cloud / Find My Device removal on a Device that is not yours and that you do not have authorization to service is strictly prohibited.
  • Reselling or facilitating the service of clearly-stolen Devices (e.g., Devices with active anti-theft locks the user cannot themselves disable) is grounds for immediate termination and reporting to relevant authorities where required by law.

2.2 Bypass security on devices you don't own

  • Even if you have physical possession of a Device, you may not use the Service to bypass account, FRP, anti-theft, or carrier locks unless you can demonstrate ownership or written authorization.

2.2a Identifier modification (illegal in most jurisdictions)

  • Do not use the Service to modify, repair, change, rewrite, or restore Device identifiers — IMEI, Serial Number (SN), MEID, MAC address, or any other manufacturer-assigned identifier. The Service does not provide this functionality and we will not add it. Tampering with these identifiers is a criminal offense in most countries.

2.2b MDM-enrolled / corporate-managed devices

  • Do not use the Service to bypass, remove, or unenroll Mobile Device Management (MDM) profiles on Devices that belong to a corporate, educational, or government organization, unless you have explicit written authorization from that organization. Servicing your own personal Device's MDM enrollment that you set up yourself is fine; bypassing your employer's enrollment is not.

2.2c Payment-installment / PayJoy / financed devices

  • Do not use the Service to bypass or remove locks on Devices that are subject to an active payment-installment plan, PayJoy lock, carrier financing agreement, or similar credit-purchase enforcement mechanism. These locks exist to enforce a payment obligation and bypassing them facilitates fraud against the financing party. Service these Devices only after the financing is fully paid off and the lock has been released by the financer.

2.3 Run automation / bots / scrapers

  • Do not script, automate, or pipeline Operations through bots. The Service is designed for interactive, technician-driven use.
  • Do not use the Service's responses to feed competing tools or aggregator services.

2.4 Circumvent limits or controls

  • Daily Operation limits, account caps, IP-based rate limits, and similar controls exist to keep the Service stable and fair. Do not attempt to bypass them by rotating accounts, IPs, or VPN endpoints.

2.5 Resell the binary

  • The desktop tool binary is licensed for use, not for redistribution. You may resell Credits under a Reseller agreement, but not the binary itself.

2.6 Reverse-engineer for competition

  • Internal investigation of the tool for your own understanding is fine. Reverse-engineering with the intent to clone, sell, or release a competing product is not.

2.7 Use for unlawful purposes

  • Anywhere a specific Operation is illegal under your local law, you may not perform that Operation, regardless of whether the Service technically allows it.

3. Reporting Abuse

If you become aware of Service abuse — for example, someone using a Phoenix Service Tool reseller account to launder stolen device IMEIs — please report it to [email protected] (include "ABUSE" in the subject line). Include:

  • The reseller account or user email if known.
  • A short description of the abuse.
  • Evidence (screenshots, log IDs, transaction IDs) where you have them.

We investigate every credible report and act within 48 hours.

4. Enforcement

Violation of this AUP may result in any of the following, depending on severity and history:

  • Warning for first-time minor violations.
  • Temporary suspension (typically 7-30 days) for repeated minor violations or single moderate violations.
  • Permanent termination for severe violations (stolen-device service, fraud, repeated bot use after warnings).
  • Credit forfeiture in cases of fraud or repeated AUP violations.
  • Report to law enforcement where the activity appears to violate criminal law.

We aim to be reasonable. We will normally contact you before taking permanent action unless the activity is fraudulent, criminal, or causing active harm to other users or the Service.

5. Cooperation with Law Enforcement

We cooperate with lawful requests from law enforcement when properly served and within scope. We may also proactively report activity that we reasonably believe constitutes criminal conduct (organized theft rings, fraud, money laundering) to the relevant authorities.

6. Changes

This AUP may be updated to address emerging abuse patterns or new Service features. The "Last updated" date reflects the most recent revision.

7. Contact

Questions about this policy or to report suspected abuse: [email protected] (use "ABUSE" in the subject line for abuse reports so we prioritize them).