Privacy Policy

You can browse public projects and issues without signing in. Connecting GitHub creates or updates your Hub account and supports saved work, personalized recommendations and community features.

We request read:user and user:email: read access to your GitHub profile and email addresses. We do not request repository write permissions. GitHub handles your password and shows the permissions you grant on its authorization screen.

We store your GitHub ID, username, name, avatar, email and profile fields such as bio, location, company and website when available. We use repository metadata to infer technologies and may store repository counts, including private repository counts if GitHub returns them. This is different from requesting access to private repository source code.

Your GitHub OAuth access token is stored encrypted on our server so account features can call GitHub. Older grants can differ from the permissions currently requested; review your actual authorization in GitHub settings.

We store the projects and issues you save, workflow status, notes, preferences, follows, buddy requests and messages or code snippets you send. These support your workspace and the community actions you choose.

New account preferences have automatic digest emails off. You can choose to receive issue recommendations during setup and change the choice in Settings. Signing in does not require opting into digest emails. Existing accounts keep their saved email preference until it is changed.

We use the email supplied by GitHub for account features and optional emails; onboarding cannot replace it with an arbitrary address. Your email is not a field on public developer cards.

Your developer profile can appear in discovery, including your username, name, avatar, bio, technologies and visible activity. OpenSourceHub membership and follower counts are distinct from GitHub verification or endorsement.

Buddy requests and issue reservations are community features. Your chosen public buddy note and profile can be visible to others interested in the issue. Reserving an issue here does not assign it on GitHub.

Direct messages and code snippets are shared with the conversation participant and stored by the service. Messages are not end-to-end encrypted. Blocking, reporting and moderation are available; avoid sharing information you do not want the service or recipient to receive.

Battle drafts and submitted source code are stored, and submissions are sent to the configured code runner, such as Judge0, for execution and judging. Battle results are available to participants; relevant records can be inspected for moderation.

While the editor is open, we collect editing counters and timings: typed/pasted character counts, paste events, pauses, and window focus changes. These counters do not contain clipboard text, browsing destinations or the text of individual keystrokes. This does not mean your submitted code is never stored: drafts and submissions are separate records.

A stored submission may be reused as a ghost opponent under its contributor's username. A ghost is a replayed submission, not a person currently online. Consider this reuse before submitting. Additional privacy and reuse controls are not currently offered in Settings.

Sign-in uses session cookies and a session token in your browser's local storage. Local storage is accessible to scripts running on the site; the session is not stored exclusively in HTTP-only cookies. Signing out clears the app's local session token and asks the server to clear its cookie.

The service uses hosting, database, cache, email and code-execution infrastructure to operate these features. GitHub provides identity and repository data. Email delivery uses Resend when enabled. Custom avatar uploads are sent to Cloudinary if that upload integration is configured; otherwise the chosen image is saved with the profile. External avatar and image providers receive the requests needed to load their images.

Diagnostics and caches support reliability and troubleshooting. Encryption of stored GitHub tokens does not mean all records are end-to-end encrypted or that the platform has independent security certification. Contact the team for details about the infrastructure used by a particular deployment.

To revoke GitHub access, open GitHub Settings → Applications → Authorized OAuth Apps, select OpenSourceHub, and choose Revoke. This stops future access through that authorization; it does not automatically delete information already stored by OpenSourceHub. Signing out is also different from revoking GitHub access.

You can delete your Hub account from Settings. The app removes the active profile and associated bookmarks; deletion is not a promise that every report, copied battle record, migration archive, cache or backup is immediately erased. The application does not impose one fixed automatic retention period on all records. Contact us about retained information or a deletion request beyond the in-app action.

Profile changes and email preferences are available in Settings. Automated data export and an in-app GitHub disconnect control are not currently available. OpenSourceHub is operated by the miidaystudio team and is independent of GitHub.