Extracted page rows stay in your browser.

1. Single purpose

The extension's single purpose is to extract visible tables and repeated lists from the webpage the user explicitly invokes it on, clean the extracted fields and let the user copy or export the resulting spreadsheet data. The optional Pro workflow can save local extraction settings for repeat pages.

2. What the extension reads

After the user invokes the extension, it inspects the active page's rendered DOM as necessary to identify tables or repeated structures. This can include visible text, table cells, link destinations, image URLs and DOM structure needed to create the requested dataset.

3. What is not sent to Solarc Labs

The inspected page, extracted rows and export files are not sent to the Solarc Whop gateway or a third-party scraping service. Extraction, cleaning and CSV/XLSX generation run locally in the browser. Saved Recipes store workflow configuration, not the captured dataset.

4. Optional Pro authentication and access checks

If a user chooses Sign in with Whop, Chrome asks for the optional identity permission and the exact Whop/Solarc gateway HTTPS origins needed for that Pro flow. The Free extractor does not require those permissions. Chrome's identity API then opens Whop OAuth login. Whop can return an OAuth access token and refresh token to the extension.

The extension stores the Whop session/access state in browser extension local storage until sign-out or session expiry. The token is sent over HTTPS to Whop and is presented to the Solarc Whop gateway only for authentication/access and billing-management requests. The Solarc gateway verifies the authenticated Whop user and asks Whop whether that user has access to the configured Pro resource. Server-side Whop API and webhook secrets are never packaged into the extension.

5. Local storage and Saved Recipes

Chrome v0.2 uses the storage permission for local Whop session/access state and recipe configuration. A recipe can contain a user-provided name, site origin/path pattern, detected-candidate fingerprint, hidden-column preferences, export format and schema/timestamps. It must not contain extracted row data, page credentials, cookies or arbitrary executable JavaScript.

Candidate/preview rows remain in memory for the current interaction. CSV and XLSX exports are created locally only when the user chooses an export action.

6. Permissions and network hosts

• activeTab: temporary access to the current page after the user invokes the extension.
• scripting: injects the packaged local extraction script into that user-invoked active tab.
• sidePanel: displays the extraction, preview, export and optional Pro controls on Chrome.
• storage: stores local recipe configuration and Whop session/access state on the Chrome build.
• identity (optional): requested only when the user starts Whop Pro sign-in.
• https://api.whop.com/* (optional host): requested for Whop OAuth/account communication only when Pro sign-in is enabled.
• The exact production Solarc Whop gateway HTTPS origin (optional host): requested for server-side entitlement and billing-management checks only when Pro sign-in is enabled.

The Chrome v0.2 design does not request <all_urls>, cookies, webRequest, downloads or persistent arbitrary-site host access. Other browser packages remain Free-only until their account/payment path is separately verified.

7. Chrome Web Store Limited Use

The use of information received from Chrome extension APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data obtained for the extension's single purpose is not sold, transferred for personalized advertising, used for credit decisions, or made available for unrelated human review.

8. Third-party processor: Whop

Whop is used for optional Pro identity, checkout, subscription/billing and access verification. Information you provide directly to Whop is handled under Whop's own privacy terms. Solarc Labs does not use the extension to sell extracted page data, use it for advertising or credit decisions, or transfer the extracted dataset for unrelated purposes.

9. Remote code

The extension does not execute remotely hosted JavaScript or WebAssembly. Its extraction, cleaning, Saved Recipe and XLSX generation code is packaged with the extension. The HTTPS Whop/gateway calls exchange authentication/access/billing data, not executable extension code.

10. Website visits

This extension-specific notice describes the browser extension. If you separately visit solarclabs.com, the general Solarc Labs Privacy Notice applies to that website visit.

11. Contact

Privacy or support questions can be sent to enoch@solarclabs.com. The data controller for the Solarc Labs website is SOLARC GOODS LIMITED.

12. Changes

This notice must be reviewed before the extension adds materially different page-data handling, cloud sync, broader website access, new third-party processors or materially different account/storage behavior.