Effective August 19, 2026

Privacy policy

Good Detour is designed so your redirect choices and browsing behavior never go to the developer. Rules stay on one browser unless you choose Chrome Sync.

What the extension stores

The extension stores the redirect rules you create, your pause-page preferences, whether redirects are enabled, and a total count of pause pages shown. By default, Chrome stores this information locally in the extension's private storage on your device.

No Good Detour account

This version does not create or operate a Good Detour account. Your Google account, Chrome Sync, and GitHub account (if you submit feedback) are separate third-party services governed by their own terms and privacy notices.

Optional Chrome Sync

If you enable Chrome Sync inside Good Detour, Chrome Sync stores and synchronizes your rule definitions, enabled setting, and pause-page preferences through your signed-in Google account. The local pause count is never synced. The developer cannot access your Chrome Sync data. Chrome advises that extension sync storage should not hold confidential data, so do not put sensitive or private URLs in synced rules. Each Chrome browser still requires its own approval for the source-site permissions used by synced rules. You can turn this feature off at any time; doing so stops using the synced copy on that browser but does not delete the copy used by your other signed-in Chrome browsers.

What the extension does not collect

Good Detour does not send visited domains, browsing history, page content, identifiers, or the local pause count to the developer. It contains no analytics, advertising, or tracking SDK. When you opt in to Chrome Sync, only the rule domains and destination URLs you entered plus related preferences are handled by Google's Chrome Sync service.

Permissions

Good Detour requests access to a domain only after you add that domain as the source of a redirect. That access is used to apply the redirect you requested. It uses Chrome's declarative network request system so the browser can perform the redirect without giving the extension the contents of each network request.

Sharing and sale

Good Detour does not sell, rent, or share personal information for cross-context behavioral advertising, and the developer does not receive it. It has not sold or shared personal information in the preceding 12 months. Browsing activity is not used for advertising, profiling, creditworthiness, or any unrelated purpose. Optional synchronization is performed by Google's Chrome Sync service at your request.

Delete your data

Open Good Detour Settings and use Privacy & data. Delete synced copy removes Good Detour's rules and preferences from Chrome Sync while keeping the current browser's copy locally. Delete all Good Detour data removes rules, preferences, and the pause count from the current browser and removes the shared Chrome Sync copy. The developer cannot perform these actions for you because it cannot access that storage.

A local pause count on another browser must be deleted on that browser. A JSON backup is a separate file under your control. Feedback submitted through GitHub is public and belongs to your GitHub account; edit or delete it using GitHub's controls. Uninstalling removes local extension storage according to Chrome's behavior, but use the in-product delete control first if you also want to clear Chrome Sync.

California and other U.S. state privacy rights

Depending on where you live and whether a privacy law applies, you may have rights to know or access personal information, delete it, correct it, opt out of its sale or sharing for cross-context behavioral advertising, limit certain uses of sensitive personal information, and receive equal service after exercising a right. Good Detour does not discriminate against anyone for exercising a privacy right.

The categories handled by this version are the source domains and destination URLs you enter, redirect and pause-page preferences, and a device-local aggregate pause count. They come directly from you and are used only to provide the features you request. The developer does not collect or disclose them. They remain in local storage or optional Chrome Sync until you delete them as described above. Because the developer has no copy, the in-product controls are the direct method for requests concerning extension data.

Future changes

If a future version introduces other optional remote features, it will explain the data involved in the product interface before collection and request affirmative consent where required. Material privacy changes will not be applied retroactively without notice and any required consent.

Chrome Web Store Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Contact

For privacy questions or applicable privacy-rights requests, email admin@productlab.ai. Do not include private URLs, account information, browsing history, or other sensitive information unless it is necessary for the request. General product feedback may use the public support tracker; never post a privacy-rights request publicly. Security-sensitive reports should follow the repository's security policy.