Google Chrome · Privacy at UA Pro

Privacy Policy

This policy explains how UA Pro handles user configuration and page and network information, and how that information may be stored, synchronized, or transmitted.

Last updated:  · Applies to UA Pro 1.5.0

01Information processed

UA Pro changes the User-Agent (UA) sent by the browser according to the user's rules and synchronizes related browser properties in supported pages. To provide these features, the extension processes:

  • Rules and settings: global and domain rules, custom UAs, appended text, the resource-domain fallback setting, interface language, appearance, and overlay settings.
  • Page and network information: open tabs and their URLs, main-page navigation events, request URLs, and the User-Agent sent, for matching rules, showing status, and managing random UAs. Request-header events supplied by the browser may contain other headers; the current code extracts the User-Agent for rule processing or the overlay. When the overlay is enabled, it also reads the UA visible to the current page's scripts.
  • Temporary state: tab rules, page-load identifiers, random-UA bindings, and application status used to apply the selected rules. When the overlay is enabled, the main-document request UA and URL hashes used to associate navigations are kept temporarily in session storage. When the overlay is turned off, the extension clears these overlay session records, including per-tab sizes; overlay settings saved locally remain.
  • Imported configuration: a local file selected by the user or configuration fetched from a user-specified URL. The extension validates the configuration and asks the user to confirm before importing it.

The current version does not automatically upload browsing history or the settings above to a developer server and has no built-in advertising or user-behavior analytics collection. It does not create a browsing-history list; processing the current page and network events still involves browsing activity information.

02Storage and synchronization

Global and domain rules, custom lists, and the resource fallback setting are saved using the browser's chrome.storage.sync. Whether they synchronize across devices, and which service is used, depend on the browser and the user's settings. For example, when Chrome sync is enabled, Google's sync service may process them; when they are not synchronized, the browser stores them locally.

Interface language, appearance, the overlay switch, and the overlay's position, size, and opacity are stored in the extension's local storage. To reduce size changes during navigation, the most recent window size is also stored locally, and each tab's window size is kept in session storage; the size cache does not contain a UA. Tab rules, page-load information, random bindings, and overlay request records are held in session storage or runtime memory; session data may be cleared when the extension reloads or the browser restarts.

03Transmission and sharing

  • Websites visited: the browser sends the chosen User-Agent to visited websites and their related resource services, according to the user's settings.
  • Welcome page after installation or update: the extension sends a HEAD request without browser credentials to the UA Pro website's welcome page for the selected or inferred language to check whether it is available. If available, the browser opens the page normally and loads its resources; otherwise, it opens the bundled welcome page. Page and resource requests may include cookies or other information according to browser settings. The website may receive ordinary request information, such as the IP address, request time, and headers; the URL path also reflects the interface language. The availability check does not send a list of visited websites or the rule configuration.
  • User-specified configuration services: when a user imports configuration from a direct HTTPS URL, the extension requests that address without browser cookies or other browser credentials, does not send a Referer, and does not follow redirects. UA Pro does not apply its configured UA rules to that request; other extensions or network devices may still modify it. Query parameters are sent to the service. Its operator may receive an IP address, request time, and ordinary headers; its own practices govern that information. Use trusted addresses.
  • Browser sync services: if browser sync is enabled, the browser's sync service (such as Google's) may process settings saved in sync storage, subject to that service's own privacy terms.

This version has no preset server endpoint for sending the developer browsing activity or settings. If a user selects an address operated by the developer or another third party for remote configuration, the request is sent to that user-selected service.

04Your choices and deletion

You can edit or remove rules and custom entries within the extension or uninstall it. You are responsible for managing files you export and copies that may exist on other synchronized devices.

The exported JSON file contains the global rule, domain rules, custom UA and appended-text lists, the resource-domain fallback setting, and the export timestamp. It does not contain the interface language, appearance, overlay settings, or temporary tab state. After validation and confirmation, importing replaces those saved configuration items with the complete configuration in the file.

Do not put unnecessary passwords, access tokens, or other sensitive information in custom UAs or configurations. Exported files may contain rules and text you entered.

05Data-use commitments

UA Pro does not sell or transfer user data outside approved uses, use or transfer it for purposes unrelated to the extension’s single purpose, or use or transfer it to determine creditworthiness or for lending purposes.

UA Pro’s use and transfer of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including its Limited Use requirements.

06Contact and changes

For questions about this policy or how the extension handles data, please use the email contact below.

If the extension’s data practices change, we will update this policy and the corresponding store disclosures and notify users as required.