Security and secrets

You control the credentials used by your destinations and log streams. CLItrail encrypts saved credentials and does not display their full values again.

#Write-only credentials

After you save an API secret, access token or key, the dashboard shows that it is set, identifying details and when it was updated. Keep your own secure copy: CLItrail cannot show the original value again.

#Replace or revoke access

Create a replacement credential in the platform that issued it.
Open the destination or log stream in CLItrail and choose Replace.
Choose Send test to check the replacement, then revoke the old credential at its source.

Removing a destination or log stream deletes its saved credentials. To revoke access immediately, revoke the credential in the platform that issued it.

#Signing secrets for your webhooks

Save the signing secret when you create a webhook or log stream; it is shown once. If you lose it, use Rotate secret and update your receiving endpoint. See webhook verification for the code your endpoint needs.

#Protect your account

Give team members only the role they need. Review active sessions in Account and security and sign out any you do not recognise. Secure the Google account or mailbox you use to sign in.

#In transit

Use HTTPS for your website and receiving endpoints. CLItrail redacts credentials from logs. Never paste live credentials into a support request, screenshot or shared document.

#Data and privacy

Read What is collected for the data involved in attribution, and Retention and deletion for your export and deletion options.

#Report a security issue

Email founders@pilotprotocol.network with what you found and the steps to reproduce it. Never include live credentials; rotate any you shared by mistake.