Privacy

This is what Kite collects and why.

Your account

Your email, and your name and photo if you sign in with Google. We use them to show who shared a file and to email you about activity on your files.

Your files

Your design files, and the pictures you add to them, are stored so they can be shown to the people you share them with. They are private to you and your workspace until you share them. We don't read them, train on them, or sell them.

Viewers

Opening a file is counted, but nobody is shown who opened theirs. Someone who isn't signed in is counted without a name, and nothing about it is kept on their device. People who comment are shown by their name or email.

How Kite is used

To see what to make better, Kite records the pages you open and what you do — making, sharing and commenting on files, connecting agents and the tools they call — against your account, never what is in your files. While you're signed in, your sessions are recorded as replays with every text masked and every picture hidden, so we see where Kite gets in the way, not what you made. Someone who isn't signed in is only counted, never recorded.

Cookies

We use cookies to keep you signed in, to remember that you passed an email check on a file shared with you, and, once you're signed in, to count your visits as yours (PostHog's, kept in your browser's storage too). No advertising cookies.

Figma

If you connect Figma, Kite keeps an encrypted access token and uses it only to fetch the pictures of layers you paste from Figma, from files you can open. It never changes your Figma files. Disconnect in Settings, under Connect, and the token is deleted.

Kite Capture, the Chrome extension

Kite Capture reads the page you point it at, only when you press its button, and puts a copy of it on your clipboard for you to paste into Kite. It has no account and sends nothing to Kite or anyone else: what you paste is all that reaches Kite. To copy pictures a page shows from other sites, it fetches them itself, only if you turn that on, and only for that copy. It keeps nothing once the copy is made.

Agents you connect

When you connect an AI agent — Claude, ChatGPT, Grok, Muse, Cursor or another — you sign in to Kite and allow it. It can then make and edit design files for you, change who can open them, and read and answer their comments, only in your account. Kite receives only what the agent sends to Kite's tools, never your conversation with it. We keep the agent's name, to show it on the board while it works, and a sign-in token, stored hashed: it lapses after 7 days, and the agent can renew it for up to 90 days. Disconnect it in Settings, under Agents, and it stops at once.

Services we rely on

Supabase (database and storage), Vercel (hosting), Resend (email), Google (sign-in, if you choose it), Figma (if you connect it), PostHog (how Kite is used, in the US).

How long we keep things

Your account and files are kept until you delete them. Archive a file from the library; it stays in the Archive until you delete it forever. A page deleted inside a file is removed for good after 30 days, and older versions of a file are thinned out as they age. Server logs are kept by Vercel for a limited time under its own retention.

Deleting

Delete your account from Settings, and everything you own goes with it: your account and your files' pictures are deleted at once, your files go offline, and they are deleted for good a month later. What PostHog holds on you — your events and replays — is deleted with your account.

Questions: hello@kite.new