This policy covers the Chrome extension operated by Abdullah Khan, including the Google-account edition and older licence-key-only releases. Free domain-list tools do not require an extension account. The Google-account edition uses Google and Supabase for sign-in and Polar for purchase verification. Older releases validate licence keys directly with Polar.
The extension does not run usage analytics or advertising scripts, read your Gmail messages, or collect your browsing history. Opening an Ahrefs report sends the selected hostname to Ahrefs. Account and payment verification require the network communications described below.
Cleaner and Compare process the lists you enter locally. Saved domain lists and interface preferences remain in your Chrome profile and are not sent to the account service. When you open a traffic or authority report, the selected hostname becomes part of the report URL sent to Ahrefs. Ahrefs handles your activity on its website under its own policies. Copy and CSV actions export the selected results at your request.
In the Google-account edition, Google and Supabase process your Google identity, email and basic profile information to authenticate you. The extension stores session access and refresh tokens in Chrome local storage. A short-lived Google provider token is held in Chrome session storage for purchase ownership verification and can be sent to the Supabase-hosted account service and Google's identity endpoint. The developer does not receive your Google password.
The account service verifies the signed-in identity, links an eligible purchase to its owner and restores eligible Pro access on later sign-ins. Authentication, session refresh, licence linking, entitlement checks and installation management can each make network requests; requests are not limited to one per day.
Polar hosts checkout and handles billing as merchant of record. Card details are entered on Polar's checkout, not in the extension. The developer can access purchase records needed for customer support, including purchase email, order and licence information, but does not receive your full payment card number.
When you link a licence in the Google-account edition, the extension sends the key to the Supabase-hosted account service, which validates it with Polar and checks purchase ownership. The account database stores user, Polar customer, licence and benefit identifiers and relevant timestamps. It does not store the raw key in its licence table. Older releases store licence data using Chrome storage and send the key directly to Polar for validation. Legacy local or synced licence data may remain after an upgrade; the Google-account edition does not use it as proof of Pro access.
The Google-account edition creates a random installation identifier and secret. The server stores the identifier, a hash of the secret and timestamps to manage the two-installation allowance. This is an installation limit, not hardware fingerprinting. Signed entitlement proofs are stored locally and can support offline access for up to 24 hours after issue, or an earlier applicable expiry. The service also stores account-linked rate-limit counters to protect verification endpoints.
https://jlmmvbraebksomcubhke.supabase.co.Older releases request storage only. The Google-account edition adds identity and the specific Supabase host permission. Neither edition requests access to arbitrary page contents, Gmail messages or browsing history.
These providers may process technical connection information, including IP addresses, timestamps and operational logs. Their retention and processing arrangements depend on their services and policies; this policy does not promise that provider infrastructure keeps no logs. Provider infrastructure may process information outside your country.
Account and purchase information is used to provide authentication, paid access, installation management, security and customer support. It is not sold to data brokers or used by the developer for advertising or creditworthiness decisions. Necessary service-provider processing is described above. Authorized administration or support can involve access to relevant account records; this policy does not claim that no human can access them. Information received from Google APIs is subject to the applicable Google API Services User Data Policy, including Limited Use requirements.
Local saved lists remain until removed through the extension or its local data is cleared. Sign-out clears the current account session and cached account entitlement; it does not delete server-side account records, necessarily clear older synced licence data, or cancel billing.
The account service retains account, purchase-binding and installation records to provide access, restore purchases and enforce the installation allowance. Subscription cancellation alone does not erase these records. For account deletion or purchase recovery, contact itsabdullahkhan4@gmail.com from the relevant account or purchase email. Ownership must be verified before account records or purchase links are changed. Do not send passwords, Google verification codes or full payment-card details.
Deletion of extension account data and cancellation of a Polar subscription are separate requests. Polar retains billing records under its own retention and legal obligations. Provider backups and logs are governed by their retention arrangements; removing an application record does not imply immediate erasure from every provider backup.
Manage subscriptions through Polar. Signing out, removing an installation or uninstalling the extension does not cancel a subscription. Access follows the purchase entitlement and effective end date; cancellation may leave access available through the remaining paid or trial period.
This professional SEO tool is not intended for children under 13. This page is updated when data practices change. Check the update date and the disclosures in the installed edition.
Abdullah Khan · itsabdullahkhan4@gmail.com