Acceptable Use Policy
This Acceptable Use Policy explains what is not allowed on NobGit. By using NobGit, you agree not to use the service for harmful, abusive, illegal, deceptive, or disruptive activity.
1. Purpose
NobGit is built for Git hosting, repository management, collaboration, wiki pages, issues, organizations, and related developer workflows. To keep the platform safe, users must not upload, host, share, promote, or support content or activity that harms people, systems, networks, services, NobGit, or the wider internet.
2. Malware and Harmful Code
You may not use NobGit to create, store, distribute, promote, or operate:
- Malware, ransomware, spyware, credential stealers, destructive scripts, botnets, droppers, or loaders.
- Code designed to compromise, damage, exfiltrate from, or disrupt systems without permission.
- Command-and-control infrastructure, payload hosting, phishing kits, or active abuse tooling.
- Instructions or tooling primarily designed to enable unauthorized access or harm.
Security research, educational code, and proof-of-concept material may only be hosted when it is lawful, clearly documented, controlled, non-abusive, and not used to attack, compromise, or harm others.
3. Phishing, Fraud, and Impersonation
You may not use NobGit for phishing, fake login pages, credential collection, social engineering, brand abuse, scams, impersonation, payment fraud, account takeover attempts, or attempts to trick people into sharing passwords, tokens, payment details, personal data, or other sensitive information.
4. Spam and Platform Abuse
You may not use NobGit to send, host, support, automate, or enable spam or platform abuse. This includes unwanted messages, mass account creation, fake activity, abusive automation, link spam, SEO spam, misleading repositories, scraping that harms service performance, or activity designed to manipulate users, search engines, or the platform.
5. Credential Leaks, Secrets, and Stolen Data
You may not knowingly upload, publish, sell, share, or distribute leaked, stolen, exposed, or unauthorized credentials or data. This includes passwords, private keys, API tokens, OAuth tokens, session cookies, access tokens, database dumps, SSH private keys, signing keys, or other secrets that belong to another person, company, service, or system.
If you accidentally upload secrets, you are responsible for removing them, rotating the affected credentials, and limiting further exposure.
6. Copyright, Licenses, and Intellectual Property
You may not upload, store, distribute, or link to content that infringes copyright, trademarks, licenses, trade secrets, or other intellectual property rights.
You are responsible for making sure you have the right to upload, host, publish, fork, clone, license, and share the code, files, assets, documentation, or other material in your repositories.
7. Harassment, Doxing, and Abuse
You may not use NobGit to harass, threaten, stalk, shame, dox, intimidate, target, or abuse another person or group.
You may not publish private personal information without permission, including home addresses, private phone numbers, private email addresses, identification documents, financial details, private images, or sensitive personal data.
8. Illegal Content and Illegal Activity
You may not use NobGit to host, distribute, support, encourage, facilitate, or coordinate illegal content or illegal activity.
This includes fraud, theft, exploitation, unlawful access to systems, illegal marketplaces, threats of violence, terrorist or extremist abuse, non-consensual intimate material, child sexual abuse material, or any activity that violates applicable law.
9. Service Abuse and Unauthorized Access
You may not abuse NobGit infrastructure, services, users, or systems. This includes:
- Denial-of-service activity, traffic flooding, excessive automated requests, or load abuse.
- Storage abuse, bandwidth abuse, resource abuse, or attempts to bypass limits.
- Attacking NobGit systems, repositories, workers, tunnels, mail systems, or providers.
- Attempting to bypass access checks, account restrictions, repository permissions, rate limits, or suspension measures.
- Accessing private repositories, issues, wiki pages, metadata, raw files, Git endpoints, APIs, OAuth, or MCP data without permission.
10. Private Repositories Are Not Exempt
Private repositories must still follow this policy. A repository being private does not allow malware, phishing, stolen data, harassment, illegal content, copyright infringement, service abuse, or harmful activity.
11. Security Research
Security research must follow the Security Policy. Testing must be limited, non-destructive, lawful, and performed only on accounts, repositories, organizations, tokens, keys, and systems you own or are authorized to test.
Do not access, copy, modify, delete, or expose another user's private data. If you accidentally access private data, stop testing and report it immediately.
12. Enforcement
NobGit may remove content, disable repositories, restrict features, revoke credentials, suspend accounts, block access, or terminate accounts that violate this policy or create risk for NobGit, users, infrastructure, providers, or third parties.
NobGit may also take action when content or behavior appears harmful, suspicious, illegal, abusive, or likely to damage the service. NobGit may preserve records where needed for security, abuse handling, legal compliance, or dispute handling.
13. Reporting Abuse
To report abuse, copyright issues, phishing, malware, harassment, leaked credentials, illegal content, or other policy violations, use: https://abuse.nobgit.com .
Abuse email fallback: abuse@nobgit.com . For general support questions, contact: support@nobgit.com .
14. Changes to This Policy
NobGit may update this Acceptable Use Policy from time to time. Updates will be posted on this page with a new version or effective date. Continued use of NobGit after changes means you accept the updated policy.