wakeahuman
1. Automatic Secret & PII Redaction
Before any code snippet or context summary is stored or sent to Telegram, Slack, Discord, or a Decision Room, WakeAHuman runs edge pattern scrubbing to redact Stripe keys, AWS access keys, JWT/Bearer tokens, database connection URIs, generic API secrets, and email PII. You should still avoid pasting raw production credentials into chat replies.
2. What We Store
- Account identity: Your GitHub handle, display name, and public avatar URL used to identify your workspace and optional
1ST → 2ND → 3RDteam escalation relay slots. - Connected channel targets: Your verified Telegram
chat_id, Slack incoming webhook / channel metadata, or Discord channel webhook metadata—used strictly to deliver wake cards you or your team trigger. - Wake state & receipts: Scrubbed wake questions, option labels, human decisions, and
HMAC-SHA256verification signatures so your MCP agent can resume reliably.
3. OAuth Scopes & Permissions
Slack, Discord, and Telegram integrations request only the minimum permissions required to post interactive escalation cards into the channel or DM you choose and receive your button clicks back. WakeAHuman does not read unrelated channel history or private messages.
4. Revoking Access & Deleting Data
You can disconnect Slack, Discord, or Telegram at any time from their respective app settings, or remove teammates from your escalation relay directly on wakeahuman.com. To request complete deletion of your workspace and wake records, open an issue or reach out via GitHub (@gel).