Public node safety notes

Free public nodes are not recommended for sensitive use because you rarely know who operates them, how traffic is logged, or whether configuration has been modified. Avoid entering sensitive accounts through unknown nodes.

Security, Privacy & Compliance

Direct answer

Free public nodes are not recommended for sensitive use because you rarely know who operates them, how traffic is logged, or whether configuration has been modified. Avoid entering sensitive accounts through unknown nodes.

What to check first

Proxy tools do not remove legal, security or privacy responsibilities. Protect subscription URLs, avoid unknown nodes and follow the rules of the network and jurisdiction you are using.

  • Keep subscription URLs, tokens and node details private.
  • Avoid unknown free nodes for sensitive accounts.
  • Remove private domains and identifiers before sharing logs.
  • Follow local law, workplace policy and provider terms.

Recommended handling

Use the conservative path: protect private URLs, avoid unknown nodes for sensitive accounts, and follow the rules of the network and jurisdiction you are using.

Practical notes

  • Remove URLs, tokens, node names and private domains before sharing screenshots or logs.
  • Change one setting at a time so the result is attributable.
  • Use logs and timestamps when asking for provider or community support.