Usage Guide: E-Commerce Platforms

Relevant source files

The following files were used as context for generating this wiki page:

• README.md
• README_zh.md
• renderer.js
• main.js
• CHANGELOG_v1.2.3.md
• index.html
• package.json
• setup.js

GeekEZ Browser is a specialized anti-detect browser designed for e-commerce operators managing multiple accounts on platforms like Amazon, TikTok, Facebook, and Shopee. Built on Electron, Puppeteer, and Xray-core, its primary purpose is to provide strict isolation between browser profiles to prevent account association and suspension. The browser achieves this through advanced fingerprint isolation, network environment separation, and a "Native Consistency" strategy to bypass sophisticated detection systems like Cloudflare Turnstile.

This guide outlines the browser's compatibility with various platforms, its core safety features, and the best practices required for successful multi-account management in an e-commerce context. The information is derived directly from the application's source code and documentation.

Sources: README.md:14-19, README_zh.md:14-18

Core Principles for E-Commerce Operations

Successful and safe multi-account management depends on a combination of the tool's capabilities and the user's operational discipline. The following principles are critical for avoiding detection on e-commerce platforms.

The diagram below illustrates the recommended workflow for safe account management.

Key Success Factors

The application's documentation emphasizes that browser fingerprinting is only one part of the equation. The following factors are weighted by importance for avoiding detection:

Factor	Weight	Description
IP Quality	50%	Use high-quality, clean residential or mobile IPs. The IP address is the most significant factor in account association.
Behavioral Patterns	25%	Actions should mimic a real user. Avoid high-frequency, repetitive, or robotic automation.
Browser Fingerprint	15%	The browser must present a unique and consistent fingerprint. GeekEZ is designed to handle this aspect.
Fixed Environment	10%	Each account should be consistently used within the same browser profile to maintain a stable fingerprint.

Sources: CHANGELOG_v1.2.3.md:66-71, renderer.js:302

Platform Compatibility Guide

GeekEZ Browser has been tested for compatibility with several major e-commerce and social media platforms. The safety rating depends on the platform's specific anti-fraud mechanisms and the user adhering to best practices.

Platform	Safety Rating	Recommendations & Notes
TikTok	✅ Safe	Canvas noise effectively prevents device association. Requires a clean residential IP.
Facebook	✅ Safe	WebDriver and automation flags are stripped. Avoid high-frequency automation.
Shopee	✅ Safe	Provides a stable fingerprint for the seller center. Use a fixed environment for each account.
Amazon (Buyer)	✅ Safe	Sufficient isolation for buyer and product reviewer accounts.
Amazon (Seller)	✅ Safe	TLS Fingerprint Safe. Usable for main seller accounts, but requires a high-quality residential IP and a fixed environment.
Cloudflare	✅ Pass	Successfully bypasses Turnstile (hCaptcha) due to the native injection strategy, which avoids detectable JS hooks.
Rakuten	✅ Safe	Requires a local (Japanese) IP address.
Mercado Libre	✅ Safe	Risk profile is similar to Amazon.

Sources: README.md:86-96, renderer.js:321-345, CHANGELOG_v1.2.3.md:50-57

Technical Features for E-Commerce Safety

GeekEZ Browser implements several layers of protection to ensure each profile is unique and isolated, making it suitable for sensitive e-commerce operations.

Advanced Fingerprint Isolation

The browser spoofs multiple layers of the browser fingerprint to create a unique identity for each profile. This is achieved without easily detectable JavaScript hooks, focusing instead on native browser arguments and minimal, non-intrusive noise.

The following diagram shows the fingerprint components that are randomized for each profile.

Key Fingerprinting Features

Feature	Description	Implementation Detail
Hardware Randomization	Each profile reports a different number of CPU cores and device memory, significantly increasing fingerprint uniqueness.	This is part of the generateFingerprint function.
Media Noise	Non-intrusive noise is added to Canvas, WebGL, and AudioContext APIs to generate unique hardware hashes for each profile.	A content script (content.js) is injected at document_start to apply these modifications.
TLS Fingerprint Safety	The browser uses a real, unmodified Chrome binary, ensuring the TLS (JA3) fingerprint matches that of a standard Chrome user. This is critical for platforms like Amazon that analyze TLS handshakes.	The setup.js script downloads an official Chrome for Testing build. The browser is launched directly without modifications that would alter the TLS stack.
WebRTC Protection	The disable_non_proxied_udp policy is enforced via a command-line argument, physically preventing the browser from leaking the user's real IP address through WebRTC.	The --force-webrtc-ip-handling-policy=disable_non_proxied_udp argument is passed on browser launch.
Timezone & Geolocation	The browser's timezone is automatically matched to the proxy's IP location to ensure consistency.	The timezone property is set within the profile's fingerprint object.

Sources: README.md:23-39, main.js:621, main.js:92-102, setup.js:154-165, CHANGELOG_v1.2.3.md:19-27

Secure and Isolated Profile Launch

When a profile is launched, the application orchestrates the creation of a completely sandboxed environment. This process ensures that no data (cookies, cache, etc.) is shared between profiles and that all network traffic is routed correctly.

The following sequence diagram illustrates the launch process:

Sources: main.js:497-683, renderer.js:616-621

Safe Profile Identification

To avoid detection methods that scan for automation markers, GeekEZ Browser uses the browser's bookmarks bar to display the current profile's name. This avoids injecting text into the document.title, a practice that can be flagged by some anti-fraud systems.

A bookmark named 🔍 Profile-1 (for example) is created in the bookmarks bar, providing a safe and visible way for the user to identify the active profile.

{
  "roots": {
    "bookmark_bar": {
      "children": [{
        "name": "🔍 Profile-Name",
        "type": "url",
        "url": "chrome://newtab/"
      }]
    }
  }
}

This simplified structure shows how the profile name is added as a bookmark.
Sources: main.js:569-572, README.md:62-63

Summary

GeekEZ Browser provides a robust and technically advanced solution for managing multiple e-commerce accounts. Its strength lies in its "Native Consistency" approach, which combines a real Chrome browser engine with deep fingerprint randomization and strict network isolation. By adhering to the platform compatibility guide and the core principles of IP quality and user behavior simulation, operators can significantly reduce the risk of account association and suspension on modern e-commerce platforms.

Sources: README.md:14-19, CHANGELOG_v1.2.3.md:88-92