Subprocessors & Providers

Version 1.0, effective June 7, 2026

This page lists the main infrastructure providers and service providers NobGit uses to operate the service. These providers may process personal data only as needed to provide hosting, traffic delivery, security, email, abuse handling, backups, or related operational services.

1. Direct Providers Used by NobGit

Provider Role Purpose Data that may be processed Location / Notes
Hetzner Online GmbH Hosting provider / processor Server hosting, virtual machines, storage, databases, repositories, backups, and related infrastructure. Account data, repository data, Git metadata, wiki content, issue content, uploaded files, email server data, operational data, backups, and technical data. NobGit is hosted on an EU-Central Hetzner server. Hetzner backups for the CPX22 Cloud Server are retained for 7 days.
Cloudflare DNS, traffic, security, and edge provider / processor DNS, traffic routing, TLS, Cloudflare Tunnel, security filtering, abuse reporting Worker, static policy pages, and related edge services. IP addresses, request metadata, security events, Cloudflare country metadata, cached or transmitted content where applicable, and abuse report data submitted through abuse.nobgit.com. Cloudflare may process traffic and security metadata before requests reach the NobGit server.
Mailcow Self-hosted mail system Transactional email, verification emails, welcome emails, account deletion emails, support email, abuse email, and security contact email. Email addresses, email content, email delivery metadata, support messages, abuse messages, and security reports. Mailcow is self-hosted by NobGit on Hetzner infrastructure. It is not a separate external provider operated by a third party.
NobGit application and database Self-hosted internal system Main NobGit platform, accounts, repositories, organizations, issues, wiki pages, merge requests, authentication, OAuth, MCP, and platform settings. Account data, password hashes, repository content, Git metadata, wiki content, issues, merge requests, organization data, SSH keys, GPG keys, OAuth/MCP data, and related platform data. Operated by NobGit on Hetzner infrastructure.

2. Cloudflare Abuse Reporting

NobGit uses a separate Cloudflare Worker at https://abuse.nobgit.com for abuse, copyright, illegal content, phishing, malware, and security concern reports.

Reports submitted through this form may include reporter contact details, reported URLs, descriptions, timestamps, user agent data, Cloudflare country metadata, and internal report status information.

Abuse report records may be stored separately from the main NobGit application, including in Cloudflare D1 or related Cloudflare services.

3. Provider Subprocessors

Some providers listed above may use their own subprocessors to deliver their services. NobGit does not directly control those subprocessors, but relies on the providers' data processing agreements, security measures, and published subprocessor information.

NobGit may update this page if a new direct provider is added, if a provider is removed, or if the way NobGit uses a provider materially changes.

4. Services Not Currently Used

NobGit does not currently use third-party advertising providers, marketing pixels, analytics tracking providers, payment processors, customer support platforms, or external AI processing providers for private repository content.

If NobGit adds these types of providers later, this page and the Privacy & Data Handling page will be updated.

5. Contact

For privacy or provider questions, contact: support@nobgit.com

To report abuse, copyright issues, illegal content, phishing, malware, or harmful content, use: https://abuse.nobgit.com

Abuse email fallback: abuse@nobgit.com