Flamingo Privacy Policy
Last updated: June 17, 2026
Flamingo is a local Chrome Declarative Net Request rule editor. It does not sell user data, does not use analytics or advertising SDKs, and does not send rules, browsing activity, or preferences to the developer's servers.
Data Flamingo Handles
Flamingo handles only data needed to provide its single purpose: creating and applying user-defined browser request rules. This may include:
- Rule names and enabled or disabled state.
- Rule conditions, such as URL filters, regular expression filters, domains, resource types, and HTTP methods.
- Rule actions, such as redirects, block actions, mock responses, and request or response header modifications.
- Extension preferences, such as language, popup size, rule engine state, and storage mode, single-active mode, and the last selected rule position.
- Optional AI assistant settings, such as provider, selected model, enabled state, and provider-specific API keys.
Because rules are created by the user, they may contain URLs, domains, header names, header values, or mock response content that the user enters.
Website Content and Request Processing
Flamingo requests host access for http://*/* and https://*/* so
user-created rules can match normal web requests. Chrome applies enabled Declarative Net
Request rules locally in the browser.
For user-created mock rules, Flamingo may evaluate request URLs in the page locally in order to return the configured mock response. Flamingo does not create a browsing history, does not analyze page content for profiling, and does not transmit this information to the developer.
How Data Is Used
Flamingo uses stored rules and preferences only to manage and apply the rules the user creates. Flamingo does not use this data for advertising, analytics, tracking, profiling, creditworthiness, or any purpose unrelated to the extension's request-rule editing functionality.
If the user explicitly enables the optional AI assistant and uses AI rule generation or editing, Flamingo sends the user's natural-language prompt and current rule or group context to the AI provider configured by the user. The AI response is used only to create a disabled rule draft or a reviewed edit draft for user approval.
Storage
By default, Flamingo stores rules and preferences in
chrome.storage.local on the user's current browser profile.
If the user chooses Chrome Sync storage mode in Settings, Flamingo copies rules and key
preferences to chrome.storage.sync so Chrome can synchronize them across
browsers where the user is signed in with the same Chrome account. Chrome Sync is optional
and controlled by the user.
AI assistant settings, including API keys, are always stored in
chrome.storage.local and are not copied to Chrome Sync by Flamingo.
Sharing and Third Parties
Flamingo does not send rules, browsing activity, preferences, or mock response data to the developer's servers. Flamingo does not sell, rent, or share user data with advertisers, analytics providers, data brokers, or other third parties.
If Chrome Sync storage mode is enabled, synchronization is handled by Google Chrome through Chrome's built-in sync infrastructure. Flamingo does not control Google's Chrome Sync service.
If the optional AI assistant is enabled, requests are sent directly from the extension to the selected AI provider's built-in official endpoint, using the provider-specific API key provided by the user. Flamingo does not proxy those requests through the developer's servers.
Network Requests
Flamingo does not make external network requests to collect, transmit, or analyze user data by default.
The optional AI assistant makes external network requests only after the user enables it and explicitly asks Flamingo to generate or edit rules. Those requests go to the user's configured AI provider and may include the user's prompt, current rule or group context, and the API key needed to authorize the provider request.
The network behavior performed by Flamingo is limited to the user-defined rules that the user creates and enables.
Permissions
- storage: saves rules and preferences locally or through Chrome Sync.
- declarativeNetRequest: applies enabled request rules in Chrome.
- declarativeNetRequestWithHostAccess: allows user-created rules to run on sites covered by host permissions.
- webRequest and webRequestBlocking: support local request-header operations and mock response handling for rules configured and enabled by the user.
- Host permissions for http and https sites: allow user-created rules to match regular web requests. Rules are applied only when created and enabled by the user.
User Choice, Retention, and Deletion
Users create rules manually and can enable, disable, edit, or delete them in the extension UI. Stored data remains in Chrome storage until the user deletes it, clears the extension's storage, or uninstalls Flamingo.
Contact
For privacy questions or deletion requests, contact mashichen1999@gmail.com.