top of page

Privacy Policy for Edge Syncer Extension

 

Last Updated: April 26, 2026
Operated By: Mr Mastering (www.mrmastering.com)

This Privacy Policy explains how Mr Mastering (“we”, “us”, or “our”) processes information when you use the Edge Syncer Chrome Extension (the “Service” or “Extension”). By installing and using Edge Syncer, you agree to this Privacy Policy.

​

1. Core Purpose

Edge Syncer has a single purpose: trade copying and trade-management workflows for supported platforms (including Tradovate, TopstepX, and TradingView).

​

2. Information We Process

The Extension processes the following categories of information:

  • Authentication/session data: Session headers and tokens needed to authenticate with supported trading platforms.

  • Trading/account data: Orders, positions, fills, account IDs/specs, account labels, balances, and related status data required for copier/risk workflows.

  • Extension account/subscription data: Extension sign-in token and subscription status data used to validate access to Extension features.

  • Settings and preferences: Theme, privacy masking preferences, copier settings, risk settings, companion settings, and other local configuration.

  • Optional session widget data: Coarse geo-location and weather data for the session widget.

  • Optional AI cloud fallback data: If enabled by you, AI companion prompt/context/conversation snippets sent to your configured cloud endpoint.

  • Diagnostics and support data: Runtime diagnostics/log data generated for troubleshooting.

​

3. How We Use Information

We use this information to:

  • Authenticate requests to supported platforms and extension services.

  • Detect/replicate trading actions across selected accounts.

  • Provide copier health, risk-management, and account status features.

  • Validate extension subscription/access status.

  • Render optional widgets/features (weather/location, AI cloud fallback).

  • Generate user-initiated diagnostic exports for troubleshooting.

We do not use this information for ad targeting or selling personal data.

​

4. Network Destinations and Third Parties

Depending on enabled features and your usage, data may be transmitted to:

  • Supported trading platforms/APIs (for trading and account operations).

  • Mr Mastering extension endpoints under https://www.mrmastering.com/_functions/* (including CTID validation and extension auth/status/logout flows).

  • Ably (ably.io) for real-time message transport used by extension workflows.

  • api.ip.sb and api.open-meteo.com for optional session widget location/weather functionality.

  • www.google.com/s2/favicons for account/firm favicon rendering.

  • Your configured AI cloud endpoint (optional, only when AI cloud fallback is enabled).

We do not sell your data.

​

5. Local Storage, Debug Logging, and Diagnostics

  • Edge Syncer stores operational state in Chrome local extension storage.

  • Debug/diagnostic logging may be enabled to support troubleshooting.

  • The “Export Diagnostic Report” action is user-initiated and can include storage snapshots and diagnostic payloads that may contain sensitive operational/account context.

  • You control whether to share exported reports with support.

​​

6. Permissions Justification (Manifest)

Edge Syncer requests only permissions used by extension features:

  • webRequest: Read request metadata/headers needed for supported authentication/session capture flows.

  • scripting: Inject packaged observer scripts on supported domains.

  • alarms: Run periodic maintenance/health/auth refresh tasks.

  • storage: Save extension settings, state, and diagnostics locally.

  • tabs: Manage workflow tabs and platform/login-related flows.

  • sidePanel: Provide the extension side panel UI.

  • offscreen: Support offscreen document workflows used by extension features.

  • host_permissions: Restrict page/API access to required domains only.

​​

7. Security and Retention

  • Most extension processing occurs locally in your browser context.

  • Data in transit is sent via HTTPS/WSS endpoints.

  • Retention of local extension data depends on your browser profile state and extension lifecycle.

​​

8. Changes to This Policy

We may update this policy to reflect product, legal, or Chrome Web Store requirement changes. We will update the Effective Date when changes are made.

​

9. Contact

If you have questions about this policy, contact us at:

bottom of page