Last revised August 2026
Privacy
This foundation stores the information required to operate accounts, routines, connected tools, run history, and delivery.
Information handled
Account identifiers, routine configuration, encrypted connection metadata, model and tool traces after redaction, API-key metadata, and webhook delivery records. OAuth access and refresh tokens and complete Discord webhook URLs are credentials encrypted at rest and never included in analytics.
Why it is handled
To authenticate users, execute configured routines, preserve audit history, deliver results, secure the service, and diagnose failures.
Business inquiries
The Business contact form collects name, work email, company, expected run volume, history requirements, workload context, and consent. We use it to assess fit and follow up about Business; it is not used to authorize routine execution or payment.
Service providers
Deployment may involve SQLite or PostgreSQL hosting, depending on deployment, LLMGateway, model providers selected through the gateway, and MCP servers configured by the organization owner. Website speed onboarding also uses Google PageSpeed Insights, which receives the protocol, hostname, port, and path of the submitted website URL. Credentials, query strings, and fragments are removed before that request.
Retention
We retain Business inquiries only as long as needed to assess and respond, unless a longer period is required for legitimate business or legal reasons.