Privacy policy

If you visit this website

We count the visit, and record which page you landed on, the site that referred you, and any campaign tags in the link you followed. No account is required, no profile is created, and we don’t record what you click or type. We don’t count visits to pages inside the product this way.

If you ask for a demo

We keep your name, your work email, your team’s size, and anything you write about what you’d like to cover, and we share it with our team so someone can reply. With each request we also record the network address, country, browser, and page you sent it from, so we can keep spam out. If you book a time on trykiwi.now, the booking is handled by Google Calendar under Google’s privacy policy.

If you use Kiwi

Your account: your name, email address, and team.

What you make: the agents you build, the asks you give them, their runs, and what you and your team decide at each checkpoint. If you dictate an ask by voice, the recording is sent to OpenAI to turn it into text; we don’t keep the recording.

Your connected tools: when you connect a tool, Kiwi copies what your agents need from it, for the people on your team who use Kiwi, and nothing before that. Depending on what you connect, that can be:

• records from your CRM (HubSpot, Salesforce, or Attio), such as accounts, contacts, and deals
• calendar events from Google Calendar
• meeting notes and transcripts from Granola or Fathom
• from Gmail, the sender, recipients, subject, labels, and Gmail’s short preview of person-to-person mail from the last 120 days. Never the full message, and nothing from promotions, social, updates, or forums
• a LinkedIn data export you upload, or outreach history from Linked Helper
• messages you send to Kiwi from Slack

Kiwi keeps earlier versions of these records, so any run can show exactly what it was working from. Sign-in tokens and keys for your tools, and the original records copied from them, are encrypted by Kiwi, and our databases are encrypted at rest.

Usage and errors: product events tied to an internal account identifier and your organization’s identifier: which screens you open, which buttons and links you click, the requests the app makes (what kind of request, whether it worked, and how long it took), and actions such as signing in, connecting a tool, and starting or approving a run. Click events hide the text on the page and leave out page addresses. When something breaks, we receive an error report: the error, where it happened, and a request ID. For AI features we record operational details such as the model, token counts, timing, and whether the call succeeded. We don’t send the content of your runs, notes, emails, or connected records to analytics.

What we use it for

To run Kiwi for you, keep it secure, support you, and work out which parts are useful and where people get stuck. Demo requests are used to reply to you and to keep spam out. We don’t sell your data, we don’t share it with advertisers, and we don’t use your runs, notes, or connected data to train AI models.

If you sign up with a work email, we also use its domain to identify your company, so we can show your company’s name and logo as our terms of service describe. We don’t name you.

Who else handles it

Only the service providers we need to operate, under agreements that limit them to working for us:

• Render, which hosts Kiwi and its databases in the US
• OpenAI and Anthropic, which run the AI models that do your agents’ work. They receive what a step needs, under API terms that don’t let them train their models on it. If your team saves its own model key, those calls go through your own account instead
• PostHog, in the US, for the usage events and error reports described above
• Google Workspace and Slack, which our team uses to receive and answer demo requests

Data moves between Kiwi and a tool you connect only because you connected it, and writing back to one, such as updating a CRM record, waits for a person’s approval unless your team set it up otherwise. Disconnecting a tool stops it. We may share information if the law requires it, or as part of a merger or sale of the business, in which case this policy still applies to it.

How long we keep it

Demo requests are kept until you ask us to remove them. Account data, including everything copied from your connected tools, is kept while your account is active and deleted within 30 days of you closing it. When something is deleted in a tool you’ve connected, Kiwi deletes its copy too, keeping only a fingerprint that can’t be turned back into the original, so past runs still make sense.

Your choices

Email us and we’ll show you what we hold about you, correct it, or delete it, usually within a few days and at most 30. If you’re in the EU, UK, or California, these are your legal rights (access, correction, deletion, portability); we honor them for everyone regardless. If your data reached Kiwi through a customer’s connected tools, for example as a contact in their CRM, we’ll work with that customer to handle your request.

Cookies

We use cookies only to keep you signed in. PostHog keeps a pseudonymous identifier in your browser’s local storage rather than a cookie, and session recording is off. We don’t use advertising trackers.

Changes

If this policy changes in a way that matters, we’ll email you and note the new date above. No silent edits.

Contact

Questions or requests: hello@withkiwi.ai