GeoMask

1. Overview

GeoMask ("we", "our", or "the extension") is designed to give users complete control over their location, timezone, and WebRTC privacy while browsing the web. Privacy is fundamental to our architecture, which is why GeoMask processes all data locally on your device.

2. Data Collection & Usage

We do NOT collect or transmit any data to external servers or third-party tracking services:

• No Personal Information: We do not ask for or collect names, email addresses, IP addresses, or account details.
• No Location Tracking: Your real location and your spoofed coordinates stay strictly within your local browser runtime.
• No Telemetry or Analytics: We do not track features used, session duration, or usage statistics.

3. Local Storage

GeoMask uses the browser's chrome.storage.local API exclusively to save your customized preferences on your device:

• Your preferred spoofed city or custom coordinates & timezone.
• Global masking toggle and WebRTC leak protection settings.
• Your custom domain bypass whitelist rules.

This data remains stored on your local computer and is never shared, synced to external servers, or exported without your explicit action.

4. Optional Features & Network Calls

GeoMask makes network requests only when explicitly triggered by user actions:

• VPN Sync & City Lookup: When you click the Sync with VPN button, a one-time request is made to a public geolocation IP service (e.g. ipapi.co) to detect your current VPN IP country code and synchronize your timezone preset. No user identifiers are attached to this query.

5. Permissions Usage

GeoMask requests only the minimal permissions required to function:

• storage: To persist your preferences locally on your browser.
• scripting: To inject spoofing overrides synchronously into web pages at document start.
• privacy: To configure WebRTC IP handling policies and prevent local IP leaks.
• <all_urls> (Host Permission): To apply your location spoofing settings across web pages you choose to visit.