octionic

Contact us

StopSlopIn – Privacy Policy

StopSlopIn – Privacy Policy

Last updated: April 18, 2026

This Privacy Policy describes how the StopSlopIn browser extension (“StopSlopIn”, “the extension”, “we”, “us”) handles information when you install and use it. StopSlopIn is a Chrome extension that filters low-quality content on your LinkedIn feed by routing post text to a webhook endpoint that you configure and control.

Please read this policy carefully. By installing or using StopSlopIn you confirm that you have read and understood it.

1. Who is responsible for the extension

StopSlopIn is published and maintained by octionic by Mario Haarmann, reachable at info@octionic.com. For the purposes of data-protection law (including the EU GDPR and the UK GDPR), we act as the data controller for the very limited processing described below. Where you configure a third-party webhook endpoint, the operator of that endpoint — which is typically you or an organisation you choose — acts as the controller for any data sent to it.

2. Summary in plain English

StopSlopIn does not have its own servers, database, analytics pipeline, or telemetry. We never receive any information about you, your browsing, your LinkedIn activity, or the posts you vote on. The extension runs entirely in your browser and only communicates with one server: the webhook URL you type into the settings yourself. If you do not configure a webhook, the extension performs no external network requests at all.

3. What the extension does

On pages under https://www.linkedin.com/feed*, StopSlopIn reads the visible text of each post and its internal post identifier, and sends both to the webhook URL you have configured. Your webhook returns a classification (pass or fail) for each post, and StopSlopIn either fades or collapses posts marked as fail. When you click the Good or Slop buttons rendered next to a post, your rating, the post identifier, and the post text are sent to the same webhook so that you can record feedback, build training data, or refine your own classifier.

4. Information we process

4.1 Data read from LinkedIn pages

While you are viewing your LinkedIn feed, the extension reads:

  • The text content of posts visible in your feed.
  • The internal identifier of each post (used solely to match classification results back to the right post).

This data is read only in your browser. It is never sent to us and is never stored by the extension beyond the brief moment needed to send it to your webhook.

4.2 Data you enter into the extension

You provide the following settings, which are stored locally in Chrome’s sync storage on your device and profile:

  • The webhook URL you choose.
  • Your display preference (dimmed vs. collapsed).
  • Local counters such as the number of posts scanned and the number hidden.

We never read, receive, or have any way to access this local storage.

4.3 Data we collect

None. StopSlopIn transmits nothing to its developer and has no backend infrastructure. We have no account system, no login, no user identifier, no analytics, no crash reporting, and no tracking pixels.

5. Data sent to your configured webhook

When a webhook URL is configured, the extension sends HTTP POST requests exclusively to that URL:

  • Classification requests containing the text and identifier of posts in your feed, sent to yourwebhook/?action=analyze.
  • Vote events containing your rating (good or slop), the post identifier, and the post text, sent to yourwebhook/?action=vote.

Because you choose the webhook, you alone determine where this data travels, how it is processed, how long it is retained, and whether it is shared. If the webhook is operated by a third party (for example an n8n cloud workspace, a serverless function, or an LLM provider called by your server), that third party’s privacy policy governs what happens to the data after it leaves your browser. You should make sure you are comfortable with, and legally permitted to use, the endpoint you configure.

6. Categories of data we do not handle

StopSlopIn does not collect, process, or transmit any of the following:

  • Personally identifiable information such as names, email addresses, phone numbers, or postal addresses.
  • Authentication data, passwords, cookies, or session tokens.
  • Financial or payment information.
  • Health or medical information.
  • Precise or approximate location data.
  • Browsing history outside of linkedin.com/feed.
  • Messages, direct communications, or private LinkedIn content that is not part of the public feed.
  • Biometric or facial data.

7. Permissions the extension requests and why

  • storage — to save your webhook URL, your display preference, and local counters in Chrome’s sync storage. No personal data is stored.
  • Host permission for https://www.linkedin.com/* — so the content script can read post text and render Good/Slop controls on the LinkedIn feed. This is the core functionality of the extension.
  • Optional host permission for the webhook domain — requested at runtime, only when you save a webhook URL, and only for the specific origin you entered. You can deny or revoke this permission at any time in Chrome’s extension settings, in which case the extension will simply stop sending requests until you grant it again.

StopSlopIn does not request activeTab, tabs, history, cookies, identity, webRequest, or any broad URL pattern such as <all_urls>.

8. Remote code and third parties

The extension does not download, evaluate, or execute any remote code, stylesheets, or scripts. All logic ships inside the extension package reviewed by the Chrome Web Store. It contains no advertising SDKs, no analytics SDKs, no tag managers, and no third-party tracking libraries.

9. Your choices and controls

You can at any time:

  • Clear the webhook URL in the settings to stop all external network activity.
  • Revoke the webhook host permission from chrome://extensions to block network access without removing the extension.
  • Uninstall the extension, which immediately removes all locally stored settings from your device.
  • Disable syncing of Chrome storage in your Chrome profile settings if you prefer settings to remain on a single device.

Because we do not collect or hold any data about you, requests for access, correction, deletion, portability, or restriction of processing are fulfilled entirely by the actions above. Any such requests regarding data held by your webhook must be directed to the operator of that endpoint.

10. Legal bases for processing (EEA and UK users)

To the limited extent that reading post text and relaying it to your chosen webhook constitutes processing of personal data under EU or UK law, we rely on your consent, given by installing the extension and configuring a webhook URL (Article 6(1)(a) GDPR), and on our legitimate interest in providing the feature you have requested (Article 6(1)(f) GDPR). You can withdraw consent at any time by removing the webhook or uninstalling the extension.

11. California residents (CCPA/CPRA)

We do not sell or share personal information as those terms are defined under the California Consumer Privacy Act. We do not collect personal information from California residents through the extension. Because we hold no personal information, there is nothing for us to disclose, correct, or delete in response to a consumer rights request; the controls in Section 9 give you full control over the data flow.

12. Children

StopSlopIn is intended for adult professional users of LinkedIn and is not directed to children under the age of 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect information from children.

13. International transfers

Because we do not receive any data, no international transfers take place on our side. Any transfers that occur when your browser sends data to your configured webhook are between you and the webhook operator.

14. Security

The extension communicates with your webhook over whatever transport you configure; we strongly recommend using an HTTPS URL so the request is encrypted in transit. Local settings are stored using Chrome’s built-in sync storage, which is protected by your Google account’s security controls.

15. Changes to this policy

We may update this Privacy Policy from time to time to reflect changes to the extension’s functionality or to clarify our practices. The “Last updated” date at the top of this page indicates when the policy was last revised. Material changes will be highlighted in the extension’s release notes on the Chrome Web Store.

16. Contact

Questions, concerns, or privacy requests can be sent to info@octionic.com.

StopSlopIn is an independent project and is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation or Microsoft Corporation.