Legal
Privacy
KnowMee holds a record of your working life. That is a serious thing to be trusted with, so this page says plainly what we hold, where it goes, and how to take it back.
Last updated
Who we are
KnowMee is operated by Zevora Labs Pvt Ltd, registered in India. For anything on this page, including a request to export or delete your data, write to privacy@knowmee.io.
We are the data controller for your account and your record. The processors we use are listed below, in full.
What we hold
- Account
- Your email address, name and profile image, from whichever method you signed in with. Held by Clerk, our authentication provider; we store a copy of the email, name and image so the product works when Clerk is slow.
- Your record
- The facts that make up your career record — projects, roles, skills, education, achievements — each one stored with the source it came from and when we captured it.
- Source material
- The original text each fact was drawn from: a README, a pull request title, a line from a résumé, a paragraph you pasted. We keep it because a fact that cannot name its source is not evidence, and because it lets us re-derive your record if we improve the extraction.
- Connections
- Access tokens for services you connect, encrypted at rest. You can disconnect any of them at any time, which deletes the token.
- Nothing else
- No advertising identifiers, no cross-site tracking, no behavioural profile, no data bought from a broker.
Where it comes from
Every source is one you choose and switch on yourself. Nothing is gathered in the background.
- GitHub
- Through a GitHub App with read-only permissions, on the repositories you pick at install. We never ask for blanket private-repository access and we cannot write to your code. Facts drawn from a private repository stay private in your record unless you publish them.
- Only from the export archive you download from LinkedIn and upload to us. We do not scrape LinkedIn, and we do not buy LinkedIn-derived data from anyone.
- Résumé
- A PDF you upload. It is read once to extract facts, then retained as the source behind those facts.
- AI memory
- Text you paste from another assistant, or a ChatGPT export archive you upload. From an export we read only your own messages, never the assistant's replies.
- You
- Anything you type or correct directly.
There is no browser extension and there never will be. Nothing watches what you do.
Who processes it
We use these companies to run the service. They act on our instructions and hold data only to provide their part of it.
- Neon
- The database. Your record lives here, in the ap-southeast-1 region (Singapore).
- Upstash
- The job queue. Holds import jobs briefly while they run.
- Anthropic
- Reads your source material to turn it into structured facts. Anthropic does not train on data sent through its API.
- Clerk
- Authentication. Holds your sign-in identity and session.
- Vercel · Railway
- Hosting for the website and the API.
- Razorpay · Dodo Payments
- Payments, if you subscribe. We never see or store your card details.
Because our infrastructure is in Singapore and some processors operate from the United States and the European Union, your data is transferred internationally. Those transfers rely on the processors’ standard contractual clauses.
How AI reads your record
KnowMee can act as a source of context for AI assistants you connect, through the Model Context Protocol. This only happens after you authorise a specific client and only for as long as you leave it connected.
- A connected client reads your record through a token issued to it alone. It cannot read anyone else's.
- Every read is scoped to your account. There is no shared index across users.
- A connected client may also add to your record, which always returns a visible confirmation so you can see and remove it.
- Revoking access anywhere in your account settings ends it immediately.
See the MCP documentation for exactly which tools a connected client can call.
Other people in your record
Your work involved other people, so their names appear — a co-maintainer on a pull request, a company you worked at, a person you built something with.
We treat those names as references inside your record, not as profiles. We do not build a record for anyone who has not signed up, we do not enrich those names against other sources, and we do not make them searchable.
If your name appears in someone else’s public KnowMee page and you want it removed, write to privacy@knowmee.io and we will act on it.
What is public
Your public page at knowmee.io/your-name shows only the facts you have marked public. Everything else — the raw source text behind each fact, anything from a private repository, anything you have not published — is never served to it.
You can take the page down at any time without deleting your record.
Your rights
Wherever you live, you can do all of the following, and we will not ask why.
- Get a copy
- A complete export of your record and its sources, in a format you can read without us.
- Correct it
- Edit any fact directly in the product. Corrections are versioned, so nothing is quietly overwritten.
- Delete a fact
- One tap. It is removed, not hidden.
- Delete everything
- Deleting your account removes your record, your source material and your connections. Backups roll off within 30 days.
- Withdraw a connection
- Disconnect any source; the token is deleted immediately. Facts already captured stay until you remove them.
- Object or complain
- Write to us first. If we cannot resolve it you may complain to your local data protection authority.
How long we keep it
Your record is kept for as long as your account exists, because that is the product — a record that forgets is not one. Delete your account and it goes, with backups rolling off within 30 days. We do not keep a shadow copy.
Children
KnowMee is not for anyone under 16. We do not knowingly hold data about children; if you believe we have, tell us and we will remove it.
Changes
If this policy changes in a way that affects what we do with your data, we will email you before it takes effect rather than quietly editing this page. The date at the top always reflects the current version.