slopteacher

Privacy

This is how the product actually runs. It is an operating note, not a document a lawyer reviewed.

Who operates it

Yash Ganar, an individual in India, operates slopteacher.

What is collected

  • An account with an authentication provider: the identity you use to sign in. That provider keeps the session cookies that make sign-in work.
  • Quiz answers you type, with the pass, pending, or slop notes stored beside them.
  • Public repository snapshots. Pasting a public GitHub repo stores a compact copy: a tree summary, a README excerpt, and excerpts of key files. Private repositories are not ingested.
  • Rate-limit keys, so daily caps can be enforced.
  • Model prompts. Snapshot text and your answers are sent so the product can write questions and score them.
  • Product analytics, only after you choose Accept. Decline and the quiz still works.
  • Error reports, so crashes can be diagnosed. Those stay on. They are separate from the analytics choice.

Public repos and badges

Ingest only reads repositories GitHub already exposes as public. A published badge records a completed quiz score for that repo. It is not proof the publisher wrote the code.

How long it stays

Account data stays until you ask for it to be deleted, or until the sign-in account is deleted. Deleting that account removes the matching row in the hosted database. Chats, repository snapshots, and answers attached to the row go with it.

Deletion

Email yashganar91@gmail.com from the address on the account and ask for deletion. Include the repo or session if you only want part of the history removed. Deletion is best-effort, not an instant switch.

Analytics

Analytics does not start until you accept the banner. The choice is stored in this browser. Declining does not turn off sign-in cookies or error reports. Those stay on so you can sign in and so failures can be seen.