AI and your data
For people invited to the Kipwise beta · last changed 19 October 2026
What agents see
When someone asks an agent to do something, it reads what it needs from what your workspace has given it: the thread, Knowledge pages, files uploaded to the thread, and the connections granted to its Space. What it reads is sent to the model provider so the model can write the answer.
Agents can search the web and open web pages. They run code in a sandbox, which gets a copy of the files uploaded to that thread.
In your own chat with Kipwise, it keeps facts you tell it about yourself on your private “About you” page and reads that page at the start of each chat with you. You can edit or remove anything on it.
Services that handle customer data
| Service | What it does for Kipwise | What it sees |
|---|---|---|
| Railway | Hosts Kipwise and its database | Everything stored in Kipwise, including uploaded files, which are kept in the database Which region the servers and database are in: to confirm |
| Cloudflare | Sits in front of Kipwise and passes each request on to Railway | Every request your browser sends to Kipwise and every page it gets back, with your IP address Which Cloudflare features are turned on, such as caching or a firewall. Which region Cloudflare keeps logs in, and for how long: to confirm |
| The model provider | Writes the agents’ answers | The messages, pages, files and search results an agent reads while it answers, and what it writes back Which provider serves the beta, and the second one Kipwise switches to when the first is down. How long the provider keeps what it is sent, and whether it trains on it: to confirm |
| E2B | Runs the sandboxes where agents run code | The files uploaded to a thread, and the scripts and output an agent works with there Which region the sandboxes run in, and how long E2B keeps them: to confirm |
| Resend | Sends email | Your email address and the emails Kipwise sends you, such as sign-in links and invites |
| PostHog | Product analytics and error reports | Which screens you open and what you click, and reports of errors, tied to your user id only. Your name and email are not sent. Whether screen recordings are turned on in the PostHog project. Which region PostHog keeps the data in: to confirm |
| DuckDuckGo or Brave Search | Web search for agents: Brave when the deployment sets a Brave key, else DuckDuckGo | The words an agent searches for. Pages it then opens are fetched from their own websites. Which of the two the beta uses: to confirm |
| Google Fonts | Serves the fonts of the workspace and these pages | Your IP address and browser details, each time a page loads its fonts |
| jsDelivr | Serves the script of the API reference page | Your IP address and browser details, when you open the API reference page |
| TypeSafe Only when it is turned on | Judges how much work a message to Kipwise needs, before Kipwise answers it, and sorts the files a new workspace’s owner gives Kipwise during setup | A message sent to Kipwise in the web app, and up to three earlier messages from the same chat, shortened. During setup, the name, type, size and headings of each file the owner gives Kipwise, but not the rest of what the files say. Not spreadsheets, images or videos, and not messages to named agents or from Slack. Whether the beta turns this on. How long TypeSafe keeps what it is sent: to confirm |
| Google Only when it is turned on | Sign in with Google, and the Google Drive connector | For sign-in, your Google account’s name and email. For Drive, the files an agent searches and reads in the folders it was given. |
| Slack Only when it is turned on | Lets people talk to Kipwise from Slack | Messages in the Slack channels linked to Kipwise and in direct or group messages sent to the Kipwise app, and the replies Kipwise posts there |
| GitHub Only when it is turned on | Sign in with GitHub, and the GitHub connector | For sign-in, your GitHub account’s name and email. For the connector, the requests an agent makes with that account, and what comes back. |
| Intercom and custom HTTP connectors Only when it is turned on | Accounts an admin connects so agents can read or act in them | The requests an agent makes with that account, and what comes back. A custom connector is sent only to the hosts an admin entered for it. |
Still to confirm
These facts are not settled yet. The page will be updated when they are, and the date at the top will change.
- Railway: Which region the servers and database are in. to confirm
- Cloudflare: Which Cloudflare features are turned on, such as caching or a firewall. to confirm
- Cloudflare: Which region Cloudflare keeps logs in, and for how long. to confirm
- The model provider: Which provider serves the beta, and the second one Kipwise switches to when the first is down. to confirm
- The model provider: How long the provider keeps what it is sent, and whether it trains on it. to confirm
- E2B: Which region the sandboxes run in, and how long E2B keeps them. to confirm
- PostHog: Whether screen recordings are turned on in the PostHog project. to confirm
- PostHog: Which region PostHog keeps the data in. to confirm
- DuckDuckGo or Brave Search: Which of the two the beta uses. to confirm
- TypeSafe: Whether the beta turns this on. to confirm
- TypeSafe: How long TypeSafe keeps what it is sent. to confirm
How long we keep your data, and how to have it deleted, is in the Privacy notice.
Contact
Questions about where your data goes: the Kipwise team’s support address to confirm.