Privacy Policy

When you connect your Google Account, kinroo requests these OAuth scopes — nothing broader:

• calendar.events — see, create, edit, and delete events on your calendar. kinroo reads events to answer your questions and to warn you about conflicts. kinroo never creates or changes an event silently: every change is either shown to you for confirmation first, or — if you’ve turned on adding without asking for that channel — reported to you right after, with a one-click undo.
• calendar.calendarlist.readonly — list the names of your calendars, so the settings page can let you pick which one kinroo writes to, instead of asking you to paste a raw calendar ID.
• openid, email — your Google account email, used to identify your account with kinroo.

kinroo does not request access to Gmail, Drive, Contacts, or any other Google product.

The extension reads from web pages in two ways. When you click “Find events on this page”, it reads that page’s visible text. While the kinroo panel is open and its compose box is empty, it also picks up text you’ve selected on the current tab and puts it in the compose box. Selected text stays in the panel and isn’t sent anywhere until you press send. The first time you scan a page kinroo can’t already read, Chrome asks you to allow access to web pages. That access is optional, and you can turn it off at any time under the extension’s site access in Chrome’s extension settings. kinroo doesn’t record which pages you visit or keep your browsing history.

Google Calendar is the only place your events live. kinroo doesn’t keep its own calendar, and the only event details it stores are the undo record for changes it made from your emails (below). What we do store, in a Postgres database:

• Your Google account ID, email, and name, so we know who you are.
• Your Google OAuth tokens, encrypted at rest (AES-256-GCM) — never stored in plain text.
• Your preferences: timezone, default event duration, and which calendar kinroo writes to.
• Lightweight usage metadata for each request you send (how long it took, whether it used our AI parser, whether you confirmed or corrected the result). This is for reliability and cost monitoring — it does not include the text, image, or file content of your request.
• If you send kinroo events by email: a record of each change it made from that email (the email’s subject, and the title, time, and location of each event it added, changed, or canceled), so you can undo or correct them from kinroo’s reply. If you have email auto-add turned off, a temporary record of the change you asked for instead, held only until you reply to confirm or it expires.
• If you join our waitlist: the email address you submit.

When you type a sentence, paste a screenshot, upload a flyer or PDF, or scan a page (its visible text, up to 4,000 characters), kinroo first tries to parse it with fast, local pattern-matching. When that isn’t confident enough — ambiguous phrasing, a photo, a multi-page flyer — the text or image is sent to Anthropic’s Claude API to extract the event details. That content is processed to generate a response and is not used by Anthropic to train models, per Anthropic’s API terms.

When you ask a question about your schedule, kinroo reads the relevant events from your Google Calendar. A simple question like “what’s on Sunday” is answered directly from those events, without Claude. For other questions, such as “when is my dentist appointment” or “am I free Saturday afternoon”, kinroo sends your question to the Claude API along with the title, time, and location of each event in the period it covers. That period is the dates you asked about, or the next 60 days if you didn’t name any. Claude only picks which of those events answer the question. The answer you see is built from your actual calendar events, not written by the AI. The same Anthropic API terms apply to this content, and kinroo doesn’t store it.

In the extension, nothing is written to your calendar until you review and confirm it, unless you’ve turned on adding without asking in settings. For email, kinroo adds what it finds right away by default and replies with what it did, so you can undo or correct anything; you can switch email to reply-to-confirm instead. When you reply to one of those emails with a correction (“1 is at 7pm”), your reply and the list of events it refers to are sent to the Claude API to work out what to change.

• Google Calendar API — reads and writes events on your behalf, per the scopes above.
• Anthropic (Claude API) — parses text/image input into structured event data when our fast-path parser can’t confidently handle it, and picks which of your calendar events answer a question, as described above.
• Neon — hosts our Postgres database (the account and settings data described above).
• Vercel — hosts kinroo’s backend and this website.

We do not sell your data, and we do not share it with anyone else for advertising or marketing purposes.

• Revoke kinroo’s access at any time from your Google Account permissions page.
• Uninstalling the kinroo Chrome extension stops all activity, but doesn’t by itself revoke Google access or delete your account data — do both of the above if you want a clean break.
• To request deletion of your account data from our database, email us at the address below.

kinroo is not directed at children under 13, and we do not knowingly collect data from them.

If this policy changes materially, we’ll update the date at the top of this page. Continued use of kinroo after a change means you accept the update.

Questions, or want your data deleted? Email kinroo.ai@gmail.com.