Skip to main content

How Templ keeps users and teams safe

Chat cannot sign or send transactions. Wallet sign-in binds the exact site and . Each user reads their own . Each team action checks current access. Never share a private key or recovery phrase.

Protect users​

Sign in through the sign-in card. Templ refuses signing, approval and transfer instructions from ordinary staff and . Current human workspace owners and Admins can include those instructions in their own replies. Requests for private keys, recovery phrases and credentials remain blocked for everyone. Templ refuses recognized recovery phrases and private keys before storage. Ambiguous hex values and Solana signatures stay visible to your team and the user. Templ hides them from bots, webhooks, AI and exports unless shared as a typed transaction. A can redact them.

Wallet proof proves address control at that time. It does not prove a person's identity. Spot fake support explains what users should check.

Check team access​

Managers grant explicit roles. Billing, assignments, token ownership and display names grant no case permission. Every private read, reply, export, search result, attachment and event checks current access. Removing support access ends access to retained history and open connections. The public support link opens a visitor’s own chat. In Standard chat, Templ’s servers process messages. The visitor and authorized workspace staff can read them. An enabled, authorized AI can share permitted input with its model provider. In customer-controlled encrypted chat, only approved endpoints with the workspace’s keys can decrypt messages. Templ’s relay sees delivery metadata. The customer holds the recovery keys and backups. Templ operates the team and recovery service for its own encrypted support. Earlier messages keep their original protection. A saved export or screenshot can leave Templ's access checks.

Stop team messages stops replies, initiation and reopening, including managers and AI agents. Only the user can ask again and lift the stop.

Protect AI sources​

Treat AI instructions and sources as public. AI replies can include them. Never add keys, recovery phrases, passwords or private documents. Apply this rule even when a source is marked Team only. Private cases and uploaded files still require current access.

Check AI providers​

Your agent's operator chooses its model provider and which case data it receives. That provider is the company that runs its model. Tell users which provider receives their messages and apply your agreed retention rules. Keep , secrets and unrelated cases out of model inputs. Templ's own support AI uses OpenAI when enabled. Enabled, approved pilot responders use the same OpenAI setup through Codex. Your workspace's plan or existing signed agreement controls charges. New prepaid workspaces use GPT-6.1 Sol through OpenAI when Templ AI is available and enabled. Existing agent agreements keep their recorded provider and terms.

Limit Templ access​

A signed gives Templ people no case access by itself. The form must allow Templ staff access. Your manager grants each person a team role under the signed order form. The active form, current role and approved Templ account are required on every access check. Removing any requirement ends access, including open connections. Operators, billing and order forms give no case access.

Review data and providers​

Case data explains retention and exports. De-identified copies explains the separate improvement copy. Read Trust and Privacy for providers and data terms.

Report a problem​

Describe the problem or security issue in Templ’s support widget. Do not include a private key or recovery phrase.

Details for developers​

The app uses SIWE or SIWS wallet sessions. Verified email sign-in uses a one-time code and a separate account. It never adopts an account through its alert address or merges accounts. Manager and billing changes still require a valid wallet session. Email alerts keep their separate verification and opt-in. Wallet challenges bind domain, URI, chain, nonce and expiry. Widget challenges also bind the intended workspace resource. A widget session has only the member permission role and gains no app or team authority. sessions share the exact origin and workspace scope. Contract-wallet signatures fail closed without their supported verification. Keep replay and revocation checks. See the widget reference.