> For the complete documentation index, see [llms.txt](https://whitepaper.datahunter.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.datahunter.fun/gameplay/quests/unlocking-the-cloud.md).

# Unlocking the Cloud

The **Cloud** is a digital storage space accessible from your phone (📱 top-right corner). It allows you to **store Data beyond your active team**, which is limited to **6 creatures**.

Thanks to the Cloud, you can **swap stored Data with your active team at any time**.

<figure><img src="/files/ChPsBsR6Arz98k07CJfu" alt=""><figcaption></figcaption></figure>

1. **Form a full team of 6 Data.**
   * You can catch wild Data during your exploration.
   * Or speed things up by opening **Boosters** (available in the Shop).
2. Once you’ve gathered 6 Data in your team, **go back to Dr. Senzu** (in your starting village).
3. He will unlock the **Cloud app**, directly on your phone.

> ⚠️ The Cloud can store up to 32 Data, so use it wisely.
>
> Perfect for keeping your rarest creatures safe… especially before entering a dangerous zone!

\ <br>


---

# 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://whitepaper.datahunter.fun/gameplay/quests/unlocking-the-cloud.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.