ClawdCall

Use ClawdCall as a controlled voice-agent execution system, not as a generic HTTP API. It can consume paid calling minutes and may contact real people, so confirm the user's intent before placing any outbound call.

Security Model

• Run ClawdCall in a dedicated or restricted OpenClaw agent when handling multiple users, shared workspaces, or sensitive call data.
• Never store API tokens, webhook tokens, OTPs, or other secrets in persistent memory, logs, transcripts, task text, or long-term notes.
• Use secure runtime storage for secrets when available. Environment variables are preferred.
• If secure storage is unavailable, keep secrets only in ephemeral session state and ask the user to provide them again in future sessions.
• Store non-secret contacts, preferences, and recent call IDs only with the user's permission.