Omnibot

Description Permissions Security & Compliance

Omnibound: AI-Powered Workspace for B2B Marketing Execution
Omnibound is an AI-powered workspace designed for B2B marketers. It unifies structured and unstructured data, strategy, and assets into a Marketing Context Engine, enabling AI agents to generate insights and drive execution—making every campaign, asset, and decision faster, sharper, and more revenue-focused.AI Disclaimer
Omnibound leverages AI to analyze Slack conversations and generate insights and recommendations that help teams make data-driven decisions.
While our Prompt models are continuously improved for accuracy and relevance, the generated insights may occasionally be incomplete or inaccurate.
We recommend users review and validate all AI-generated insights before taking any business or strategic actions based on them.How Omnibot Works with Slack
Slack as a Data Source
Omnibot can access selected Slack channels with read-only permissions to analyze messages and uncover insights.
By enabling the Conversation Intelligence toggle, Omnibot identifies patterns, themes, and trends from team discussions, surfacing key takeaways and helping users understand collaboration dynamics.
Users have full control over which channels are connected, and all data is accessed securely.Setup and Permissions
Connect Slack through Omnibot under Data Sources → Chat → Slack.
Required permissions are minimal:
channels:history channels:join channels:read chat:write groups:history groups:read users:readDisconnect Anytime
Users can disconnect Slack at any time. Once disconnected, all synced data is deleted, and access is fully revoked.Pricing
Omnibot is currently free during our public beta phase.
Pricing plans will be announced soon. For enterprise or early access inquiries, contact support@omnibound.ai.

Omnibot will be able to view:

Omnibot will be able to do:

Review the details to better understand this app’s security practices. To learn more about assessing apps for your workspace visit our Help Center.

General

Privacy & data governance

Data retention policy

1. Data Retention Policy Purpose: This policy defines how long customer and business data are retained within our systems. Policy: Customer data (including account information, configuration, and usage data) is retained for the duration of the customer’s active subscription or engagement with our services. Upon termination of the customer relationship, all customer data is retained for up to 90 days to support billing reconciliation, potential reactivation, and legal requirements, unless otherwise requested by the customer or required by law. After the retention period, data will be permanently deleted from production and backup systems in accordance with the data removal process.

Data archiving and removal policy

2. Data Archival and Removal Policy Purpose: To ensure customer data is managed responsibly and deleted securely once it is no longer needed. Policy: We do not archive customer data once the customer relationship ends. Data identified for removal is securely deleted from active systems and backups within 90 days, using industry-standard deletion and overwriting mechanisms. In case of a customer data deletion request (e.g., GDPR “Right to be Forgotten”), data is erased from all systems within 30 days of verification. No physical or offline archival of customer data is maintained.

Data storage policy

3. Data Storage Policy Purpose: To define where and how customer data is stored, ensuring compliance with regional and contractual obligations. Policy: Data is stored in cloud environments hosted in geo-specific regions based on the customer’s location and regulatory requirements (e.g., EU data in EU regions, US data in US regions). All data is encrypted at rest and in transit using industry-standard encryption (AES-256 for storage and TLS 1.2+ for transmission). Access to storage systems is restricted based on least-privilege principles and monitored through secure access controls and logging. No customer data is transferred outside the designated geo-location without explicit consent or legal necessity.

App/service has sub-processors

App/service uses large language models (LLM)

Certifications & compliance

Security