Agent Blocked routes human-intervention alerts for AI and LLM agents. This policy explains what information we collect, how we use it, and how to contact us about your data.
Information we collect
- Contact details such as email address, phone number, and profile label.
- Alert settings such as channels, event types, severity threshold, quiet hours, timezone, connected agents, and custom instructions.
- Agent incident details sent to the webhook, including agent ID, run ID, provider, model, event type, severity, confidence, reason, details, and timestamps.
- Delivery history for email, SMS, and voice alerts, including sent, failed, or skipped status.
- Billing state such as selected plan, trial dates, subscription status, Stripe customer ID, and Stripe subscription ID.
- Authentication identifiers needed to associate alert profiles with signed-in users.
How we use information
- To create and manage alert profiles.
- To route agent incidents to the contact channel and rules you configure.
- To generate short voice-call scripts for voice alerts when OpenAI is configured.
- To provide test alerts, incident history, token rotation, support, billing, and account management.
- To prevent abuse, debug delivery problems, and maintain service reliability.
Service providers
Agent Blocked uses service providers to operate the product: Supabase for authentication and data storage, Stripe for checkout and subscriptions, AWS SES for email, Twilio for SMS and voice calls, OpenAI for optional voice-call script generation, and Vercel or similar hosting infrastructure for deployment.
SMS alerts and mobile numbers
If you choose SMS alerts, Agent Blocked uses your mobile phone number to send transactional alerts about your configured AI agent incidents, such as blocked runs, approval requests, credential issues, low confidence, or tool failures. Message frequency varies based on your alert settings and agent activity. Message and data rates may apply.
Agent Blocked does not sell, rent, or share mobile phone numbers or SMS consent information with third parties or affiliates for their own marketing or promotional purposes. Mobile numbers may be shared with service providers, such as Twilio, only as needed to deliver SMS alerts, operate the service, prevent abuse, or comply with law.
You can opt out of SMS alerts at any time by replying STOP. For help, reply HELP or contact support@agentblocked.com.
Secrets and tokens
Provider credentials for Supabase, Stripe, Twilio, SES, and OpenAI should live only in server-side environment variables. Scoped agent webhook tokens authorize agent reports for a specific alert profile and can be rotated from the manage page if exposed.
Retention and deletion
Alert profiles can be deactivated from the manage page. Incident and delivery records may remain for operational history, abuse prevention, support, billing reconciliation, and debugging unless deletion is requested or a retention process removes them. To request deletion or export of your profile data, contact support.
Your choices
- Update alert rules, contact channels, quiet hours, and custom instructions from the manage page.
- Rotate scoped agent webhook tokens if they are exposed.
- Use Stripe Billing Portal to manage payment methods, plan changes, and cancellation when billing is active.
- Contact support to request help with access, correction, export, or deletion.
Contact
For privacy questions or data requests, contact support@agentblocked.com.
