Legal

Privacy policy

What Kairo keeps, why it keeps it, who helps run it, and how you take it back. Written in plain words.

Last updated: 3 November 2026

Your story stays in your Claude

Your CV, your facts, salary, cover letters and form answers are never sent to Kairo.

The dashboard is optional

Only if you use it do we keep the public job post, your fit score, verdict, flags, status dates and your email.

Download or delete anytime

Settings → Download CSV, or Settings → Delete my data. No email needed.

01Who runs Kairo

Kairo is a free, open-source job search partner that works inside Claude. It is built and run by Rohan Surve, an independent developer (“we” on this page). We decide what Kairo stores and why, so we are responsible for your data.

Kairo is not made by, part of, or endorsed by Anthropic.

02The two parts of Kairo

The Kairo skill

The skill runs inside your own Claude account. All the AI work (fit checks, CVs, cover letters, form answers) happens there, under your agreement with Anthropic. We cannot see your Claude chats, files or projects. If you use the skill without the dashboard, Kairo receives nothing from you at all: your tracker stays in the chat.

The dashboard and connector

The dashboard at kairo.rohansurve.in and the Kairo connector in Claude are optional. Only when you sign in and connect them does Claude send a small, fixed set of job facts to our server. Our server uses no AI: it never sends your data to an AI service.

03What we store

Only if you sign in to the dashboard or connect Kairo in Claude. You agree to this policy when you sign in: the sign-in page says so, and your account is created at that moment.

Your sign-in email	To sign you in and show which dashboard is yours.
Your sign-in ID (from WorkOS)	To link your dashboard and your Claude connector to the same account.
The jobs you check	The public job post only: company, role, country, city, work mode, the link, posting date, years of experience asked, the salary if the post shows one, and the job text.
Your result for each job	Fit score, verdict (Apply, Maybe or Skip), red flags (short public text, never your own numbers), visa flag and the public proof for it (a quote from the job post or a public register page with a date).
Status history with dates	Each status (checked, applied, interview, offer…), its date, and whether you changed it in Claude or on the dashboard.
Account dates and ticks	When you first signed in (and agreed), which version of this policy that was, your setup checklist ticks, and when the connector was last used, to show your setup progress.
A count of calls per hour	To stop overuse (about 120 calls an hour). Deleted after one day.

We use this only to run your job tracker. We do not sell it, share it for ads, send you marketing email, or use analytics or tracking tools on the site.

04What we never store

Your CV or any line from it
Your “my facts” file
Salary answers, current or expected salary
Cover letters
Application form answers
The reasons behind your fit score (they quote your CV)
Personal details such as phone, date of birth or nationality

These stay in your own Claude. Our server refuses any field it does not expect, and red flag text with an email address or phone number is rejected, so private details cannot slip in by mistake.

05Shared job posts

A public job post is stored once, even if several people check the same job. This is how Kairo spots duplicates. Your fit score, verdict, red flags, visa flag and status are private to you. Nobody else can see that you checked a job.

06Who helps run Kairo

These companies process data for us, only to run the service:

WorkOS	Sign-in. Sends you the 6-digit code and keeps your email and sign-in ID.
Neon	Database. Your dashboard data, stored in Singapore.
Vercel	Hosting. Our server runs in Singapore. Like any web host, it handles basic request data (such as your IP address) to deliver pages.

WorkOS may process your sign-in data outside your country. Claude itself is not part of this list: you use Claude under your own Anthropic account and Anthropic’s privacy policy.

07Cookies

We use only the cookies needed to sign you in. No ads, no analytics, no tracking.

kairo_session	Keeps you signed in to your dashboard. Lasts 7 days, or until you sign out.
kairo_oauth	Protects the sign-in step. Lasts 10 minutes.
kairo_notice	Shows “You’re signed out” once on the home page after you sign out. Lasts 5 minutes.

Your browser also remembers, for this visit only, if you closed the banner at the top of the home page.

08How long we keep it

Your dashboard data is kept until you delete it. When you click Settings → Delete my data:

Your jobs, scores, verdicts, flags, status history and call counts are deleted at once.
Your account is emptied: no email, no IDs. We keep only the date it was deleted.
Your WorkOS sign-in is deleted too.

Public job posts stay, because they are not linked to you. Our database and hosting providers may keep short-lived backups and technical logs for a limited time before they are overwritten.

09Your rights

We store your data because you agreed to it when you signed in. Wherever you live, you can:

See your data	Everything is on your dashboard. Settings → Download CSV gives you a copy.
Correct it	Change a status or its date on the dashboard or in Claude. For anything else, email us.
Delete it	Settings → Delete my data, at any time.
Take back your consent	Delete your data. You can also remove the Kairo connector in Claude at any time.

In India, the Digital Personal Data Protection Act, 2023 gives you the right to access, correct and erase your data, and to raise a complaint with our grievance contact first and then with the Data Protection Board of India.

In the European Union, the GDPR gives you the right to access, correct, delete and take a copy of your data, to object, and to complain to your local data protection authority.

To use any right we cannot handle in Settings, email us. We will reply within one month.

10Security

Every connection uses HTTPS. Sign-in is by a one-time email code (no passwords). Every connector call is checked against your WorkOS sign-in, and one user can never read another user’s jobs. Our server does not write sign-in tokens or the content of your requests to its logs. No system is perfectly safe; if something goes wrong that affects you, we will tell you.

11Changes

If this policy changes, we update the date at the top. If we ever want to store something new, we will ask you first.

12Contact and grievances

Questions, requests or complaints about your data: Rohan Surve, rohan.surve5@gmail.com.

Grievance contact (India, DPDP Act)

Rohan Surve, rohan.surve5@gmail.com