Privacy Policy
SlopScore privacy policy for the website and Chrome extension.
SlopScore is designed to score visible LinkedIn posts and timelines, explain why they scored that way, and optionally sync those captures to the SlopScore app. This policy explains what stays local in the browser, what lightweight telemetry reaches SlopScore, what additional data syncs when you enable it, and what becomes public if you intentionally publish a report.
What happens locally
Data the extension keeps on your device
- Extension settings such as whether scoring is enabled, scan preferences, hide thresholds, and muted authors.
- A locally generated extension client identifier and sync-status metadata used to remember whether backend sync is connected.
- Visible LinkedIn content that is processed in the browser to calculate scores before anything is sent anywhere.
Telemetry and sync
Data sent to SlopScore
The extension can run in a local-only mode. Even without sync, SlopScore receives a small amount of installation and setup telemetry so we can understand activation and support issues. If you connect an ingest key and enable sync, SlopScore also sends the minimum capture payload needed to store scores, compare timelines, and create shareable reports.
- Basic extension lifecycle telemetry such as install, startup, and setup events, plus the local extension client identifier, extension version, browser/platform metadata, and sync connection state.
- Visible LinkedIn post, comment, or notification text, author labels, profile URLs, timestamps, and engagement counts when sync is enabled.
- Timeline summaries and history requests needed to render saved feed and profile comparisons in the SlopScore app.
- Public-report payloads if you explicitly create a shareable report from the extension.
Permissions
What the extension is allowed to access and why
SlopScore does not use remote executable code. All JavaScript, HTML, and CSS ship inside the extension package. Network requests only send or receive data for lightweight telemetry, optional sync, and reporting features.
- storage: Used to save extension settings, muted authors, local sync state, and the optional ingest key/API base URL so SlopScore keeps working between sessions.
- tabs: Used to find the active LinkedIn tab, send messages between the side panel and LinkedIn pages, and open LinkedIn or SlopScore pages when you ask.
- sidePanel: Used to show SlopScore controls, live page summaries, and sync settings inside Chrome’s side panel.
- linkedin.com host access: Used only on LinkedIn pages so the content script can read the visible posts, comments, notifications, and profile activity that are currently on screen and calculate scores.
- slopscore.in host access: Used for lightweight install/setup analytics and optional SlopScore API requests such as sync, saved timeline summaries, and public report creation.
Public reports
What becomes public if you publish a report
- If you publish a public report, the selected score, preview image, report title, reasons, and source context become accessible via the public report URL.
- If you do not publish a public report, your synced captures remain account-scoped inside SlopScore.
Retention and requests
Your choices
You can disable the extension, clear local browser storage, or turn off sync at any time. If you want synced captures or a public report removed from SlopScore systems, email hello@danielsinewe.com.
SlopScore is not intended for children, and it is not a forensic authorship tool. It scores the visible sample on screen and stores LinkedIn content captures only when you explicitly enable sync or publish a report.
Last updated: March 13, 2026.