Effective date: 2026-05-16

Privacy Policy

Altreurl is a Chromium extension for backend developers who need to route configured request URLs to local or alternate backend endpoints while debugging.

Data handled by the extension

Altreurl may handle the following data only when you configure rules that need it:

• Rule configuration, including source URL patterns, redirect target URLs, groups, pattern format, and enabled state.
• Request headers from matching source requests when credential sync is enabled.
• Authorization header values when manual mode or sync mode is enabled.
• Session cookie values when cookie sync is enabled.
• Browser localStorage or sessionStorage values from matching source-origin tabs when browser storage sync is enabled.
• The active tab URL, used by the popup to show rules relevant to the current page.
• Privacy-safe diagnostics logs, including local event names, rule counts, and dynamic rule apply errors.

How data is used

Altreurl uses this data only to provide its single purpose: configurable local debugging redirects with optional request header, authorization, and cookie forwarding.

• Match configured request URLs.
• Redirect matched requests to configured targets.
• Modify configured request headers.
• Sync selected credentials from the configured source request, browser storage, or cookies.
• Display relevant rules in the popup and options page.
• Show privacy-safe diagnostics and local logs for troubleshooting extension setup.

Chrome permissions

Altreurl requests Chrome permissions only to provide local request routing and debugging features:

• cookies: read configured source-origin session cookies when cookie sync is enabled.
• declarativeNetRequest and declarativeNetRequestWithHostAccess: redirect matching requests and modify configured request headers.
• host permissions: allow matching and routing only on URLs covered by your configured rules.
• scripting: read browser storage values from matching source-origin tabs when storage sync is enabled.
• storage: save rules, preferences, diagnostics logs, and local apply state.
• tabs: read the active tab URL so the popup can show rules relevant to the current page.
• webRequest: observe matching source requests so credential sync can learn selected headers.

Storage and sharing

Rule configuration, synced credential values, theme preference, diagnostics logs, and apply error state are stored locally in chrome.storage.local in your browser profile.

Altreurl does not:

• Sell user data.
• Transfer user data to advertising platforms or data brokers.
• Send rule configuration, headers, cookies, authorization values, or browsing activity to a remote server controlled by Altreurl.
• Use user data for advertising, credit-worthiness, or unrelated purposes.

When you enable a redirect rule, the browser sends the resulting request to the target URL you configured. That target may receive the headers, authorization value, or cookies you chose to set or sync as part of the debugging workflow.

Exported rule JSON files are created only when you click export. These files may contain sensitive rule data, so Altreurl shows a warning before exporting rules that include credentials.

Remote code

Altreurl does not load or execute remote code. All executable code is packaged with the extension and runs locally in the browser.

Retention

Rule configuration, diagnostics logs, synced credential values, and extension preferences remain in your browser profile until you delete rules, clear extension data, or uninstall the extension.

User control

You can remove stored data by deleting rules, clearing diagnostics logs in the options page, clearing extension site data, or uninstalling the extension from Chrome.

Limited Use statement

Altreurl's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Contact

For privacy questions or data-related requests, email yavanara.dev@gmail.com.