Privacy Policy for WHMCS License Check

Effective date: August 4, 2026

Developer name: RDP Arena
Contact email: support@rdparena.com

This Privacy Policy explains how the WHMCS License Check Chrome extension (the “Extension”) handles information. It applies to Extension version 1.0. The Extension is developed by RDP Arena. It is an independent tool and is not affiliated with, endorsed by, or produced by WHMCS Limited.

Summary: The Extension processes the current tab and license-check information only to detect WHMCS, assist with a lookup on WHMCS’s official verification page, and show a local five-result history. It has no developer-run server, analytics, telemetry, advertising, or account system. The developer does not receive the domains, page content, cookies, or verification results handled by the Extension.

1. Information the Extension handles

The Extension handles the following information when you use its toolbar popup:

Current tab URL and hostname. When you click the Extension, it reads the active tab’s URL and hostname. This lets it prefill the domain field and determine whether the current page can be checked for WHMCS.
Limited website content. The Extension locally examines up to the first 500,000 characters of the active page’s rendered HTML, selected page elements, metadata, links, and URL patterns for indicators associated with WHMCS. The page content is analyzed in memory and is not saved or transmitted.
Presence of a WHMCS-named cookie. As one possible detection signal, the Extension locally checks the active page’s script-readable cookies to determine whether a cookie name matches a WHMCS session-cookie pattern. It does not store or transmit cookie names, cookie values, or the cookie string. Only a general detection signal, such as “WHMCS cookie,” can be returned to the popup for display.
Domain entered or selected for verification. The Extension normalizes the domain and temporarily stores it with a timestamp so it can fill the domain field on WHMCS’s official verification page.
Verification result information. After you submit the form on WHMCS’s website, the Extension reads the domain field and the visible WHMCS result alert. It locally records the domain, whether the result was “Authorized” or “Not authorized,” the result message, the date and time, and whether the result changed from the previous locally saved result for that domain.

The Extension does not intentionally seek or retain names, email addresses, passwords, payment information, health information, private communications, precise location, or the contents of authentication cookies.

2. How the information is used

The information is used only to provide the Extension’s user-facing features:

detect whether the active page appears to use WHMCS;
prefill a domain for verification;
fill that domain on WHMCS’s official verification page after its captcha is available;
read the displayed verification outcome; and
show the five most recent locally saved results.

The information is not used for advertising, profiling, credit decisions, analytics, generalized market research, or any unrelated purpose.

3. Local storage and retention

The Extension uses chrome.storage.local. This storage is local to the Chrome browser profile and is not Chrome Sync storage.

Result history: The Extension keeps no more than five results, with one current entry per domain. Older entries are removed as new domains are checked. Results remain until they are replaced, you select Clear in the popup, or you uninstall the Extension.
Pending domain: A domain waiting to be filled on the WHMCS page is considered valid for five minutes. It is replaced when another verification is started and removed after a result is recorded. If neither event occurs, it may remain in local storage even though the Extension will not use it after five minutes. The current Clear button removes result history, but it does not remove an unconsumed pending-domain handoff.
Uninstallation: Chrome clears the Extension’s local storage when the Extension is removed.

The developer has no access to this local storage. The Extension does not upload or synchronize it to a developer-controlled server.

4. Network activity and third-party websites

The Extension makes no independent background requests using services such as fetch, XMLHttpRequest, WebSocket, or analytics SDKs. It contains no remotely hosted executable code.

When you choose to verify a domain, the Extension opens WHMCS’s official License Verification page over HTTPS and fills the domain field. The Extension does not click Submit, solve the captcha, or submit the form for you. If you click Submit, the WHMCS webpage sends the domain and ordinary browser request information to WHMCS. That page may also use third-party security and anti-abuse services, including reCAPTCHA. This processing is performed by the website and its service providers, not by the Extension developer.

Third-party processing on the verification page is governed by the WHMCS Privacy Policy and the terms applicable to services embedded by that website. The Extension developer does not control those services and does not receive the information submitted to them.

Google may separately process installation, update, and Chrome Web Store activity as part of providing Chrome and the Chrome Web Store. Google may provide the developer with aggregate store statistics, such as install counts and ratings, but not the domains or results stored by the Extension. Google’s independent processing is governed by the Google Privacy Policy.

5. Sharing, sale, and human access

The Extension does not sell user data. It does not share user data with advertisers, data brokers, analytics providers, or the Extension developer. No developer employee or contractor can read the locally processed page data, cookie data, domains, or saved results because that information is not sent to the developer.

The only external submission connected with the Extension’s purpose occurs when you choose to submit the domain on the WHMCS webpage, as described in Section 4.

6. Chrome permissions

activeTab: Provides temporary access to the tab on which you invoke the Extension so it can read the URL and perform the visible WHMCS detection.
scripting: Runs the packaged detection function in the active tab after you invoke the Extension. It is not used for continuous background monitoring.
storage: Stores the pending-domain handoff and the five-result history in Chrome’s local extension storage.
Access to the WHMCS verification page: A packaged content script runs only on https://www.whmcs.com/members/verifydomain.php* to fill the pending domain and read the displayed result.

7. Security

Data retained by the Extension stays in Chrome’s local extension storage. Any transmission initiated when you use the WHMCS webpage occurs over HTTPS. The Extension does not add separate encryption to Chrome’s local storage, so anyone who can access your device or Chrome profile may also be able to access locally stored extension data. Protect your device and browser profile accordingly.

8. Your choices and deletion

You can edit or replace the prefilled domain before opening the verification page.
You can choose not to submit the form on the WHMCS website.
You can select Clear to erase the five-result history.
You can uninstall the Extension to remove all data in its local extension storage.

9. Chrome Web Store Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information handled through Chrome permissions is used only to provide or improve the Extension’s disclosed, user-facing purpose.

10. Changes to this policy

This policy may be updated if the Extension’s functionality or data practices change. The effective date at the top of this page will be revised. Any materially different data practice will be disclosed as required before the changed practice is introduced.

11. Contact

For privacy questions or support, email support@rdparena.com.