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

# Security and privacy

Calling your endpoint from a website, proxies and Cloudflare, logging, the \_\_blocked.rpcpool.com origin, and security contacts.

<details>

<summary>How do I call my endpoint from my website without exposing my token?</summary>

Never put a token in frontend code. Add your site as an allowed origin and call the endpoint URL with no token:

1. Under the endpoint's **Allowed origins**, click **Add origin**.
2. Enter the hostname without `https://`, for example `app.example.com`.
3. Click **Save**.

* An endpoint accepts up to 5 active origins by default.
* An allowed origin isn't a secret, so use a token for servers.

See [Allowed origins](https://docs.triton.one/security/authentication.md#allowed-origins-frontend).

</details>

<details>

<summary>Can I put a proxy or Cloudflare in front of my endpoint?</summary>

* Triton doesn't recommend a proxy. You don't need Cloudflare or another provider for DDoS protection.
* If you still need one, contact support first.
* Every user behind a proxy shares one IP's rate limits and blocks.
* Tokenless requests from data-centre IPs can get `403`.
* A TLS-terminating proxy reads your traffic and can change it. That includes your token and any transactions you submit.
* Triton can't guarantee the integrity of responses that pass through a proxy.
* To limit or control the RPC calls your endpoint accepts, ask support for a custom rate tier instead.

See [Proxying](https://docs.triton.one/using-your-endpoint/proxying.md).

</details>

<details>

<summary>What does Triton log, and for how long?</summary>

* **Shared services:** RPC logs are collected only for abuse prevention and operational stability, and kept for 4 weeks. Triton doesn't identify or de-anonymise individual end users.
* **Dedicated services:** you choose max privacy, enhanced privacy (the default) or GDPR privacy.

See [RPC log retention and privacy levels](https://docs.triton.one/security/privacy-and-security.md#rpc-log-retention-and-privacy-levels).

</details>

<details>

<summary>What is `__blocked.rpcpool.com` in my allowed origins?</summary>

* Triton adds it when you turn on an endpoint that has no allowed origins.
* It allows no browser origin, so only requests with a token work.
* Don't remove it. An active endpoint needs at least one active origin.
* It counts toward the 5 active origins while it's active.

See [Allowed origins](https://docs.triton.one/security/authentication.md#allowed-origins-frontend).

</details>

<details>

<summary>Who do I contact about privacy or security?</summary>

* **General security or privacy questions:** click the chat icon in the bottom right of your [customer dashboard](https://customers.triton.one).
* **Urgent security reports:** <security@triton.one>.

See [Contact](https://docs.triton.one/security/privacy-and-security.md#contact).

</details>

***

<i class="fa-life-ring">:life-ring:</i> Contact support by clicking the chat icon in your [customer dashboard](https://customers.triton.one)\ <i class="fa-briefcase">:briefcase:</i> Sales questions? [Contact us](https://triton.one/contact)\ <i class="fa-sparkles">:sparkles:</i> AI agent? Read [llms.txt](https://docs.triton.one/llms.txt)\ <i class="fa-rss">:rss:</i> Follow updates: [Blog](https://blog.triton.one) · [X](https://x.com/triton_one) · [YouTube](https://www.youtube.com/@triton_one_ltd) · [Telegram](https://t.me/tritonone) · [GitHub](https://github.com/rpcpool)
