Terms of Service

Version: 1.1

Effective date: June 7, 2026

Last updated: June 7, 2026

These Terms of Service explain the rules for using NobGit. By creating an account, accessing NobGit, using Git over NobGit, using the web interface, or using any NobGit service or feature, you agree to follow these terms.

If you do not agree to these terms, you should not use NobGit.

1. About NobGit

NobGit is a Git hosting and code storage platform. It allows users to create, store, manage, and share Git repositories.

NobGit may include repository hosting, Git push and pull access, SSH access, account profiles, organizations, teams, repository settings, issues, comments, wikis, merge requests, fork requests, stars, follows, GPG key verification, SSH key management, access tokens, passkeys, OAuth-related features, MCP-related features, and other developer tools.

NobGit is not a storage vault, archival service, compliance archive, password manager, secrets manager, or guaranteed backup service. Users should keep their own copies of important data.

2. Beta Status

NobGit is currently provided as a beta service. This means the platform is still under active development.

Features may change, break, be removed, be rebuilt, be renamed, or become temporarily unavailable without prior notice.

During beta, NobGit may experience bugs, failed deployments, incomplete features, broken pages, performance problems, data sync issues, Git access issues, authentication problems, missing features, or unexpected behavior.

Repository pages, issues, wikis, account settings, organizations, teams, SSH access, GPG verification, passkeys, APIs, OAuth features, MCP features, email flows, and other platform features may change as NobGit develops.

By using NobGit during beta, you understand that the service may not be suitable for critical production workloads, regulated workloads, legal archives, sole-source backups, or systems where downtime or data loss would cause serious damage.

3. Account Rules

You are responsible for your NobGit account and anything done through it. You must keep your login details and account security methods safe.

Account security methods may include your password, email account, SSH keys, GPG keys, passkeys, OTP authenticator, access tokens, OAuth authorizations, MCP authorizations, recovery methods, and any connected provider accounts.

You agree not to:

• Create accounts using false, misleading, stolen, or unauthorized information.
• Create accounts for another person without permission.
• Use NobGit to impersonate another person, company, project, service, or organization.
• Use names, usernames, repository names, or organization names in a misleading or abusive way.
• Sell, rent, lease, transfer, or share accounts in a way that creates security risk or confusion about ownership.
• Use another user's account without permission.
• Attempt to access accounts, repositories, organizations, systems, or data that you do not own or have permission to access.
• Bypass account restrictions, suspensions, security controls, repository permissions, rate limits, or access checks.
• Use automated traffic, scraping, bots, scripts, or mass requests in a way that harms or overloads NobGit.
• Use NobGit for malware, phishing, spam, credential leaks, copyright infringement, harassment, illegal content, or service abuse.

You must keep your account information reasonably accurate. If your email address no longer works, you may lose access to account recovery, security notices, and support.

4. Age Requirement

You must be at least 13 years old to use NobGit.

If you are under the legal age of majority in your country, you may only use NobGit with permission from a parent or legal guardian.

NobGit may restrict or delete accounts if NobGit believes an account violates the age requirement or was created without required permission.

5. User Responsibility

You are responsible for all content you upload, push, publish, store, create, import, mirror, or share through NobGit.

User content includes source code, Git objects, Git history, commit messages, branch names, tag names, repository names, repository descriptions, organization names, team names, wiki content, issues, issue comments, merge requests, review comments, uploaded files, profile information, avatars, keys, tokens, documentation, releases, and any other material connected to your account.

You must make sure you have the legal right to store, upload, publish, license, copy, distribute, and share any content you place on NobGit.

You must not upload or publish content that violates copyright, license terms, privacy rights, security laws, contractual duties, confidentiality duties, trade secrets, or the rights of another person, project, company, or organization.

You are responsible for reviewing repositories before making them public. Public repositories may be viewed, cloned, copied, indexed, archived, mirrored, downloaded, forked, or shared by others.

NobGit cannot guarantee that public content can be fully removed from third-party systems after it has been made public.

6. Secrets and Sensitive Data

You should not store secrets in NobGit repositories unless you fully understand the risk and have your own security process.

Secrets include passwords, private keys, API keys, access tokens, session cookies, database credentials, webhook secrets, encryption keys, cloud provider credentials, personal identity documents, or other sensitive credentials.

If you accidentally upload secrets, you are responsible for removing them, rotating the affected credentials, invalidating exposed tokens, reviewing access logs where available, and limiting further exposure.

Deleting a commit or repository from NobGit may not immediately remove the exposed data from clones, forks, caches, public archives, logs, backups, search indexes, or third-party systems.

7. Public and Private Repositories

Public repositories may be visible to anyone. Public repository content may be cloned or copied by any visitor.

Private repositories are intended to be visible only to authorized users, teams, organizations, and the system components needed to operate NobGit.

Private repositories must still follow these terms and the Acceptable Use Policy. A repository being private does not allow malware, phishing, stolen data, harassment, illegal content, copyright infringement, or service abuse.

Repository permissions are a technical access-control feature. You are responsible for choosing the right visibility, teams, collaborators, organization roles, and access levels.

8. Backups and Data Safety

NobGit uses Hetzner CPX22 Cloud Server backups. These backups are created daily and are retained for exactly 7 days.

Backups are intended for disaster recovery and service restoration. They are not a user-controlled restore feature.

NobGit does not guarantee that any specific repository, Git object, issue, wiki page, merge request, comment, account setting, uploaded file, avatar, organization, team, key, token record, or other piece of data can always be restored.

