Terms of Service

1. Accepting these terms

By downloading, installing or playing Breach Protocol, or by using breachprotocol.info, you agree to these terms. If you do not agree, do not use them.

If you are under the age of majority where you live, you need permission from a parent or guardian.

2. What the alpha is

Breach Protocol is unfinished software distributed free of charge for testing. In practice that means:

• It may crash, corrupt saved data, or behave incorrectly.
• Features may be added, changed or removed without notice.
• Progression, unlocks and any in-game currency may be reset at any time. Nothing you earn in the alpha is guaranteed to survive to a later build.
• Access may be suspended or ended at any time, including ending the alpha entirely.

Nothing in the alpha is sold. There is no store, no purchasable currency and no paid access. Anyone offering to sell you access, keys, accounts or items is not connected to this project.

3. How you are expected to behave

Do not:

• Cheat, or use software that modifies the game to gain an advantage — aim assistance, wall visibility, speed modification, or anything else of the kind.
• Exploit a bug deliberately and repeatedly instead of reporting it.
• Grief your own team: deliberate team-killing, blocking teammates, or sabotaging the objective.
• Harass, threaten, or abuse other players, in text, voice, or through names and cosmetics.
• Use hateful, sexual, or illegal content in any name, emblem, calling card or message.
• Attempt to disrupt other players' connections, or to attack the services the game uses.
• Share another player's personal information without their consent.
• Attempt to obtain, guess or reuse another player's identifiers or credentials.

Breach Protocol has an automatic answer to some of this — when friendly fire is enabled, a player who crosses the grief threshold begins taking their own fire back. That is a game rule, not a substitute for these terms.

4. Suspensions and bans

Accounts that break section 3 may be restricted, suspended, or permanently banned. Severity depends on what happened and whether it kept happening.

You may appeal any enforcement action. Appeals are read by a person, and an enforcement that turns out to be wrong is reversed. What to send, and where, is set out on the support page.

Creating a new account to evade an enforcement action is itself a violation, and it is the one thing most likely to turn a temporary restriction into a permanent one.

5. Things you make in the game

Names, emblems, calling cards and other content you create in Breach Protocol remain yours. By creating them in the game you allow the project to display them to other players, which is the entire point of them existing.

Content that breaks section 3 may be removed or reset without notice.

6. The game itself

Breach Protocol — its name, its logo, its maps, its characters, its art, its audio, its code and its written material — belongs to the project. You may:

• Record, stream and publish footage of the game, including monetised video.
• Use screenshots from this site in coverage of the game, with attribution.

You may not redistribute the game's builds or assets, sell them, present the game as your own work, or use its name or logo in a way that implies endorsement or partnership.

7. How matches are hosted

Matches are peer-to-peer: one player in the lobby hosts and the others connect to them directly. There is no dedicated game server between you.

This has a consequence you should understand before you play, and it is set out in full in the privacy notes: a direct connection works by each end knowing where the other end is. Playing an online match therefore involves your network address being visible to the other machines in that match. This is a property of how the matches are hosted, not a setting that can be switched off, and eliminating it requires relayed matches — which are on the roadmap and not in the current build.

8. What the game stores, and what leaves your machine

The full account is in the privacy notes. The substance is here as well, because a player reading these terms inside the game cannot click a link.

Your profile — your Agent ID, operator name, level, progression, unlocks and settings — is stored on your own machine. There is no central account service holding it.

Information leaves your machine in four situations, and only these:

• Matchmaking. To find and join matches the game contacts a matchmaking service and exchanges what is needed to open a connection to other players, which necessarily includes network address information.
• In-match traffic. Once a match starts your game talks directly to the other players in it: position, actions, your operator name, and voice if you use it.
• Reports you choose to send. The in-game report tool sends what you typed together with technical details about the build and the match it was sent from.
• Account backup, if you turn it on. Your save can be uploaded so you can restore it later. It is encrypted on your machine before it is sent, and it is restored only to someone holding your account's signing key.

Your Agent ID is a credential, not just a name. Treat it like a password: do not post it, and do not send it to anyone who asks for it. Nobody working on Breach Protocol will ever ask you for it. The key that proves the account is yours is kept in a file on your machine and is never sent anywhere — which also means that if you lose that file, we cannot prove the account is yours, and we cannot give it back to you.

You can ask for your data to be removed. The in-game report tool and the routes on the support page both reach a person.

Breach Protocol is not directed at children, and the age statement in section 1 applies.

9. No warranty

The alpha and this website are provided "as is", without warranty of any kind. To the fullest extent permitted by law, the project is not liable for lost data, lost progression, hardware problems, or any indirect or consequential loss arising from using them.

10. Changes to these terms

These terms may change as the game does. Material changes will be noted in the update notes, and the date at the top of this page will change. Continuing to play after a change means accepting it.

11. Contact

Support questions, appeals and reports go through the routes on the support page. The in-game report tool (X in the menu) reaches the developers directly.

Breach Protocol is an independent project operated by a sole individual developer, publishing as ImBadDecisions, in the State of New York, United States. It is not a registered company, and no legal entity has been incorporated for it.

Legal notices may be sent to Breach Protocol, New York, New York, United States.

These terms, and any dispute arising out of them or out of your use of Breach Protocol, are governed by the laws of the United States and of the State of New York, without regard to conflict-of-laws rules. Courts located in New York, New York have jurisdiction.

Still to be completed: a qualified legal review, and a registered entity if this project ever takes payments or collects data through this site. Breach Protocol is currently run by one person under a handle, which section 11 states plainly rather than implying a company that does not exist.