Skip to content

Social Terminal 1.21.0 / Operations

Terminal data and external requests

Distinguish local terminal state from data and external requests owned by add-ons.

Free core terminal use is local. Public page loads do not contact the licensing authority. Transcript and command-history behavior follows the configured actor and browser policy.

A deliberate account connection, license action, protected install, or update may send the site URL, random installation ID, WordPress environment, requested product, and submitted credential to Cointacted. Credentials are encrypted at rest and must not be pasted into support logs.

AI providers, blockchain RPCs, commerce services, community systems, and other external requests belong to their owning add-ons and are documented there. Clearing a visible transcript does not erase those systems’ records.

Social Terminal must never print private keys, passwords, license secrets, authentication tokens, or raw provider credentials.

Was this documentation helpful?Your response helps us improve this page.