Omahub

Privacy Policy

Last updated: August 17, 2026

1. Controller

Nick Friedrich
Butterbauernstieg 4
22339 Hamburg
Germany
Email: feedback@nick-friedrich.de

2. Hosting and server logs

When you visit Omahub, the web server may process technical information required to deliver and secure the site. This may include your IP address, date and time of access, requested page, referrer, browser, operating system, and response status. Processing is necessary for the site’s reliable and secure operation and is based on Art. 6(1)(f) GDPR. Log data is retained only as long as needed for security, troubleshooting, and abuse prevention, unless a longer period is legally required.

3. GitHub sign-in

If you choose “Sign in with GitHub,” you are redirected to GitHub for authentication. GitHub then provides Omahub with your GitHub account ID, username, display name, email address (if available), profile URL, and avatar URL. Omahub stores this information to create and maintain your account, display your account, attribute actions, prevent abuse, and manage administrator access.

The legal basis is Art. 6(1)(b) GDPR where authentication is needed to provide requested account features, and Art. 6(1)(f) GDPR for platform security and abuse prevention. GitHub processes data under its own privacy statement.

4. Plugin submissions

When you submit a plugin, Omahub stores the GitHub repository URL, submission and review timestamps, status, and—where applicable—technical failure or review information. Published plugin data may include information imported from the repository and is visible publicly. This processing is necessary to handle your submission and provide the registry (Art. 6(1)(b) GDPR) and to maintain the quality and security of the service (Art. 6(1)(f) GDPR).

5. Cookies and sessions

Omahub uses technically necessary cookies for session management, sign-in, security, and protection against cross-site request forgery. These cookies are not used for advertising or cross-site tracking. They are necessary to provide the service and are stored or accessed in accordance with § 25(2) no. 2 TDDDG; related personal-data processing is based on Art. 6(1)(b) or (f) GDPR.

6. External content

Profile images are loaded from the avatar URL supplied by GitHub when a signed-in user is shown. Your IP address and browser information may therefore be transmitted to the host serving that image, which may be GitHub or a GitHub content-delivery service. Plugin pages also contain links to third-party websites, but Omahub does not control their data processing.

7. Recipients and international transfers

Personal data may be processed by service providers used to host and operate Omahub and by GitHub when you use GitHub sign-in or GitHub-hosted content. Some providers may process data outside the European Economic Area. Where required, such transfers are protected by an adequacy decision or appropriate safeguards such as the European Commission’s standard contractual clauses.

8. Retention

Account data is kept while your Omahub account exists and then deleted unless retention is required by law or necessary to establish, exercise, or defend legal claims. Submission records are kept for as long as needed to operate and document the registry and prevent duplicate or abusive submissions. You may request deletion using the contact details above.

9. Your rights

Subject to the applicable legal requirements, you have the right to access, rectify, erase, or restrict the processing of your personal data, to receive data you provided in a portable format, and to object to processing based on legitimate interests. Where processing is based on consent, you may withdraw it at any time with effect for the future.

You also have the right to lodge a complaint with a data protection supervisory authority. The authority responsible for Hamburg is the Hamburg Commissioner for Data Protection and Freedom of Information.

10. No advertising analytics

Omahub does not currently use advertising cookies or third-party analytics. If this changes, this policy and any required consent mechanism will be updated before such technologies are used.

11. Changes to this policy

This policy may be updated when the service, its providers, or legal requirements change. The current version is always available on this page.