[ protorip ]
---
site: protos.rip
page: acceptable-use
---
                              __        __    __                      
  ____ ______________  ____  / /_____ _/ /_  / /__     __  __________ 
 / __ `/ ___/ ___/ _ \/ __ \/ __/ __ `/ __ \/ / _ \   / / / / ___/ _ \
/ /_/ / /__/ /__/  __/ /_/ / /_/ /_/ / /_/ / /  __/  / /_/ (__  )  __/
\__,_/\___/\___/\___/ .___/\__/\__,_/_.___/_/\___/   \__,_/____/\___/ 
                   /_/
# Acceptable Use Policy
Last updated: April 26, 2026
This policy explains what is and is not permitted on Protorip. It applies to everyone who uses Protorip, with or without an account. It is part of our [Terms of Service](/terms).
## Intended Use
Protorip is provided as a developer tool designed to be used as part of a software development lifecycle. We provide the protos.rip protobuf registry for publishing and consuming modules via the open source buf CLI, and a website for browsing modules and documentation and managing your account and content.
Normal and fair use looks like:
  • Browsing the Protorip website, dashboard, and module listings.
  • Direct use of the buf CLI with the protos.rip registry.
  • Automated use through the buf CLI and registry APIs in development workflows such as CI pipelines.
Don't use the service in ways outside this purpose, such as:
  • Calling our APIs during your application or service's runtime
  • Using it as a medium for data storage or transfer
  • Re-hosting, proxying, or rebranding Protorip as your own registry
## Prohibited Content
Don't publish, upload, or transmit anything that:
  • Breaks the law. Including copyright, trademarks, patents, export controls, privacy, or anti-discrimination law
  • Infringes someone else's rights. Content that isn't yours to publish
  • Contains malware. Viruses, trojans, ransomware, exploit payloads, or anything else designed to compromise systems — in any form
  • Contains secrets. Credentials, API keys, private keys, passwords — yours or anyone else's
  • Promotes hate or violence. Including extremism, harassment, or incitement
  • Is deceptive. Passing off someone else's work as your own, or misrepresenting the purpose of a module
## Prohibited Conduct
Don't:
  • Circumvent the system. Bypassing rate limits, plan limits, or access controls — including signing up for multiple accounts to get around enforcement
  • Overload the service. Crawling, enumeration, or bulk requests at rates or volumes that disregard rate limits or degrade the service for other users. Automated clients must identify themselves with an honest User-Agent and back off when we return `429 Too Many Requests`
  • Resell the service. Offering Protorip access under your own pricing or branding
  • Harass people. In content, commit messages, or anywhere else on the service
## Names
Don't:
  • Register usernames or organisations you don't plan to use
  • Use names designed to impersonate a person, organisation, or project
  • Use names resembling Protorip's reserved patterns
How we handle name disputes is set out in the [Name Dispute Policy](/disputes).
## Reporting Problems
Abuse. If something violates this policy, email [abuse@protos.rip](mailto:abuse@protos.rip) with a description, where to find the content (module path and commit id), and your contact details.
Copyright. If you believe content here infringes your copyright, send a notice to [abuse@protos.rip](mailto:abuse@protos.rip) with:
  1. Your contact details
  2. The copyrighted work you are claiming has been infringed
  3. Where on Protorip the infringing content is (module path and commit id)
  4. A good-faith statement that the use is not authorised
Trademark. If you believe content here infringes your trademark, send a notice to [disputes@protos.rip](mailto:disputes@protos.rip) with:
  1. Your contact details
  2. The trademark you are claiming, including registration details if applicable
  3. Where on Protorip the infringing content is (module path and commit id)
  4. A description of how the content infringes your rights
We will confirm receipt of any notice and tell you what we did. If content of yours was removed and you believe that is a mistake, reply to the removal notice and we will reconsider.
## What We Do About Violations
Depending on the severity, we may:
  • Warn you
  • Remove or hide the offending content
  • Reclaim user or organisation names held in violation
  • Suspend your API keys or account
  • Terminate the account
  • Refer the matter to law enforcement
## Changes
We may update this policy. For meaningful changes that affect paying customers, we will email you at least 30 days in advance. Smaller changes take effect immediately when published.
## Contacts