Privacy

AI Search Bro stores account, workspace, client, domain, keyword, topic, content, run, artifact, and publishing-status data needed to operate SEO, GEO, and AEO workflows. During beta, users should treat the service as an operational product for marketing data, not as a vault for secrets unrelated to publishing.

The application uses login sessions and tenant-scoped API credentials so work can be separated by workspace. Publishing integrations may require repository, CMS, or automation credentials. Those credentials should be scoped to the smallest useful role and rotated when a teammate or agent no longer needs access.

We use submitted domains, keywords, prompts, briefs, drafts, and performance data to provide the product workflow: queueing work, generating drafts, tracking state, and helping users decide what to publish next. Contact [email protected] for account questions, removal requests, or integration concerns.