Privacy notice

For people invited to the Kipwise beta · last changed 19 October 2026

What we keep

• Your name and email address.
• What you and your team write in Kipwise: threads, replies, Knowledge pages, memory and the files you upload.
• What agents write for you, and the steps they took. In your own chat with Kipwise, it keeps facts you tell it about yourself on your private “About you” page, which you can edit.
• The accounts you connect, kept as encrypted access tokens.

How we use it

Only to run Kipwise for your workspace and to fix what goes wrong. An agent reads what your workspace has given it, when someone asks it to do something.

Services that handle it

Kipwise uses these services to run: Railway, Cloudflare, The model provider, E2B, Resend, PostHog, DuckDuckGo or Brave Search, Google Fonts, jsDelivr, TypeSafe, Google, Slack, GitHub, Intercom and custom HTTP connectors. What each one does, and what of yours reaches it, is on AI and your data.

In your browser

Kipwise sets a cookie that keeps you signed in. PostHog keeps an id in your browser so its analytics can tell visits apart; it is tied to your Kipwise user id, not your name or email.

Keeping and deleting

We keep your data while your workspace exists. During the beta, to delete your account or your workspace, email the Kipwise team from the address you sign in with. We delete it within 30 days.

Setup keeps the files you give it, and what Kipwise read from them, for 30 days after setup was last worked on, then deletes them. The files Kipwise kept in your Libraries, including the text of most files it set aside there, are not deleted with them: they stay until someone deletes them.

Contact

Questions about your data: the Kipwise team’s support address to confirm.