Privacy policy

SlopCop receives the repository URL or GitHub repository selection you submit and retrieves repository content to run analysis. Scan records can include repository identity, commit and branch information, file paths, source excerpts, findings, progress events and generated reports. Source and history may contain personal information supplied by repository contributors.

Connecting GitHub provides user and installation identifiers, repository selections and authorization credentials used to check access and retrieve the selected repository. The service stores an encrypted GitHub user authorization credential behind an expiring connection. Repository checkout uses a separate short-lived GitHub App credential created by the service.

Confirming an email address reserves an account with a username, display name and personal workspace. We store your verified email address encrypted, your profile, workspace memberships and invitations, and session records. If you choose a password, we store a salted password hash rather than the password. Workspace members can see one another's usernames and display names.

The check API also receives patches and associated repository/commit information from authenticated clients. Patches can contain unpublished source and binary content. Review what you submit, including repository rules and untracked changes.

Public-repository report links show the public portion of the report while the link remains valid. Additional living-review findings require a verified email session for that scan. Reports can show repository names, file paths and source excerpts. Keep report links private when their contents are sensitive.

Private-repository access is subject to GitHub authorization as well as report access. The associated access-control change is under review with this draft; this page is not a security assurance. Removing access cannot recall copies already downloaded by authorized readers.

AI review is enabled by default. Analysis evidence, including source excerpts, can be sent to configured model services to interpret findings and generate reports. Model providers, their data-use and training terms, their retention, and processing locations must be confirmed before this policy is published.

If you request email access or review notifications, the service processes your email address and records needed to verify the request, deliver messages and associate reports with that address. Contact forms collect the name, email address and message you submit.

When you are signed in, the service requests your profile picture from Gravatar using a SHA-256 hash of your verified email address. Gravatar receives that identifier and the server's request, without your browser session, raw email or browser IP address. If no picture is available, the application shows initials from your display name or username.

Unlocking a living review requires email verification. Separately, you can choose to let SlopCop email you about that review and its services. This choice is optional and starts unchecked; leaving it unchecked does not prevent you from unlocking the review. Sending a verification link does not by itself give permission for promotional follow-up.

If you opt in, we record the disclosure and its version, your choice and when you made it, linked to the verification request. Permission is confirmed only when you verify that request. Use the email preferences link in your review verification email to unsubscribe from optional follow-up emails. Opening the link does not change your choice; use Unsubscribe to confirm. If you unsubscribe by accident, you can explicitly accept the disclosure and resubscribe on the same page. You can also ask us to withdraw permission using Talk to us and specifying the email address concerned. These choices are separate from essential verification and requested report messages, and do not remove your report access.

Operational records support request limits, job execution, troubleshooting and message delivery. Configured operator notifications can include repository labels, revisions, event details and masked email information. Hosting, repository, model, mail and notification providers and their contractual roles remain subject to review.

An expired sign-in session or report link does not by itself delete a scan or report. The application has cleanup rules for temporary execution, access and delivery records, with eligibility rules based on a 30-day cutoff and exceptions for active work and access grants. Owned reports and successful in-depth review results can remain stored beyond that period.

Account details and the verified email needed for sign-in are retained separately from temporary report and delivery records. Signing out or letting a session expire does not delete your account or workspace membership.

The operating retention schedule, backup retention, deletion request process and any contractual exceptions must be verified before publication. This draft does not promise that all data is deleted after 30 days.

Feature cookies support sign-in, request security and access to reports you open. Where opt-in is required, one banner offers Accept all to allow optional theme storage and product analytics, Essential only to decline both, or Customize to choose each separately. Essential only removes the saved theme. You can still switch themes for the current page and use the service.

Change or withdraw either choice anytime using Cookie settings in the footer. Where analytics is enabled, PostHog (US region) measures visits, public-page attribution, explicit demo interactions and product adoption. For requests identified as US traffic by our authenticated Cloudflare connection, analytics may start without a consent popup unless you have declined. All other countries and unknown locations require explicit opt-in. You can opt out using Cookie settings; we also treat Global Privacy Control as an analytics opt-out. Previous theme acceptance and choosing theme storage alone never enable analytics. Declining analytics does not affect sign-in, your current theme or repository checks; Customize lets you keep theme storage while declining analytics.

Analytics uses random identifiers and, after verified sign-in, an opaque account identifier. Your signed-in analytics permission also controls export of hosted product activity, including CLI checks. Explicit consent is recorded separately from a temporary US policy permission. CLI traffic can renew an existing US permission but cannot establish one merely because a CI runner is hosted in the US. Cloudflare country classification is used to apply this policy and is not sent to PostHog. It excludes contact details, repository identities and content, private URLs, arbitrary campaign values, IP addresses and raw errors. Session replay, automatic interaction recording and automatic exception capture are disabled. PostHog’s free plan has a one-year event retention period. Withdrawal clears browser analytics identifiers immediately. Once saved to your account, it also stops future account analytics and cancels pending export. When you sign in on a browser that has no choice saved, a refusal saved to your account is applied there, with theme storage off, instead of asking again. If the account update fails, the controls show an error and retry when you return online or revisit the page. A request already in flight may finish; withdrawal does not automatically delete events previously sent to PostHog. Use Talk to us to request deletion of previously collected analytics.

Use Talk to us to raise a privacy question without including passwords, access tokens or private source. The organization responsible for processing, its official privacy contact, legal bases, applicable rights and complaint route, international transfers and any additional sharing purposes are still to be confirmed. This draft makes no legal compliance or model-training commitment.