OpenSourceHub Logo
OpenSourceHub

Plain-language summary

What we access

Signing in with GitHub gives OpenSourceHub read-only access to your profile and email. Nothing more. Here is exactly what that means, what we keep, and how to take it back.

We read

Your public profile and your email address.

We never

Touch your repositories or act on GitHub as you.

You control

Revoke access on GitHub or delete your account anytime.

The GitHub permissions we ask for

read:user

Read your public GitHub profile: username, name, avatar, bio, location, company, website and repository counts.

user:email

Read your email addresses, so we can use your primary verified email for your account.

That's the full list. We don't request repo or any write permission. GitHub shows the same list on its authorization screen before you approve. GitHub's scope reference

What we never do

  • Write to, push to or delete any of your repositories
  • Read the source code of your private repositories
  • Post, comment or open issues on GitHub as you
  • See or store your GitHub password

What we store

  • Your GitHub ID, username, name, avatar, email and profile fields
  • Repository counts and the technologies we infer from repository metadata
  • Your GitHub access token, encrypted on our server (AES-256-GCM)
  • What you do here: saved projects and issues, notes, preferences, follows, messages and battle code

What other people can see

  • Your developer profile (username, name, avatar, bio, technologies) can appear in discovery
  • Buddy notes you choose to make public on an issue
  • Messages and code snippets, to the person you send them to

Your email is never shown on public developer cards.

Honest limits

We'd rather tell you what we don't do yet than let you assume:

  • Messages are not end-to-end encrypted.
  • Your session uses cookies and a token in browser storage, not only HTTP-only cookies.
  • Deleting your account removes your profile and bookmarks, but some records (reports, battle records, backups) may not be erased immediately.
  • An in-app GitHub disconnect button is not available yet; revoke on GitHub instead.
  • OpenSourceHub has no independent security certification.

Take your access back

Revoke GitHub accessGitHub Settings → Applications → Authorized OAuth AppsDownload your dataSettings → Privacy & connections, as a JSON fileDelete your accountSettings → Danger zoneEmail preferencesDigest emails are off unless you turn them on

Revoking on GitHub stops future access but doesn't delete what's already saved here. Signing out is different from revoking.

Who runs OpenSourceHub

OpenSourceHub is built and operated by the miidaystudio team. It is independent of GitHub and not endorsed by it.

miidaystudioagency@gmail.com
Continue to sign in Full privacy policyTerms of service