# Protect Your UpScalp and Exchange Accounts

**Last reviewed:** 2026-05-23.

Most support and security problems start with a bad link, a fake support DM, or weak account protection. Use this checklist before connecting any workflow to trading activity.

Use this page when checking API-key safety, exchange credentials, withdrawal permissions, fake support messages, or any request for secrets.

## Start from official links

1. Open links from [Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links).
2. Compare Telegram usernames character by character.
3. Treat unsolicited support DMs as suspicious.
4. Do not act on urgency messages asking for funds, wallet access, or secrets.

## Secure Telegram and exchange accounts

1. Use unique passwords stored in a password manager.
2. Enable two-factor authentication where available.
3. Review active sessions.
4. Log out unknown devices.
5. Keep recovery email and phone access secure.

## Keep secrets out of chat

Never share:

1. Seed phrases.
2. Private keys.
3. Exchange passwords.
4. Exchange API secrets.
5. Account recovery codes.

UpScalp support will never ask for seed phrases, private keys, exchange passwords, exchange API secrets, or account recovery codes.

## API keys and exchange permissions

Lite and Premium do not require you to create exchange API keys.

If you are approved for a Private Beta API setup, follow only the official approved setup flow. Stop and contact support if any instruction asks you to:

1. Enable withdrawal permissions.
2. Send API keys through Telegram, email, chat, or support messages.
3. Paste exchange credentials into an unofficial form.
4. Use a different Telegram bot or support account.

## Before any approved API setup

Only continue with API setup when all checks pass.

| Check        | Required condition                                                                          |
| ------------ | ------------------------------------------------------------------------------------------- |
| Approval     | You have explicit Private Beta approval through the official route.                         |
| Instructions | The setup instructions come from the approved flow, not a public chat or DM.                |
| Permissions  | Withdrawal permission is off. Any requested permission is limited to the approved setup.    |
| Storage      | You are not asked to send API keys or secrets through chat, email, or screenshots.          |
| Doubt        | If anything differs from the approved flow, you stop and contact support before continuing. |

## If compromise is suspected

1. Stop trading actions.
2. Revoke suspicious sessions and permissions.
3. Change passwords from a clean device.
4. Rotate two-factor authentication if needed.
5. Record a UTC timeline.
6. Contact support with evidence that does not expose secrets.

## Related

1. [Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links)
2. [Contact Support](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-contact-support)
3. [Legal and Trading Risk Notice](https://upscalp.gitbook.io/upscalp-docs/trust-and-safety/upscalp-legal-and-risk-notice)
4. [What UpScalp Does and Does Not Automate](https://upscalp.gitbook.io/upscalp-docs/trading-principles/upscalp-what-upscalp-does-and-does-not-automate)


---

# Agent Instructions: 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:

```
GET https://upscalp.gitbook.io/upscalp-docs/trust-and-safety/upscalp-security-and-account-protection.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.