> For the complete documentation index, see [llms.txt](https://docs.lab.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lab.pro/getting-started/publish-your-docs.md).

# Safety Tips

LAB Terminal gives you full control over your assets. That means you — and only you — are responsible for securing your wallet. Here’s how to do that properly ⬇️

{% tabs %}
{% tab title="Backup Your Seed Phrase" %}
Your seed phrase is your master key. **Anyone with access to it can take your funds.**

**To back it up:**

{% stepper %}
{% step %}
Go to the Settings section in the bottom menu.
{% endstep %}

{% step %}
Select **“Export Seed Phrase.”**
{% endstep %}

{% step %}
Press and hold the blue button to reveal your 12 secret words.
{% endstep %}
{% endstepper %}

**Write them down on paper and store them somewhere safe** — never save your seed phrase in screenshots, notes, or cloud storage.
{% endtab %}

{% tab title="Enable Additional Security Measures" %}

* Set a PIN Code: From the Profile → Security section, set a PIN. This will be required once a day and when logging in from new devices.
* Enable Telegram Cloud Password: In Telegram’s native settings, set a cloud password for added protection in case someone accesses your Telegram account.
  {% endtab %}
  {% endtabs %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lab.pro/getting-started/publish-your-docs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
