← Rithub

Privacy Policy

Version: 2026-11-17 · Last updated: 17 November 2026

Needs legal review, particularly GDPR Art. 13/14 completeness for EU users and the international-transfer section once the hosting region is finalized.

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.

1. Account data

DataPurposeRetention
Username, email address, password hashAccount creation, authentication, login notificationsUntil account deletion
Repository content (code, issues, pull requests, comments)The core product — hosting and serving your codeUntil you delete the repository or account
IP address (per request, server access logs)Security, abuse prevention, debuggingShort rolling window (server log retention — confirm exact figure before publishing, see README)

2. Cookies

Rithub (via Gitea) sets real session cookies when you sign in or interact with the site:

CookiePurposeType
i_like_giteaYour logged-in session — keeps you signed in between page loadsStrictly necessary
_csrfCross-site request forgery protection on forms/API callsStrictly 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).

3. What we don't do

We do not sell your data. We do not scan private repository content for advertising purposes.

4. Sharing

Limited sharing with: hosting/infrastructure providers (needed to run the service), and lawful authorities when legally compelled (court order, applicable law).

5. Your rights

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].

6. Security

Passwords are hashed, never stored in plain text. Report a security issue to [email protected].