Account and key security
Protect keys, local configuration and diagnostic data.
On this page
Keep secrets separate
Use a unique Etage password and check the site address before signing in. An API key authorizes spending on your behalf: store it in a protected server environment or trusted local client, not a public repository or browser JavaScript. Create separate keys with suitable restrictions for different tasks.
Enter the key locally
Automatic setup takes your key in the local terminal on your computer. Documentation does not ask for a key in a form. Run commands only from the trusted Etage address and restrict access to configuration files. Do not insert a key into a command that will remain in shared terminal history, a screenshot or a log.
Remove secrets from diagnostics
Before sharing a report, remove Authorization, cookies, passwords, verification codes, keys and private messages. If a key may have leaked, delete that key in your account, create a new one and update clients. Deleting text from the latest message does not remove older copies. This guidance does not define a data retention period or a separate retention policy; avoid sending confidential data unnecessarily.