Transparency note (not legal advice): This document explains InnoStak's current technical and product practices in plain English for informational transparency. It is not legal advice and should be reviewed by qualified legal counsel before relying on it for regulatory or marketplace compliance.
Plain-English Summary
InnoStak builds InnoAgents (ai.innostak.com) and the InnoAgents Slack app so small teams can run AI employees with clear guardrails:
- No training on your data: Neither InnoStak nor our commercial AI API providers train AI models on your prompts, Slack messages, Google Workspace files, emails, calendars, or HighLevel CRM data by default.
- Channel & role isolation: New AI employees start with zero tool access. Slack access is limited to channels you invite the app into and enable per employee; Slack Connect shared external channels are ignored.
- Human approvals before external sends: External emails, Slack DMs to other people, and HighLevel outbound messages/writes require explicit approval.
- You control disconnects and deletion: You can disconnect any integration immediately from Connections and request full workspace/Slack data deletion anytime at support@innostak.com.
1. Which AI Providers & Models Run
| Workload | Provider & Models | What Context Is Sent |
|---|---|---|
| Chat, tasks, rooms, Slack replies & email drafts | Anthropic (claude-sonnet-4-6 default, plus claude-haiku-4-5 & claude-opus-4-7) | Employee instructions/Agent DNA, relevant workspace memories/documents, active chat or Slack thread text, and outputs of tools turned on for that employee |
| Web search (when turned on for an employee) | Anthropic (web_search_20250305) | Search queries generated by the employee to look up current public web facts |
| Live voice calls & audio previews | xAI (grok-voice-latest, grok-transcribe, /v1/tts) | Real-time browser-direct audio over wss://api.x.ai/v1/realtime during live calls; voice sample text when generating custom voice previews |
| Owner-only beta model testing | xAI (grok-4.x) | Restricted exclusively to InnoStak staging/owner-only beta flags (never routed for regular customer workspaces) |
| Image & portrait generation | OpenAI (gpt-image-2, gpt-image-1.5, gpt-image-1, gpt-image-1-mini) | Image description prompt, approved Brand Kit colors/rules, and optional reference image — never Slack text, emails, or CRM records |
| Agency client-portal Slack ticket detection | Groq (openai/gpt-oss-20b) | Only used on InnoStak's agency client-portal Slack webhook to classify support tickets — never called by InnoAgents workspaces |
2. Training & Vendor Data Retention
- InnoStak: We do not use customer content, Slack conversations, Google Workspace data, or CRM data to train or fine-tune models.
- Commercial AI API Terms: Standard commercial API terms for Anthropic, xAI, OpenAI, and Groq prohibit model training on API data by default.
- Vendor Log Retention Windows: Unless organization-level Zero Data Retention (ZDR) is active on a specific provider account, commercial API vendors typically retain encrypted API inputs and outputs temporarily for safety/abuse monitoring — generally up to 30 days under Anthropic, xAI, OpenAI, and Groq default commercial terms. Owner-beta xAI text requests set
store: falseviaxai-adapter, while live InnoAgents Voice sessions connect directly from your browser to xAI over WSS with session resumption enabled (not currently enforcing xAI team-level ZDR in code). Contact support@innostak.com for current provider ZDR and region confirmations.
3. How Slack Data Flows Through InnoAgents
What Slack Data Is Accessed
- Public & private channels you enable: Only after a Slack user adds the app to a channel AND an InnoAgents admin turns that channel on for a specific employee.
- Slack Connect / external shared channels: Automatically ignored.
- Direct Messages (optional): When Slack DMs are enabled (
im:history,users:read.email), incoming DMs match the Slack user's email in memory against active members of your InnoAgents organization so unauthorized external users cannot talk to your employees. Email directories from Slack are not stored for marketing.
What Happens During a Slack Turn
- Live reads: On a
@mentionor enabled reply, InnoAgents reads up to 20 replies in the thread; an optional 15-minute watcher checks up to 40 recent messages. - Tools in Slack channels vs. DMs: Channel replies can check HighLevel (only if granted to that employee) and run web search (if enabled) — they never search your Google Drive, Gmail, or Google Calendar inside channels. Matched-member DMs run in the employee's chat flow using that employee's granted tools and approval rules.
- Rate limits: Built-in caps limit autonomous replies to 3 per thread/hour, 40 per channel/day, and 5 outbound sends per turn.
- Storage: Handled channel messages are saved in
crew_slack_events(up to 4,000 characters of text, user ID, channel ID, timestamp), and Slack DM turns are saved increw_conversations/crew_messagesisolated to your organization (account_id).
4. Google Workspace, HighLevel & Voice Privacy
- Google Drive (
drive.file), Calendar (calendar.events.readonly), Gmail (gmail.readonly): Scoped per employee; adheres to the Google API Services User Data Policy (Limited Use). Temporary Drive conversion copies are deleted immediately after reading. - HighLevel: Read access to conversations, invoices, and payments; sending outbound messages requires an explicit owner/admin approval in the InnoAgents Inbox before sending.
- Voice calls: Your browser opens a direct encrypted WebSocket to xAI using a 2-minute ephemeral client secret. Transcripts stored in
crew_voice_sessions(up to 200 turns) automatically mask SSN-like patterns and 12–19 digit payment/account number runs.
5. Human Approval & AI Limitations
- Approvals: Scheduled tasks, external
@agents.innostak.comemails, Slack DMs initiated to another person, and HighLevel outbound messages wait for human review before going out unless explicitly approved by an authorized user. - Limitations: AI employees can make mistakes, misread tone, or cite inaccurate details. Treat generated drafts, research, and summaries as first drafts for human review — never rely on AI outputs without verification for legal, tax, financial, medical, compliance, or employment decisions.
6. Disconnect, Uninstall & Data Deletion
| Action | What Happens Immediately | What Remains & How to Delete |
|---|---|---|
| Disconnect Slack in InnoAgents | Revokes the Slack token, marks the connection revoked, and deletes employee grants and channel picks. Clears the stored Slack token and deletes Slack DM routing data (crew_slack_dm_routes and the Slack user map). Clears stored Slack event text and Slack user ids. | InnoAgents chats (including Slack DM chats), documents, and approval records stay until you delete them or email support. |
| Disconnect Google or HighLevel | Revokes Google access where supported, marks the connection revoked, and removes grants and HighLevel sub-account picks. Employees stop using it right away. | Workspace files and chats stay until you delete them or request deletion. |
| Uninstall or revoke the app in Slack | app_uninstalled and bot tokens_revoked run the same Slack cleanup as Disconnect: stored Slack token cleared, Slack DM routing data deleted, event text cleared, connection marked revoked. | InnoAgents chat history is kept. Email support@innostak.com for anything else you want deleted. |
| Delete an AI employee | Cascades deletion of that employee, its chats, messages, runs, memories, DNA history, and tool grants. | Workspace-level documents are kept with agent_id = null unless deleted; aggregate credit counters remain in ai_usage_log. |
| Automatic system trims | — | Concurrency slot logs purge after 30 days; tool-call before/after field values purge after 12 months. |
| Email support@innostak.com | We confirm receipt within 2 business days. | Complete workspace, account, and Slack/integration deletion or export completed within 30 days (excluding records required by law/billing). |
For related details, see our Privacy Policy, Terms of Service, Subprocessors, and Support.