SourceHop Privacy Policy

Effective date: October 2, 2026

SourceHop provides source navigation from configured development webpages to original source locations in VS Code through a local bridge on your computer.

Information SourceHop handles

Authentication information: the pairing token you enter for your local bridge. It is stored in the extension's local storage and sent to that bridge to authenticate requests. - Development-site information: configured origins, project identifiers, the current page's origin, and the local bridge address. SourceHop uses these to select the correct project and check authorization. It does not maintain a browsing-history log. - User interactions: modifier key state, pointer movement, and clicks on authorized development pages. These are processed to highlight mapped elements and trigger navigation; SourceHop does not keep an interaction history. - Website and source metadata: instrumented element identifiers and source paths, line numbers, and column numbers used to identify the source location. The local bridge resolves identifiers against the project's source registry. - Preferences: highlight, shortcut, appearance, and enabled pairing settings.

SourceHop ignores editable fields for shortcut interception and does not collect their typed contents. It does not collect names, email addresses, payment data, health information, personal communications, or geographic location.

Use and transmission

SourceHop uses this information solely for project pairing, element highlighting, source lookup, and editor navigation. It sends the project identifier, development origin, source identifier where applicable, and authentication token to the configured loopback bridge. That bridge opens the resolved source location using your local editor. The extension restricts bridge addresses to loopback hosts.

SourceHop has no analytics, advertising, or developer-operated collection server. The developer does not receive your pairing tokens, development-page contents, source files, or navigation requests through the extension. SourceHop does not sell data, use it for advertising or credit decisions, or transfer it to data brokers. All extension executable code is bundled in the installed extension.

SourceHop's use of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Storage, retention, and control

Pairings, tokens, and preferences remain in chrome.storage.local until changed, removed, or cleared. They are not stored using Chrome's sync storage. Tokens are restricted to trusted extension contexts; they are not embedded in webpage DOM attributes. Local extension storage is not an encrypted password vault.

You can disable or remove a pairing in Settings, revoke site access through Chrome, or uninstall the extension to remove its extension storage. Removing a pairing deletes its token from the extension's settings; reload open development tabs to remove an already injected content script. Project registrations, source registries, and bridge tokens on disk are separate local files and are not deleted by uninstalling the extension. You control and can delete those files yourself.

Support communications

If you email support, the maintainer receives your email address and the information you choose to include. This information is used to respond to your request and resolve the reported issue. Support messages are retained as needed to resolve requests and maintain relevant support records; you can request deletion by email.

Support email is handled using Gmail under Google's privacy policy. Do not include pairing tokens or private source code in support messages. Chrome Web Store may process its own service data independently of the extension.

Changes and contact

This policy will be updated if SourceHop's data practices change. The effective date above identifies the current policy. For privacy questions or requests, contact the maintainer through ghulammujtaba908@gmail.com.