Privacy Policy
Privacy Policy and Data Protection
Your privacy is very important to WindSeed. This Privacy Policy covers how we collect, use, disclose, transfer, and store your information for the WindSeed website and our Chrome extensions. Use the links below to jump to a product-specific section.
01Collection and Use of Personal Information
Personal information is data that can be used to uniquely identify or contact a specific individual.
You may be asked to provide your personal information anytime you are in contact with us (like when you fill out our contact form or sign up for a newsletter). You are not required to provide the information we requested, but if you choose not to do so, in many cases this means we will not be able to provide you with our products or services or respond to your inquiries.
02What, What for, and How We Use Your Personal Information
Currently we are collecting the following data when you interact with us:
- Email address: We collect your email address to contact you for offers. This is purely optional and you can unsubscribe from our mailing list at any time.
- Uninstall reason: If you visit the uninstall page after removing an extension and tap a reason tag or optionally type a short comment, we store that voluntary feedback (reason, extension ID, version, and coarse request metadata) to improve our products. You do not have to provide it.
03Analysis and Tracking Tools
We may use cookies and tracking tools to provide you with an optimal experience when visiting our websites and using our apps and digital offerings. To do this, we may use analytics and tracking tools to:
- Ensure functionality
- Usage analysis, in order to thereby be able to optimize the products
- Market research, thereby gaining insights into target groups
- For advertising
- For testing purposes (e.g. contract implementation for free and paid offers)
- For IT security and fraud prevention
Profiling or automated decision-making only takes place if this is expressly stated below. Otherwise, profiling or automated decision-making does not take place.
04Cookies
If cookies, device identifiers or other information are stored or retrieved on your end device for processing, the legal basis for this is the European Cookie or e-Privacy Directive in conjunction with the Telemedia Act or the General Data Protection Regulation. These services are largely integrated via the Google Tag Manager.
Cookies are text files that contain data of visited websites or domains and are stored by a browser on users' computers. The primary purpose of a cookie is to store information about a user during or after their visit within an online offer. Cookies can be set by us or by third parties.
In order to ensure the functionality of our digital offers, we process your data on the basis of our legitimate interest, by:
- Storing and/or retrieving information on a device
- Providing ads or content technically
For product optimization, we process your data based on our legitimate interest by:
- Measuring content performance
- Using market research to gain insights about target groups
- Developing and improving products
For personalization purposes, we process your data with your consent by:
- Creating a personalized ad profile
- Creating a personalized content profile
- Selecting personalized content
- Selecting personalized content and merging it with offline data sources
- Linking different devices
In order to be able to finance ourselves with advertising, we process your data with your consent by:
- Selecting simple ads
- Selecting personalized ads
- Measuring ad performance
We use precise location data only with your consent.
We do not actively query device properties for identification (fingerprinting).
05Google Analytics
This website uses Google Analytics, a web analytics service provided by Google, Inc. ("Google"). Google Analytics uses cookies, which are stored on your computer or mobile device and which allow an analysis of your use of the website. The information generated by the cookie about your use of this website (including your IP address) will be transmitted to and stored by Google on servers in the United States. In the event that IP anonymization is activated on this website, your IP address will be truncated beforehand by Google within member states of the European Union or in other contracting states to the Agreement on the European Economic Area. Only in exceptional cases will the full IP address be transmitted to a Google server in the USA and shortened there.
We use this information to evaluate your use of the website, compile reports on website activity for website operators, and provide other services relating to website activity and internet usage, including but not limited to Google Analytics Demographics and Interest performance reporting features. Google Analytics Demographics and Interest Reporting allows us to use data from Google's interest-based advertising and/or third-party data about our advertising audience (e.g., age, gender, and interests) in conjunction with Google Analytics for targeted and optimized advertising activities, strategies, and content on our website.
Google may also transfer this information to third parties where required to do so by law, or where such third parties process the information on Google's behalf. Google will in no case associate your IP address with other data stored by Google.
You may refuse the use of cookies by selecting the appropriate settings on your browser, however please note that if you do this you may not be able to use the full functionality of this website. You can also prevent the collection of data generated by the cookie and related to your use of the website (including your IP address) to Google and the processing of this data by Google by downloading and installing the browser plug-in available at tools.google.com/dlpage/gaoptout.
06Privacy Questions
If you have any questions regarding our Privacy Policy or data processing, or if you would like to make a complaint about a possible breach of local privacy laws, please contact us at admin[at]windseed.app.
Our Privacy Policy may change from time to time. When we change the policy, we will post the changes on this page.
08Chat Privacy Chrome Extension
This section applies to the Chat Privacy Chrome extension, which automatically hides chat history lists on supported AI chat websites to help protect privacy during screen sharing, presentations, or public use. Last updated: July 14, 2026.
Data Collection
This extension does not collect, store, or transmit personal data. It does not send browsing data, chat content, chat titles, account information, or page content to any server.
Data Usage
No user data is collected or used. The extension only reads and updates the local page display in supported AI chat tabs so that sidebar chat history can be hidden or shown.
Data Storage
The extension stores only user preferences: whether hiding is on or off, whether the optional page bubble is shown, the selected interface language, and the bubble position for each supported site. Preferences are stored with the browser's extension storage APIs so they can persist across browser sessions and, where the browser supports it, sync across the user's signed-in browser profile. They are not sent to the developer or any third party.
Data Sharing
The extension does not share data with third parties. No analytics, tracking, advertising, or remote logging services are used.
Permissions
- storage: Used only to save the user's preferences for hiding chat history and showing the optional page bubble.
- scripting: Used only after installation or update to refresh Chat Privacy on already-open supported tabs, avoiding the need for a manual page reload.
- Host access for supported AI chat websites: Used only to inject local page styles, a sidebar toggle button, and the optional page bubble on those websites.
Contact
If you have questions about this section, please contact us at admin[at]windseed.app or create an issue in the Chat Privacy GitHub repository.
09Puffer: AI Usage Tracker Chrome Extension
This section applies to Puffer: AI Usage Tracker (the Extension), which helps users monitor AI service usage limits for Claude, ChatGPT, Grok, and optional supported providers directly in Chrome and Firefox. Last updated: July 15, 2026.
Data Collection
The Extension does not collect, store, or transmit personal data to the developer or to any developer-operated server.
To provide its user-facing quota tracking features, the Extension may read usage and session information from supported AI services while you are signed in to those services in your browser. This information can include quota percentages, rate-limit values, reset times, plan status, provider connection status, and locally counted ChatGPT request timestamps and model names.
The Extension does not collect names, email addresses, payment details, passwords, chat message content, or browsing history across the web. For ChatGPT quota estimation, the Extension observes matching ChatGPT conversation request URLs and request metadata in order to count your own sent requests locally; it does not store or transmit the text of your conversations.
Data Usage
Data is used only to display AI usage meters, toolbar badge percentages, reset timers, provider connection status, and local threshold notifications.
Data Storage
All Extension settings and usage snapshots are stored locally in your browser using the WebExtensions storage APIs. Locally stored data may include enabled provider settings, display preferences, usage snapshots, notification state, detected ChatGPT plan status, and ChatGPT request counters. The Extension does not operate a backend service for collecting or storing user data.
Data Sharing
The Extension does not sell, share, or transfer user data to third parties. It makes direct requests from your browser to supported AI service domains, such as claude.ai, chatgpt.com, grok.com, gemini.google.com, and cursor.com, only for the purpose of reading your usage status or checking provider availability. Those requests are subject to the privacy policies of the corresponding services.
The Extension may also request the public product list from windseed.app (/api/products) to show other apps by the same developer in the settings page. That request does not include personal account data. The Extension may open an uninstall feedback page if you remove it; that page is separate from quota tracking and is not used to collect Extension usage data.
Permissions
- storage: Saves Extension settings, usage snapshots, notification state, display preferences, and local ChatGPT request counters in your browser.
- alarms: Refreshes usage data periodically and rotates toolbar badge display when enabled.
- notifications: Shows local alerts when configured usage thresholds are reached or reset.
- webRequest: Used only on matching ChatGPT request URLs to count your own ChatGPT conversation requests locally for quota estimation. It does not modify requests or read chat content for transmission.
- Host permissions for supported AI services: Request usage, rate-limit, session, or availability information from supported AI services while you are signed in.
- windseed.app: Used only to load the public product list and product logos for the in-extension “More apps” page.
Contact
If you have questions about this section, please contact us at admin[at]windseed.app or create an issue in the Puffer GitHub repository.
10US Stock Watch - Badge Prices Chrome Extension
This section applies to US Stock Watch - Badge Prices (the Extension), which displays selected US stock prices on the browser toolbar badge and provides a popup or side panel for watchlists, quotes, and charts. Last updated: August 18, 2026.
Data Collection
The Extension does not collect, sell, or share personal data. It stores the user's watchlist, display settings, and optional price alert configuration in Chrome storage so the Extension can work across browser sessions. It requests stock quote, search, intraday, and daily chart data from WindSeed market-data endpoints using only stock symbols selected or searched by the user.
Minimized Core-Feature Events
When the user installs the extension or performs a core action such as adding or removing a watch item, changing a tracked setting, opening charts or an external quote site, importing or exporting a backup, submitting feedback, or responding to a review prompt, the extension queues anonymous core-feature status events and later delivers them to Windseed in idle gaps. An event contains a schema version, random event and operation IDs, a product-scoped random install ID, a short-lived session ID, extension version, fixed feature name and status, coarse environment such as user agent and available UA-CH, OS/platform, locale/timezone, screen/viewport, color-scheme and reduced-motion preferences, and network hints, plus optional allow-listed setting keys, site identifiers, aggregate counts, or error codes. Events do not contain stock symbols, company names, search terms, prices, alert conditions, URLs, page content, account identifiers, cookies, or credentials. The install ID is never merged across products and is deleted when the user removes the extension or clears its storage. There is no in-extension analytics toggle.
Data Usage
Stored data is used only to provide the Extension's core features: showing the toolbar badge price, rendering the watchlist, caching recent quote and chart data, and triggering optional local price notifications. Stock symbols sent to WindSeed endpoints are used only to return market data requested by the Extension. Minimized core-feature events are used only to measure feature reliability and improve the Extension.
Data Storage
Watchlists, settings, and alert configuration are stored with chrome.storage.sync. Quote and chart caches, a product-scoped random install ID, and a queued list of minimized core-feature events are stored locally with chrome.storage.local. The Extension does not store personal data on a remote server.
Data Sharing
The Extension does not share user data with third parties. It communicates with stock.windseed.app and related WindSeed market-data services only to fetch stock market data required by the user's selected symbols. It also communicates with windseed.app for the in-product Windseed extension directory and to deliver the minimized core-feature events described above.
Permissions
- storage: Stores the watchlist, settings, alert configuration, local quote/chart caches, the anonymous install ID, and the core-feature event queue.
- alarms: Refreshes selected market data periodically so the toolbar badge stays current. Alarms are not used to send analytics.
- notifications: Shows optional local price alert notifications when configured alert conditions are met.
- sidePanel: Allows the user to open the watchlist and chart experience in Chrome's side panel.
- stock.windseed.app: Fetches stock symbol search, quote, intraday, and daily chart data for symbols selected or searched by the user.
- windseed.app: Loads the public product list and delivers the minimized core-feature events described above.
Remote Code
The Extension does not execute remotely hosted code. Remote requests are used only for market-data API responses and the minimized event endpoint described above.
Contact
If you have questions about this section, please contact us at admin[at]windseed.app or create an issue in the US Stock Watch GitHub repository.
11Delete Tab Groups Chrome Extension
This section applies to Delete Tab Groups, a Chrome extension that helps users manage Chrome tab groups and tabs and intentionally share the current tab or current group by QR code. It does not require an account and does not sell user data. Last updated: August 23, 2026.
Data Collection
Delete Tab Groups does not collect, transmit, store, or share personal browsing data on external servers for advertising or profiling. The only tab-data transfer is the optional, user-initiated encrypted group-sharing flow described below. It does not create user accounts, upload browsing history or page content, sell or transfer user data to third parties, or use data for advertising.
Optional Encrypted QR Sharing
A single-tab QR code directly contains the tab's HTTP(S) URL and is generated entirely on the device; its URL and title are not sent to Windseed. A group share is created only after the user clicks Create group QR code. The extension filters out browser-internal and local URLs, then encrypts the group name and remaining ordered titles and URLs on the device with a new 256-bit AES-GCM key. tabs.windseed.app temporarily stores only ciphertext, IV, format version, expiry information, and a hash of an independent revoke token for 1, 7, or 30 days. The decryption key remains in the URL fragment and is not sent to the server. The receiving page decrypts in browser memory, does not send plaintext back, requires no account, and never opens multiple tabs without a recipient click.
Minimized Core-Feature Events
When the user installs the extension, changes a tracked setting, imports or exports group rules, submits feedback, manually runs a tab-management action, or creates/revokes a QR share, the extension queues anonymous core-feature status events and later delivers them to Windseed in idle gaps. An event contains a schema version, random event and operation IDs, a product-scoped random install ID, a short-lived session ID, extension version, fixed feature name and status, coarse environment such as user agent and available UA-CH, OS/platform, locale/timezone, screen/viewport, color-scheme and reduced-motion preferences, and network hints, plus optional allow-listed setting keys or error codes. Events do not contain tab URLs, titles, domains, group names, share IDs or URLs, encryption keys, IVs, ciphertext, revoke tokens, exact link counts, page content, screenshots, account identifiers, cookies, or credentials. The receiving page sends no product events. The install ID is never merged across products and is deleted when the user removes the extension or clears its storage.
Data Storage
The extension stores local settings, optional board thumbnails, a product-scoped random install ID, and a queued list of minimized core-feature events in Chrome extension storage. Settings may be synchronized by Chrome through the user's signed-in browser profile. These records remain inside Chrome storage and are used only to provide the extension's functionality and product reliability.
Permissions
- storage: Saves user preferences, the optional event queue, and the product-scoped install ID.
- tabs: Finds, closes, moves, ungroups, archives, or dedupes tabs, and prepares a user-requested local QR or encrypted group share.
- tabGroups: Identifies which tabs belong to tab groups and updates groups the user selected.
- https://windseed.app/*: Loads optional product data and sends the minimized product events described above.
- https://tabs.windseed.app/*: Creates or revokes only a user-requested encrypted group share. Single-tab QR generation does not use this host.
Remote Code
Delete Tab Groups does not use remote code. All extension logic is packaged inside the extension bundle installed from the Chrome Web Store.
Contact
If you have questions about this section, please contact us at admin[at]windseed.app.
12Gmail Assistant Chrome Extension
This section applies to Gmail Assistant, a Chrome extension that adds optional writing, summarization, organization, follow-up, and privacy tools to Gmail. Last updated: July 18, 2026.
Data Processing
Email content is processed locally by default. If the user enables an AI provider and confirms a request, only the previewed email or draft content is sent directly from the browser to that selected provider. WindSeed does not receive or store the email content. Provider API keys are stored only in chrome.storage.local and are excluded from backups and synchronized settings.
Local Storage and Tracking
Settings, templates, notes, contacts, follow-ups, sequences, automation rules, and extension-observed analytics events are stored in Chrome extension storage. Optional analytics remain local. Email-open and link-click tracking is disabled by default and is not activated without a separately reviewed compliant backend and explicit user consent.
Permissions
- mail.google.com: Adds user-invoked assistant controls and reads the currently visible Gmail content needed for those actions.
- storage: Stores settings and local productivity data.
- alarms and notifications: Schedules and shows local follow-up reminders.
- AI provider hosts: Sends confirmed requests only to the provider selected by the user.
- windseed.app: Loads the public product list and opens install or uninstall information pages without email content.
Data Sharing and Contact
The extension does not sell personal data or use email content for advertising. Data sent to a user-selected AI provider is subject to that provider's privacy policy. Questions may be sent to admin[at]windseed.app.
13Doubao Image Cleaner Chrome Extension
This section applies to Doubao Image Cleaner (豆包原图助手), a Chrome extension that uses original-image URLs already returned to the user's Doubao web session. Last updated: July 21, 2026.
Data Processing
The extension runs locally in the browser. It examines Doubao page response objects and image links only to associate a watermarked display URL with the corresponding original-image URL. The latest captured original URL is held temporarily in the active tab so the user can click the branded download button; complete image URLs are not written to extension storage. Images, prompts, page text, account identifiers, and complete URLs are not uploaded to WindSeed or any extension-operated server.
Local Storage
Chrome local storage contains the enabled state, language and appearance preferences, diagnostic settings, aggregate replacement count, recent success time, and limited error codes. Optional anonymous usage events are off by default; if enabled, at most the latest 200 events remain on the device and are never transmitted. Review-invitation eligibility uses only minimal local aggregates such as success count, success days, and recent result status. These records do not contain image data, prompts, page text, account identifiers, or complete image URLs. The user can clear this data by removing the extension or clearing its extension storage.
Permissions
- www.doubao.com: Reads and changes image links on Doubao pages so eligible display links can use the original-image URL returned to the same browser session.
- storage: Saves local settings, limited diagnostics, optional local-only usage events, and minimal review-invitation aggregates.
- downloads: Saves a captured original image only after the user clicks the extension's branded download button. The extension does not read or manage existing download history.
Sharing, Remote Code, and Use
The extension does not sell or share personal data, does not use remote code, and does not remove invisible provenance credentials such as SynthID. It is intended only for images the user owns or is authorized to process. Questions may be sent to admin[at]windseed.app.
14Image Remix Workbench Chrome Extension
This section applies to Image Remix Workbench, a Chrome extension for user-initiated visual analysis and controlled image variation. Last updated: July 21, 2026.
User-Initiated AI Processing
The extension sends a selected reference image and the prompt fields chosen by the user directly from the browser to the AI provider configured by that user. WindSeed does not proxy, receive, or store these images, prompts, results, or API credentials. Processing by the selected provider is governed by that provider's own privacy policy and terms.
Local and Synchronized Storage
Provider API keys, reference images, generated images, project lineage, and review-eligibility counters are stored only in chrome.storage.local. Non-sensitive preferences such as theme, language, default provider, and default template may be stored in chrome.storage.sync. Optional minimized analytics are disabled by default and never include images, prompts, complete URLs, page text, API keys, account identifiers, or browsing history.
Permissions
- activeTab, scripting, and host access: Let the user select an image or capture an area on the active page and communicate directly with the configured AI provider.
- contextMenus and sidePanel: Provide user-invoked entry points and keep long-running tasks visible.
- storage: Store credentials and project data locally, and synchronize non-sensitive preferences.
- downloads: Save a generated image only after the user requests a download.
Remote Code and Contact
The extension does not execute remotely hosted code and does not sell personal data or use creative content for advertising. Questions may be sent to admin[at]windseed.app.
15Gemini Image Cleaner Chrome Extension
This section applies to Gemini Image Cleaner, a Chrome extension that lets users process and download images from supported Gemini and Google AI Studio pages. It removes only supported visible marks and does not attempt to remove or bypass SynthID or other invisible provenance signals. Last updated: July 29, 2026.
Image Processing and Network Access
Image decoding, visible-mark detection, image modification, format conversion, and ZIP creation run locally in the browser. When the user starts an operation, the extension reads the selected or current-conversation image from Gemini, Google AI Studio, or the Google-hosted image source already used by that page. Requests to those Google image hosts may use the user's existing browser session solely to retrieve the requested image. Images, prompts, conversation text, account identifiers, and complete image URLs are not uploaded to WindSeed or any extension-operated server.
Chrome Storage
Non-sensitive preferences such as language, light theme, output format, image quality, filename template, enabled state, toolbar visibility, ZIP behavior, and the local-event setting are stored in chrome.storage.sync and may be synchronized by Chrome through the user's signed-in browser profile. Toolbar position, installation time, minimal review-invitation aggregates, and at most the latest 50 anonymous local usage events are stored in chrome.storage.local. Local usage events are enabled by default, can be disabled in settings, never leave the device, and contain only fixed event names and limited properties such as supported site, output format, result category, or item count. Stored records do not include image data, prompts, conversation text, account identifiers, complete URLs, or browsing history. Removing the extension or clearing its extension storage deletes this data, subject to Chrome's own synchronization behavior for synced preferences.
Permissions
- gemini.google.com and aistudio.google.com: Adds user-invoked image controls and discovers images on supported pages.
- Google-hosted image domains: Retrieves only the image selected for a user-initiated operation when the page's normal image request cannot be read directly.
- downloads: Saves an individually processed image or a user-requested ZIP archive without reading or managing existing download history.
- storage: Stores synchronized preferences and the limited local records described above.
- activeTab: Lets a user-triggered toolbar action communicate with the current supported tab.
WindSeed Requests, Sharing, and Remote Code
On first installation, the extension opens the WindSeed installation page; Chrome may open the WindSeed uninstall page after removal. These URLs include only the extension ID, localized extension name, and extension version. Like an ordinary website request, WindSeed may also receive standard request metadata such as IP address, browser information, and request time under the Website section of this policy. No image, prompt, conversation text, account identifier, or complete image URL is included. The extension does not sell personal data, use image content for advertising, or execute remotely hosted code. It is intended only for images the user owns or is authorized to process. Questions may be sent to admin[at]windseed.app.
16TempoRefresh Chrome Extension
This section applies to TempoRefresh, a Chrome extension for scheduling page refreshes, detecting page changes, and running user-configured follow-up actions. Last updated: August 10, 2026.
Local Processing and Storage
Refresh tasks, schedules, page-change rules, selectors, notification settings, recipes, templates, execution history, diagnostics, and other extension preferences are processed and stored in Chrome extension storage. Page content is inspected in the active page only to run the task and checks configured by the user. WindSeed does not receive or store page content, complete browsing history, task URLs, selectors, captured values, or execution history.
Optional Sync and Anonymous Events
If the user enables Chrome Sync, eligible non-sensitive settings and task configuration may be stored in chrome.storage.sync and synchronized by Chrome through the user's signed-in browser profile. The device list contains only a random local device ID, a browser-provided platform label, and the last synchronization time so the user can review or forget devices. Secrets such as API keys, webhook credentials, and mail-provider credentials remain in chrome.storage.local and are excluded from synchronization and exported backups. Limited anonymous product events may be queued locally for up to eight hours before delivery to WindSeed. These events use fixed event names and coarse result properties for product reliability, and exclude page content, complete URLs, selectors, captured values, credentials, and account identifiers. There is no in-extension analytics toggle; this disclosure lives only in the privacy policy and Chrome Web Store privacy practices. Clearing extension storage deletes the local event queue.
User-Configured Integrations and AI
Webhook, email, and AI features run only when configured or invoked by the user. The extension sends the user-selected payload directly from the browser to the endpoint or provider chosen by that user. A change summary may include page text selected by the configured rule when the user chooses to send it to an AI provider. WindSeed does not proxy or store these payloads or credentials. Processing is governed by the selected provider's privacy policy and terms.
Permissions, Sharing, and Contact
- activeTab, scripting, and site access: Run user-created refresh, monitoring, scrolling, and click actions only on matching pages.
- alarms, notifications, and offscreen audio: Restore schedules, display user-configured local alerts, and play the built-in local alert tone only when sound is enabled.
- Optional power permission: Keep the device awake only while the user enables unattended mode and at least one task is running; release it when the last task stops.
- storage: Save local tasks, preferences, histories, diagnostics, credentials, and optional synchronized non-sensitive configuration.
- User-approved provider hosts: Deliver only the integration or AI request configured or confirmed by the user.
- windseed.app: Load the public product list and, when analytics is enabled, deliver the minimized anonymous events described above.
TempoRefresh does not sell personal data, use page content for advertising, or execute remotely hosted code. Removing the extension or clearing its extension storage deletes locally stored data, subject to Chrome's own synchronization behavior. Questions may be sent to admin[at]windseed.app.
17Footprint Purge Chrome Extension
This section applies to Footprint Purge, a Chrome extension that helps users review and remove their own Facebook activity through a read-only scan, a limited trial, explicit confirmation, and verifiable cleanup. Last updated: August 11, 2026.
Local Facebook Data Processing
Facebook content, complete URLs, Profile or Page identifiers, friend or group names, candidate snapshots, backups, failure evidence, and audit reports are processed and stored only on the user's device. User-requested exports do not pass through WindSeed services. Removing the extension or clearing its extension storage deletes locally stored extension data, subject to files the user has deliberately downloaded.
Minimized Core-Feature Events
Where the applicable legal basis permits collection without consent, the extension may send fixed core-feature events for scan, trial, cleanup, pause, and verification reliability. An event contains only a schema version, environment, fixed event name and phase, random operation UUID, timestamp, extension version, and optional non-negative aggregate counts or an allow-listed reason code. Events do not contain Facebook content, complete URLs, account, Profile or Page identifiers, browsing history, email addresses, cookies, Authorization headers, credentials, secrets, or free-text properties. Requests omit credentials and use a no-referrer policy.
Regional Privacy Gate
Before an event can be queued or sent, the extension requests a versioned regional privacy decision from WindSeed without credentials or a referrer. The response contains only a broad consent-required or other region group and the applicable legal basis; it does not return a precise location. Footprint Purge has no analytics-consent interface, so consent-required users are not tracked unless valid consent is available. Collection is allowed only for the explicit other and legitimate-interest combination. Offline, timeout, non-success, malformed, unknown, or policy-error responses fail closed, and any existing queue remains unsent.
Permissions and WindSeed Requests
- storage: Stores settings, task checkpoints, candidates, backups, evidence, and audit records locally so work can be reviewed, paused, resumed, verified, or cleared by the user.
- www.facebook.com: Performs the user-requested read-only scan and confirmed cleanup only on supported Facebook pages.
- windseed.app: Loads the public product catalog and privacy decision, delivers only permitted minimized events, and opens official product, privacy, installation, or removal pages.
Installation and removal page URLs contain only the extension ID, localized extension name, and extension version. Like an ordinary website request, WindSeed may receive standard request metadata such as IP address, browser information, and request time under the Website section of this policy. Footprint Purge does not sell personal data, use Facebook content for advertising, or execute remotely hosted code. Questions may be sent to admin[at]windseed.app.
18tata Chrome Extension
This section applies to tata, a Chrome extension that sends one prompt into official AI chat websites the user already signed in to, then compares answers in a workbench, window board, or sidebar. Last updated: August 17, 2026.
Local Control of Official AI Websites
tata is a remote control for tabs and windows the user already owns. Prompts, attachments, answers, and sign-in cookies stay inside the official AI websites selected by the user. The extension does not proxy those conversations through a tata server, does not store API keys, and does not read website passwords. Page content is inspected only on declared AI hosts, and only to send a user-started prompt, apply a saved model or effort setting, capture the resulting answer for the local comparison surface, or insert page context the user requested.
Chrome Storage
Non-sensitive preferences such as enabled AI slots, layout, theme, appearance, language, shortcuts, toolbar behavior, and model or effort settings are stored in Chrome extension storage and may be synchronized by Chrome through the user's signed-in browser profile. Draft prompts, local comparison history, and a queued list of minimized core-feature events remain on the device. Stored records do not include API keys, website credentials, complete conversation URLs, or full prompt and answer text sent to WindSeed.
Minimized Core-Feature Events
The extension may queue fixed core-feature events for product reliability, such as opening a workbench, sending a comparison, or changing a setting. Events are stored locally first and later delivered to WindSeed in idle gaps. An event contains a schema version, random identifiers, extension version, fixed feature name and status, coarse environment such as browser and locale, and optional allow-listed result or error codes. Events do not contain prompts, answers, attachments, complete URLs, account identifiers, cookies, or credentials.
Permissions
- storage: Saves preferences, local drafts, comparison history, and the minimized event queue described above.
- tabs, scripting, and webNavigation: Open, arrange, and talk to official AI tabs or windows after the user starts an action. Sensitive tab fields are used only to keep those AI surfaces aligned with the workbench, window board, or sidebar.
- sidePanel and system.display: Open the Chrome side panel and place window-board panes on the current display work area.
- declarativeNetRequest: Removes frame-blocking headers only for declared AI hosts so the workbench can embed those official pages. Other sites are not modified.
- alarms: Optional local scheduling for flushing the on-device event queue. Alarms are not used to read page content.
- Declared AI website hosts: Send the user's prompt and read the resulting answer only on the official chat sites the user enabled.
- Optional broader site access: Used only after the user asks to add the current non-AI page as sidebar context.
- windseed.app: Opens official product, privacy, installation, or removal pages, loads the public product catalog, and delivers only the minimized events described above.
Installation and removal page URLs contain only the extension ID, localized extension name, and extension version. Like an ordinary website request, WindSeed may receive standard request metadata such as IP address, browser information, and request time under the Website section of this policy. tata does not sell personal data, use chat content for advertising, or execute remotely hosted code. Questions may be sent to admin[at]windseed.app.
19Pane Grid Chrome Extension
This section applies to Pane Grid, a Chrome extension that splits tabs into real Chrome windows, tiles or snaps those windows across one or more monitors, and saves or restores window layouts when the user starts an action. Last updated: August 17, 2026.
Local Window Arrangement
Pane Grid rearranges Chrome windows and tabs on the user's computer. Page content stays in those Chrome windows. The extension does not inject into arbitrary websites, does not read page text, and does not proxy browsing through a Pane Grid server. Named-layout restore uses tab URLs only after the user grants the optional tabs permission and starts a save or restore action.
Chrome Storage
Saved layouts, split presets, theme, appearance, language, toolbar-button binding, and other non-sensitive preferences are stored in Chrome extension storage and may be synchronized by Chrome through the user's signed-in browser profile. A queued list of minimized core-feature events remains on the device. Records sent to WindSeed do not include page URLs, page content, account identifiers, or credentials.
Minimized Core-Feature Events
The extension may queue fixed core-feature events for product reliability, such as applying a split, snapping a window, or restoring a layout. Events are stored locally first and later delivered to WindSeed in idle gaps. An event contains a schema version, random identifiers, extension version, fixed feature name and status, coarse environment such as browser, locale, and timezone, and optional allow-listed result or error codes. Events do not contain page URLs, page content, user-entered layout names, account identifiers, cookies, or credentials.
Permissions
- storage: Saves layouts, presets, preferences, and the minimized event queue described above.
- system.display: Reads display work-area bounds so tile, snap, and multi-monitor moves stay on the visible desktop.
- contextMenus: Adds right-click actions the user starts, such as splitting the current tab or snapping the current window.
- Optional tabs: Used only after the user grants it, to save or restore named layouts that include tab URLs.
- Optional tabGroups: Used only after the user grants it, to keep Chrome tab groups intact when rearranging or restoring.
- Optional notifications: Used only after the user grants it, to show a local completion notice for a user-started action.
- windseed.app: Opens official product, privacy, installation, or removal pages, loads the public product catalog, accepts in-product feedback, and delivers only the minimized events described above.
Installation and removal page URLs contain only the extension ID, localized extension name, and extension version. Like an ordinary website request, WindSeed may receive standard request metadata such as IP address, browser information, and request time under the Website section of this policy. Pane Grid does not sell personal data, use page content for advertising, or execute remotely hosted code. Questions may be sent to admin[at]windseed.app.
20PlayLatch Chrome Extension
This section applies to PlayLatch, a Chrome extension that adds seek, volume, mute, speed, fullscreen, and optional loop or picture-in-picture controls to Instagram Reels, Stories, and Feed videos, and can latch volume, mute, and speed onto the next video. Later platforms such as YouTube Shorts, TikTok, and Facebook Reels stay off until the user grants those sites. Last updated: August 19, 2026.
On-Page Video Controls
PlayLatch inspects HTML video elements only on Instagram and on optional sites the user has authorized. It does not download video or audio files, does not read captions or comments, and does not send page URLs, video identifiers, or playback position to WindSeed. Volume, mute, and speed preferences are stored in Chrome extension storage so they can be reapplied after a swipe or a restart.
Chrome Storage
Enabled state, theme, appearance, language, keyboard, toolbar binding, loop points, optional-platform flags, latched volume/mute/speed, and a queued list of minimized core-feature events are stored in Chrome extension storage. Latched playback preferences may synchronize through the user's signed-in Chrome profile. Stored records sent to WindSeed do not include page URLs, video titles, account identifiers, or credentials.
Minimized Core-Feature Events
The extension may queue fixed core-feature events for product reliability, such as toggling the control bar, seeking, changing volume or speed, opening help, or submitting feedback. Events are stored locally first and later delivered to WindSeed in idle gaps, targeting about eight hours rather than a strict timer, and without Chrome Alarms. An event contains a schema version, random identifiers, extension version, fixed Chinese feature name and status, coarse environment such as browser, locale, and timezone, and optional allow-listed error codes. Events do not contain page URLs, video content, playback position, account identifiers, cookies, feedback body, or contact email. There is no in-product analytics switch; this disclosure is the privacy notice for that queue.
Permissions
- storage: Saves preferences, latched playback values, the review-invitation state, and the minimized event queue described above.
- instagram.com: Injects the on-page control bar only on Instagram Reels, Stories, and Feed videos.
- Optional youtube.com, tiktok.com, facebook.com, and scripting: Used only after the user grants them, to inject the same control bar on those short-video sites.
- windseed.app: Opens official product, privacy, installation, or removal pages, loads the public product catalog, accepts in-product feedback, and delivers only the minimized events described above.
Installation and removal page URLs contain only the extension ID, localized extension name, and extension version. Like an ordinary website request, WindSeed may receive standard request metadata such as IP address, browser information, and request time under the Website section of this policy. PlayLatch does not sell personal data, use video content for advertising, or execute remotely hosted code. Questions may be sent to admin[at]windseed.app.
21Phone Shape Chrome Extension
This section applies to Phone Shape, a Chrome extension that draws a device frame around the current webpage, spoofs a mobile viewport and user-agent for that tab, and can capture a screenshot or optional local recording. Last updated: August 19, 2026.
On-Page Preview
After a user gesture, Phone Shape injects an isolated overlay and a main-world viewport/user-agent spoof on the active tab only. It does not read the page body for analytics, does not upload screenshots or recordings, and does not send page URLs to WindSeed. Screenshots and optional WebM recordings stay on the user's computer.
Chrome Storage
Device preferences, theme, appearance, language, toolbar binding, custom device presets, review-invitation state, and a queued list of minimized core-feature events are stored in Chrome extension storage. Preferences may synchronize through the user's signed-in Chrome profile. Stored records sent to WindSeed do not include page URLs, screenshot pixels, recordings, account identifiers, or credentials.
Minimized Core-Feature Events
The extension may queue fixed core-feature events for product reliability, such as starting preview, changing device, rotating, capturing a screenshot, opening help, or submitting feedback. Events are stored locally first and later delivered to WindSeed in idle gaps, targeting about eight hours rather than a strict timer, and without Chrome Alarms. An event contains a schema version, random identifiers, extension version, fixed Chinese feature name and status, coarse environment such as browser, locale, and timezone, and optional allow-listed error codes. Events do not contain page URLs, page content, screenshot files, user-agent strings of the simulated site as page content, feedback body, or contact email. There is no in-product analytics switch; this disclosure is the privacy notice for that queue.
Permissions
- activeTab and scripting: Inject the overlay and viewport spoof on the current tab after the user clicks the toolbar, a shortcut, or the context menu.
- declarativeNetRequest: Applies a session User-Agent and Client Hints rule to the current tab so the site can serve a mobile layout. Rules are removed when preview stops.
- storage: Saves preferences, custom devices, the review-invitation state, and the minimized event queue described above.
- contextMenus: Adds a page menu item to start preview.
- offscreen: Crops and encodes the screenshot PNG locally.
- Optional localhost / 127.0.0.1: Requested only when the user previews a local development origin.
- Optional tabCapture: Requested only if the user starts a local recording. The recording is not uploaded.
- windseed.app: Opens official product, privacy, installation, or removal pages, loads the public product catalog, accepts in-product feedback, and delivers only the minimized events described above.
Installation and removal page URLs contain only the extension ID, localized extension name, and extension version. Like an ordinary website request, WindSeed may receive standard request metadata such as IP address, browser information, and request time under the Website section of this policy. Phone Shape does not sell personal data, upload screenshots or recordings, hijack search, or execute remotely hosted code. Questions may be sent to admin[at]windseed.app.
22FeedHide Chrome Extension
This section applies to FeedHide, a Chrome extension that hides social feeds, Shorts, Reels, and recommendation modules while leaving search, subscriptions, messages, and a specific video available. Last updated: August 19, 2026.
On-Page Hiding
FeedHide injects hide styles on supported social sites after the user turns a switch on. It does not upload page content, feed text, URLs, or account identifiers to WindSeed. Optional on-page overlays stay in the current tab.
Chrome Storage
Site rules, theme, appearance, language, toolbar binding, optional self-control settings, a hashed settings password if the user sets one, review-invitation state, and a queued list of minimized core-feature events are stored in Chrome extension storage. Preferences may synchronize through the user's signed-in Chrome profile. Stored records sent to WindSeed do not include page URLs, feed content, account identifiers, passwords, or credentials.
Minimized Core-Feature Events
The extension may queue fixed core-feature events for product reliability, such as turning hiding on or off, pausing a site, opening help, or submitting feedback. Events are stored locally first and later delivered to WindSeed in idle gaps, targeting about eight hours rather than a strict timer, and without Chrome Alarms. An event contains a schema version, random identifiers, extension version, fixed Chinese feature name and status, coarse environment such as browser, locale, and timezone, and optional allow-listed error codes. Events do not contain page URLs, page content, feedback body, or contact email. There is no in-product analytics switch; this disclosure is the privacy notice for that queue.
Permissions
- storage: Saves preferences, the optional password hash, review-invitation state, and the minimized event queue described above.
- youtube.com, facebook.com, instagram.com, x.com, reddit.com, and linkedin.com: Inject hide styles only on those sites when the user enables a rule.
- Optional extra sites: Requested only if the user allows TikTok, Threads, Bluesky, Hacker News, Twitch, or Pinterest.
- windseed.app: Opens official product, privacy, installation, or removal pages, loads the public product catalog, accepts in-product feedback, and delivers only the minimized events described above.
Installation and removal page URLs contain only the extension ID, localized extension name, and extension version. Like an ordinary website request, WindSeed may receive standard request metadata such as IP address, browser information, and request time under the Website section of this policy. FeedHide does not sell personal data, hide entire websites by default, or execute remotely hosted code. Questions may be sent to admin[at]windseed.app.
23Short Drama Helper Chrome Extension
This section applies to Short Drama Helper (短剧助手), a Chrome extension that adds playback speed, auto next, Picture-in-Picture, fullscreen, local resume, and favorites on supported short-drama and mini-drama web players such as ReelShort, DramaBox, NetShort, GoodShort, and ShortMax. It does not host, produce, or stream short-drama videos. Last updated: August 19, 2026.
On-Page Playback Helper
Short Drama Helper injects an isolated helper layer only on listed short-drama domains after you open a player page. It stays dormant on checkout, payment, billing, order, and wallet paths. It does not download protected video streams, bypass DRM or paywalls, or send drama titles, episode numbers, page URLs, or playback position to WindSeed.
Chrome Storage
Settings, keyboard shortcuts, watch progress, favorites, optional update-reminder state, optional provider credentials, review-invitation state, and a queued list of minimized core-feature events are stored in Chrome extension storage. Optional provider API keys stay in local storage and are never written to export files. Stored records sent to WindSeed do not include drama titles, platforms, episode labels, page URLs, progress, favorites, subtitles, images, account identifiers, or credentials.
Optional Provider Requests
Optional translation or image recognition runs only after you configure your own OpenAI-compatible HTTPS endpoint and explicitly start the action. The request goes to that endpoint with your key. WindSeed does not proxy those requests. A vision request uses a local image you pick for that action and does not persist the image.
Minimized Core-Feature Events
The extension may queue fixed core-feature events for product reliability, such as playback controls, favorites, library import, duplicate merge, opening help, or submitting feedback. Events are stored locally first and later delivered to WindSeed in idle gaps, targeting about eight hours rather than a strict timer. An event contains a schema version, random identifiers, extension version, fixed Chinese feature name and status, coarse environment such as browser, locale, and timezone, and optional allow-listed error codes. Events do not contain page URLs, drama content, feedback body, or contact email. There is no in-product analytics copy; this disclosure is the privacy notice for that queue.
Permissions
- storage: Saves preferences, watch progress, favorites, optional reminder state, optional provider credentials, review-invitation state, and the minimized event queue described above.
- alarms: Schedules lightweight on-device checks for optional episode reminders the user enables. It does not poll remote drama APIs or invent episode updates.
- notifications: Shows optional local reminders only after the user enables them.
- Listed short-drama hosts: Injects the helper only on supported player domains such as ReelShort, DramaBox, NetShort, GoodShort, and ShortMax.
- Optional https://windseed.app/*, https://*/*, and localhost: WindSeed is used for official pages, the public product catalog, in-product feedback, and the minimized events above. Other origins are requested only for a user-configured provider after an explicit translate or recognition action.
Installation and removal page URLs contain only the extension ID, localized extension name, and extension version. Like an ordinary website request, WindSeed may receive standard request metadata such as IP address, browser information, and request time under the Website section of this policy. Short Drama Helper does not sell personal data, use drama content for advertising, or execute remotely hosted code. Questions may be sent to admin[at]windseed.app.
07SocialMiner Chrome Extension
This section applies to the SocialMiner Chrome extension (also known as Sort Feed), which sorts, filters, exports, and downloads posts, Reels, videos, images, and user-visible follower/following lists that are already available to you on Instagram, TikTok, and Facebook. It can also maintain an optional on-device account library and collection console. Last updated: August 24, 2026.
Data Collection
SocialMiner does not collect, sell, or transmit personal information, authentication information, browsing history, social-media account identifiers, or social-media page content to the developer. The minimized core-feature result events described below do not contain those data categories.
The Extension reads supported page content only to provide the sorting, filtering, exporting, downloading, account-library, collection-console, and People Export features you request. This processing happens locally in your browser. Exported CSV, TSV, JSON, or XLSX files and downloaded media are saved only to destinations you select through the browser.
The Extension may contact windseed.app to retrieve non-personal selector configuration and a list of other WindSeed products, submit feedback you explicitly write, and deliver the minimized core-feature events described below. On first installation it opens a WindSeed installation page, and Chrome may open a WindSeed uninstall page after removal. Those lifecycle URLs contain only the Extension ID and version; they do not include social-media account information, local library records, People records, or page content.
Minimized Core-Feature Events
When a user-requested core action finishes, SocialMiner may queue one succeeded or failed result event and later deliver it to Windseed during a natural program-running opportunity, targeting about eight hours rather than a strict timer and without Chrome Alarms. An event contains random event and operation IDs, extension identity/version, a fixed feature identifier and Chinese feature name, final status, entry point, duration, interface locale, coarse browser/device context (user agent, platform, languages, timezone, screen, and optional network hints), and an allow-listed error code/stage for failures. It never contains social-media accounts, usernames, user IDs, posts, URLs, captions, filters, People records, downloaded media, feedback body/contact email, page content, cookies, credentials, or browsing history. There is no analytics setting in the Extension UI; this policy and the Chrome Web Store privacy disclosure describe the queue.
Data Usage
Supported page content is used only to provide the Extension's user-facing sorting, filtering, viral-score, export, download, account-library, collection-console, and People Export features. Extension settings are used only to remember your preferences. Minimized events are used only to measure feature reliability and improve the Extension. SocialMiner does not use user data for advertising, creditworthiness, lending, or any purpose unrelated to the Extension's single purpose.
Data Storage
Preferences such as theme, language, download settings, panel settings, and feature toggles are stored with Chrome's local or synchronized extension storage. On-device account-library entries, aggregated post caches, collection/People tasks, People records, snapshots, and queue state are stored locally in Chrome extension storage or IndexedDB and are not uploaded to the developer. Chrome may synchronize supported preferences through your Google account according to Google's own Chrome Sync settings and policies.
Temporary page data used for sorting and filtering remains in browser memory. The Extension may cache non-personal selector configuration in Chrome local storage. The minimized event queue and last-send timestamp are also stored locally; events are removed only after Windseed confirms receipt, failed attempts remain for a later natural running opportunity, and the queue is capped at 1,000 records. Exported files and downloaded media remain on your device in the location chosen through Chrome. Removing the Extension or clearing its storage deletes its local data.
Data Sharing
SocialMiner does not sell or share user data with third parties. Media downloads are fetched directly from the supported social-media platform or its content-delivery network at your request. The developer does not receive downloaded media, page data used to create exports, account-library entries, cached posts, collection/People task data, People records, or snapshots. When the Extension opens or requests a page on windseed.app, that website visit is governed by the sections of this Privacy Policy that apply to the WindSeed website.
Permissions
Remote Code
SocialMiner does not download or execute remote code. Remote configuration contains data values such as selectors and operational settings; all executable code is packaged with the Extension.
Children's Privacy
SocialMiner is not directed to children under 13, and the developer does not knowingly collect personal information from children through the Extension.
Contact
If you have questions about the SocialMiner privacy practices described in this section, please contact us at admin[at]windseed.app or create an issue in the SocialMiner GitHub repository.