Creator Signal Chrome Extension Privacy Policy
Creator Signal processes user-selected webpage content locally. Stripe handles subscription checkout. A separate activation service verifies completed subscriptions and issues signed access codes. The extension does not continuously monitor browsing and does not receive card details.
1. Scope
This privacy policy applies specifically to the Creator Signal — Make, Save or Skip Chrome extension. It is not a general company homepage or a policy for an unrelated product.
2. Information the extension handles
After the user explicitly clicks the capture control, Creator Signal may read the active page title, URL, and text the user selected. Users may also paste content manually. The extension creates local Signal Breakdown, Originality Ledger, hook, execution-plan, and Make/Save/Skip records.
| Data category | Handled? | How it is used |
|---|---|---|
| Website content | Yes, only after user action | Selected text or manually pasted content is analyzed locally to identify creative patterns. |
| Web history | Yes, if the user saves it | The active page title and URL may be stored with a saved Make, Save, or Skip record. |
| Authentication information | Yes | A signed product access code is stored locally to verify subscription access. |
| Financial and payment information | No inside the extension | Stripe processes checkout. The extension does not receive card or bank details. |
| User activity / analytics | No | No advertising trackers, behavioral analytics, or continuous browsing monitoring are included. |
3. Local storage and retention
Saved records, analysis results, preferences, and the signed access code are stored with chrome.storage.local on the user's device.
Users can remove locally stored records through the extension's delete or clear controls. Removing the extension also removes extension-managed local storage according to Chrome's behavior.
4. Subscription checkout and activation
Subscription checkout is hosted by Stripe. Stripe may collect the buyer's email address, billing information, and payment details under Stripe's own privacy terms. The extension does not receive or store full card numbers, bank-account credentials, wallet private keys, or seed phrases.
After successful checkout, Stripe redirects the buyer to a separate activation page with a Checkout Session identifier. The activation service uses that identifier to verify the completed subscription with Stripe and issue a signed access code for the correct product and plan. The extension stores the signed access code locally to verify access.
5. Data sharing
We do not sell user data. We do not use captured webpage or checkout content for advertising, profiling, creditworthiness, lending, or unrelated purposes. Stripe receives checkout information necessary to process subscriptions. The activation service communicates with Stripe only to verify subscription status and issue access.
6. Chrome permissions
activeTab provides temporary access to the active page after user action. scripting runs the packaged capture function after user action. storage saves the local library, preferences, and signed access code.
7. Security
The extension is designed to minimize data handling. User-selected content is processed locally unless this policy explicitly states otherwise. Secret payment credentials should never be pasted into the extension.
8. Children
This extension is not directed to children under 13, and we do not knowingly collect personal information from children under 13.
9. Changes to this policy
If the extension's data practices materially change, this page will be updated before or when the changed version is distributed.
10. Contact
Privacy and support contact: lorensaisolutions@gmail.com