CrewSelector Privacy Policy
Product: CrewSelector Chrome DevTools Extension
Developer: Husni Tabazah
Contact: husnitabazah@gmail.com
1. What CrewSelector processes
CrewSelector may process website content and DOM structure, sanitized element metadata, selector candidates and runtime match results, form-related element metadata such as labels and placeholders, and Page Locator Audit evidence required to provide its developer-facing selector workflow.
CrewSelector intentionally avoids forwarding live input values, password values, authentication tokens, full DOM content, and secret-like testing attributes into the DevTools panel workflow.
2. Why the data is used
The data is used only to provide CrewSelector's disclosed single purpose: inspect page elements; generate and validate selectors; evaluate locator quality, risk, and stability evidence; support explicit Human Review; provide recommendation-only Healing intelligence; and produce read-only Page Locator Audit results for test automation.
3. Local storage
CrewSelector stores local product state such as theme preference, selector-output settings, Workbench settings, bounded saved selector history, and Human Review state/history on the user's device using local browser storage.
4. Data transmission and sharing
The current release does not transmit inspected page content to CrewSelector-controlled analytics or backend servers. CrewSelector does not sell user data, does not share inspected user data with advertisers or data brokers, and does not use inspected data for personalized advertising, credit decisions, or unrelated profiling.
User-clicked LinkedIn and Gmail contact links open those external services and are subject to the destination service's own privacy practices.
5. Permissions and page access
CrewSelector requests the storage permission for local product state. Its
content script runs on normal HTTP and HTTPS pages so the DevTools workflow can inspect the
page the user is actively analyzing, validate selectors against the live DOM, run stability
checks, re-identify intended elements, and perform the read-only Page Locator Audit.
The current release does not request Chrome permissions for cookies, webRequest interception, scripting injection, file URLs, or Chrome internal pages.
6. Retention and deletion
Local CrewSelector state remains on the user's device until it is replaced, cleared, or removed through normal browser/extension storage lifecycle behavior, including extension removal where applicable. CrewSelector does not retain a server-side copy of inspected page content in the current release.
7. Security
CrewSelector uses a local-first architecture, does not load remote executable scripts or styles, and does not include developer-controlled telemetry in the current release.
8. Limited Use
CrewSelector's use of information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Data accessed by CrewSelector is used only to provide or improve the extension's disclosed single purpose and is not sold or used for personalized advertising.
9. Changes to this policy
If CrewSelector's data practices change, this policy, relevant in-product disclosures, and Chrome Web Store disclosures will be updated before the changed practices are rolled out.
10. Contact
Questions about this policy can be sent to husnitabazah@gmail.com.