> For the complete documentation index, see [llms.txt](https://docs.battlefrens.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.battlefrens.fun/terms-and-conditions.md).

# Terms and conditions

## Disclaimer

Battlefrens is a project in **Beta**, under continuous development and subject to frequent updates, improvements, and changes. By accessing, using, or participating in Battlefrens, each player acknowledges and expressly agrees to the following:

### 1. Beta Version

* Battlefrens is currently in a testing and development phase.
* The game may contain bugs, technical failures, interruptions, security vulnerabilities, or unexpected behavior.

### 2. No Liability for Errors or Failures

* The developers and operators of Battlefrens do not guarantee uninterrupted, secure, or error-free operation of the platform.
* We are not responsible for losses, damages, service interruptions, transaction errors, minting issues, duel malfunctions, or any other technical incident.

### 3. Security and Inherent Risks

* Players understand that participation involves the use of blockchain technology and smart contracts, which may be exposed to risks including, but not limited to: attacks, hacks, exploits, bugs, and vulnerabilities.
* Marketplace trades in Battlefrens are powered by **Metaplex smart contracts**, which are widely used and battle-tested. However, the risk of hacks or exploits is not entirely eliminated.
* Players are solely responsible for the security of their wallets, private keys, NFTs, and tokens.

### 4. Gameplay, Transactions, and In-Game Economy

* Interactions within Battlefrens (including **duels** and NFT minting) are voluntary activities carried out entirely at the player’s own risk.
* The developers of Battlefrens are not responsible for any financial losses resulting from participation in the game or from the use of digital assets.
* **Any game element, including NFTs, stats, abilities, rewards, or mechanics, may be freely modified at any time to balance the economy or combat systems.**
* Battlefrens does **not** have its own token. Beware of scams claiming otherwise.
* **GOLDIES** are an in-game currency shown in players’ inventories as an internal annotation. GOLDIES are **not transferable** and should not be confused with a blockchain token.

### 5. Compliance with Local Laws

* If your country prohibits or restricts blockchain, cryptocurrency, or related activities, you are solely responsible for ensuring compliance with your local laws and regulations.
* The developers of Battlefrens disclaim any liability arising from a player’s violation of their local regulations.

### 6. Privacy and Data Use

* Battlefrens does **not** collect or store personal data of any kind.
* The only information handled by the game is:
  * The **public wallet address** of the player (public information by design).
  * The **Telegram ID** of users who connect through Telegram (also public and visible).
* This data is only used for matchmaking, in-game functionalities, and account linkage.

### 7. No Warranties

* Battlefrens is provided “as is” and “as available.”
* No warranties, express or implied, are given regarding functionality, economic value, merchantability, or fitness for a particular purpose.

### 8. Player Acceptance

* By playing Battlefrens, players confirm that they fully understand and accept all associated risks.
* If a player does not agree with these terms, they must refrain from participating in the game.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.battlefrens.fun/terms-and-conditions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.