Privacy.

enoki runs entirely within the Google Cloud project you deploy it to. Inference uses that project’s own Vertex AI; every Google Cloud action runs under the connecting Slack user’s own Google identity, bounded by their IAM. The project authors operate no shared service and receive no data, telemetry, or analytics from your deployment.

enoki is built to keep no Slack data outside your project, and as little as possible inside it. The hosted configuration keeps conversation history in memory only, so no Slack message text is written at rest; channel names and file contents are never persisted. The only long-lived state is each user’s Fernet-encrypted Google refresh token and an append-only audit record of the actions taken.

Self-hosted deployments may optionally enable a short-lived transcript cache (ENOKI_PERSIST_HISTORY=1, a 24-hour TTL in your own Firestore) so threads continue across restarts — off by default. enoki never uses your Slack or Google Cloud data to train any model; inference runs on your project’s own Vertex AI with request data excluded from training.

If you deploy enoki for your organization, you are the data controller for that deployment: the encrypted tokens, audit trail, and any cached context sit in your project, under your control and your retention rules.

enoki calls Google Cloud and Slack on your behalf using credentials you supply. Data handled by those platforms — API requests, OAuth grants, workspace content — is subject to their own privacy terms, not this one. enoki requests only the OAuth scopes needed for the tools you enable.

Slack scopes are least-privilege with a stated purpose. The history scopes (channels:history, groups:history, im:history, mpim:history) exist only so the Slack MCP Server can read the specific channel or thread you ask enoki about, on demand and under your own user token — never a bulk export, and nothing is stored. The search:read.* scopes back query-based search; users:read resolves the requester; chat:write and canvases:* let enoki reply and draft workflow blueprints. enoki does not request admin.* scopes.

This marketing site is a static SvelteKit app deployed to Vercel. It sets no advertising or cross-site tracking cookies. Vercel may collect standard, aggregated request logs (such as IP address and user agent) as part of serving the site.

The contact form opens your own mail client to send a message to 2495.immanuel@gmail.com; nothing is submitted to a server on this site. If you email us, we use your message only to reply.