Skip to content
grostifyConnectDocs

Security and privacy

How Connect protects your API, your users' credentials and the data that flows through it.

On this page

Credentials and encryption

  • Each integration has its own data key. It is encrypted with a master key in Google Cloud KMS that never leaves KMS.
  • Your users' credentials (access and refresh tokens, or API keys), your OAuth client secret and the signing keys are encrypted with that key using AES-256-GCM.
  • Meta business tokens and test credentials are also encrypted with AES-256-GCM, with a key kept in Google Secret Manager.
  • Connect's own authorization codes and refresh tokens are stored only as hashes.
  • Connect only shows the last 4 characters of a key or test credential again.

Credentials are added to each request to your API and never reach the AI model. If your API echoes a credential in its response, Connect replaces it with [redacted] before passing the result on. Credentials shorter than 8 characters are not replaced.

Your API, and only your API

  • Connect calls your API only after you verify your domain, and only on that host.
  • Calls use HTTPS, ports 443 or 8443, and public addresses only. Private, local and cloud metadata addresses are blocked.
  • Redirects are not followed.
  • Each call has a 10 second timeout and a 2 MB response limit.

Each user, their own access

  • Every call carries the credential of the user who asked. An assistant only sees what that user can see in your system.
  • Users approve the access on a Connect page that shows your verified domain, every time they connect. Connect never sees their password.
  • The pages your users see cannot be embedded in other sites.
  • You can revoke any connection at any time.

What Connect records

For each tool call, Connect records the tool, the channel, the result, the HTTP status, the time it took and the size of the response. It never records the arguments or the response. Changes to integrations, reviews and connections are recorded too, with IP addresses stored as a hash.

WhatsApp messages

  • The text of messages is stored so your team can read it in the inbox. It is never written to server logs.
  • When you connect a number you already use in the app, your previous chat history and your phone's contacts are not imported.
  • Media files are not downloaded.

Web chat

  • The session cookie is partitioned, HttpOnly and Secure. The JavaScript of your website never sees it and Connect stores only its hash.
  • The chat runs in an iframe that only the origins you allow can embed. Your page never sends text to the assistant.
  • The text of the conversations is never written to server logs and is deleted after 30 days. Your company sees metrics, not text.
  • Links in the answers are removed unless they point to your verified domain.

See Web chat.

AI providers

FeatureWhat is sent to Anthropic
Tools in Claude and ChatGPTNothing. Connect does not call any model: results go to the user's own assistant.
Write descriptions with ClaudeThe structure of your API: names, paths, parameters and response field names. Never your data or credentials.
WhatsApp assistantThe customer's questions and the results of the tools needed to answer them. Never credentials or your team's messages.
Web chatThe customer's questions and the results of the tools needed to answer them. Never credentials.

Where it runs

Grostify operates from the United States. Connect runs on Google Cloud, and its keys are in Cloud KMS in the us-east4 region.

Delete data

Read the privacy policy (opens in a new tab) for retention periods and your rights.