> For the complete documentation index, see [llms.txt](https://support.trybit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.trybit.com/security/account-protection.md).

# Account Protection Recommendations

How to recognize scammers and secure access to your account.

### Trybit staff never ask for

* your account password;
* two-factor authentication (2FA) codes;
* any login information other than your email — for example, when verifying your identity in a support conversation.

Trybit staff also never ask you to install remote-access software on your computer.

### General recommendations

* use a strong, unique password that doesn't match passwords for other services, and update it roughly every 3 months;
* use a password manager (such as 1Password or LastPass) instead of storing your password in a browser or on paper;
* be sure to enable two-factor authentication — more details on the [Setting Up Two-Factor Authentication page](/security/2fa.md);
* use reliable antivirus software on the device you use to log in to your account.

{% hint style="success" %}
If you have any questions or need help, you can contact our support via chat on the website and in your personal account, as well as reach us on Telegram. Support contacts are listed [on our website](https://trybit.com/support).
{% endhint %}


---

# 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://support.trybit.com/security/account-protection.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.