Deleted or changed data may remain inside backups until the relevant backup expires and is removed through the 7-day backup rotation.

Users should keep their own local Git copies and independent backups of important repositories.

If you rely on NobGit as your only copy, you accept the risk of data loss.

NobGit is not responsible for loss of data caused by user error, software bugs, failed deployments, hosting failures, account compromise, misuse, abuse, suspension, deletion, maintenance, provider outages, network issues, security incidents, or events outside NobGit's control.

9. Suspension, Restriction, and Termination

NobGit may suspend, restrict, disable, or terminate accounts, organizations, repositories, Git access, SSH access, web access, API access, token access, OAuth access, MCP access, or other features if NobGit believes there has been abuse, a security risk, illegal activity, policy violation, harmful behavior, or misuse of the platform.

NobGit may also limit or block access to protect the service, other users, infrastructure, providers, or third parties.

If your account is suspended or restricted, you may lose access to repositories, organizations, Git push and pull access, SSH access, issues, wikis, account settings, uploaded files, keys, tokens, authorizations, and other NobGit features.

NobGit may remove or disable content that violates these terms, the Acceptable Use Policy, copyright rules, abuse rules, security requirements, or applicable law.

NobGit may preserve certain records after suspension or termination where needed for security, abuse handling, legal compliance, dispute handling, fraud prevention, or backup integrity.

10. Service Availability

NobGit is provided as available. NobGit does not guarantee that the service will always be online, fast, secure, error-free, compatible with every Git client, compatible with every browser, or available in every location.

Maintenance, upgrades, hosting issues, network problems, Cloudflare issues, Hetzner issues, DNS issues, Cloudflare Tunnel issues, attacks, provider outages, software bugs, configuration errors, database issues, disk issues, or security incidents may cause interruptions.

NobGit may change infrastructure, providers, routing, domains, server locations, deployment methods, storage methods, or security systems as needed to operate or improve the service.

11. Your Content and NobGit's Permission to Operate the Service

You keep ownership of content that you upload to NobGit.

You give NobGit permission to store, process, display, transfer, index, clone, pull, push, serve, cache, back up, scan for abuse, and otherwise handle your content as needed to operate the platform.

This permission exists so NobGit can provide Git hosting, repository pages, issue tracking, wiki features, organization features, team features, repository permissions, authentication, notifications, backups, abuse handling, security features, and support.

NobGit does not claim ownership of your code merely because you store it on NobGit.

12. Prohibited Content and Use

You may not use NobGit to store, distribute, support, promote, or enable malware, phishing kits, credential theft, stolen credentials, exploit kits, spam systems, botnets, ransomware, spyware, destructive tools, illegal content, harassment campaigns, or material intended to harm people, systems, services, or networks.

You may not use NobGit for spam, mass account creation, fake activity, repository spam, link spam, SEO spam, misleading projects, fake stars, fake follows, or abusive automation.

You may not use NobGit to publish private personal information without permission, including home addresses, private phone numbers, private email addresses, identity documents, financial details, private credentials, or sensitive personal data.

Security research tools, proof-of-concept code, and dual-use software may be allowed only when used responsibly, clearly documented, lawful, and not used to attack, abuse, compromise, or harm others.

More detailed rules are provided in the NobGit Acceptable Use Policy.

13. Security Testing

Security testing must follow the NobGit Security Policy. You may test only accounts, repositories, organizations, keys, tokens, and data that you own or have clear permission to test.

Denial-of-service testing, load testing, phishing, social engineering, malware uploads, accessing other users' private data, destructive testing, physical attacks, provider attacks, and public disclosure before responsible reporting are not allowed.

If you accidentally access data that does not belong to you, stop testing and report the issue immediately.

14. Third-Party Providers

NobGit uses third-party providers to operate the service.

NobGit is hosted on an EU-Central Hetzner CPX22 Cloud Server. Public traffic is handled through Cloudflare and Cloudflare Tunnel before reaching the Hetzner server.

Provider outages, routing issues, policy changes, security systems, technical problems, support limitations, or infrastructure failures may affect NobGit availability, speed, routing, or reliability.

NobGit may add, remove, or change providers as needed to operate, secure, or improve the service.

15. Email and Notifications

NobGit may send transactional emails related to account verification, password resets, security events, authentication, repository activity, issue activity, organization activity, access changes, abuse reports, policy notices, and service operation.

NobGit may not always send every possible notification. Email delivery may fail because of provider issues, spam filtering, invalid addresses, DNS problems, rate limits, or configuration errors.

16. No Warranty

NobGit is provided without warranties. To the maximum extent allowed by law, NobGit does not promise that the service will meet your needs, remain available, remain secure, preserve all data, work with every tool, or operate without errors.

You use NobGit at your own risk, especially during beta.

17. Limitation of Liability

To the maximum extent allowed by law, NobGit is not responsible for indirect, incidental, special, consequential, punitive, or exemplary damages.

This includes loss of code, loss of repositories, loss of data, lost profits, business interruption, security incidents, account compromise, service downtime, provider outages, or loss caused by relying on NobGit as your only backup.

18. Changes to These Terms

NobGit may update these Terms of Service from time to time. When changes are made, the updated version will be posted on this page with a new version number, effective date, or last updated date.

Continued use of NobGit after changes means you accept the updated terms.

19. Contact

For support, account questions, or service issues, contact: support@nobgit.com

For security vulnerabilities, contact: security@nobgit.com

For abuse, copyright, phishing, malware, illegal content, credential leaks, harassment, or policy reports, use: https://abuse.nobgit.com or email abuse@nobgit.com .