Rithub currently runs on Gitea, open-source code-hosting software, with Rithub-specific branding. This policy covers what Gitea's own session mechanism and our account system actually store.
| Data | Purpose | Retention |
|---|---|---|
| Username, email address, password hash | Account creation, authentication, login notifications | Until account deletion |
| Repository content (code, issues, pull requests, comments) | The core product — hosting and serving your code | Until you delete the repository or account |
| IP address (per request, server access logs) | Security, abuse prevention, debugging | Short rolling window (server log retention — confirm exact figure before publishing, see README) |
Rithub (via Gitea) sets real session cookies when you sign in or interact with the site:
| Cookie | Purpose | Type |
|---|---|---|
i_like_gitea | Your logged-in session — keeps you signed in between page loads | Strictly necessary |
_csrf | Cross-site request forgery protection on forms/API calls | Strictly necessary (security) |
Both are strictly necessary for the service to function (you cannot stay logged in without them) — no separate cookie-consent banner is required for these under GDPR/ePrivacy's "strictly necessary" exemption, but they must be disclosed, which this page now does. No advertising or analytics tracking cookies are set by Rithub itself (confirm this remains true if an analytics tag is ever added, and update this page first).
We do not sell your data. We do not scan private repository content for advertising purposes.
Limited sharing with: hosting/infrastructure providers (needed to run the service), and lawful authorities when legally compelled (court order, applicable law).
You can export or delete your repositories and account at any time via account settings. For a data request outside that self-service path, email [email protected].
Passwords are hashed, never stored in plain text. Report a security issue to [email protected].