Privacy
Last updated 2026-11-16.
A request to RefLib says nothing about you
When an assistant (an LLM) calls RefLib, all that is known is that a program asked a reference library for a passage. The assistant chooses what to ask. It may be working on someone else's task, or it may be hallucinating. Such a record cannot be used for any consequence about the person whose key or account made the call. It is of no use to anybody, and RefLib does not treat it as information about you.
Nothing is passed on
Even so, RefLib does not disclose, share, sell, rent, or in any other way pass any information about you or your use of RefLib to anyone, under any circumstances, except where legally forced to do so by a court order.
What is kept
- Your account: username, email, and a scrypt hash of your password (never the password itself). If you sign in with GitHub or Google, RefLib receives and keeps only that provider's account id, and uses your verified email and your login or name to set up the account.
- API keys: a SHA-256 hash of each key and its first 10 characters. The key is shown to you once and is not stored.
- Each MCP request: the time, the key and account, the tool, the corpus, the question text, the section read, how close the best match was, the result status, and the server time. Not the answer. These rows are used only to run RefLib: its speed, its errors, and the questions the library answers badly.
- Corpus suggestions you submit or upvote, tied to your account.
- Contact form messages, delivered to RefLib by email with your address.
- Server logs: the web server records the address, time, page and browser of each request, including searches made on the website. Web server logs are kept 14 days; the system log is kept until its space is reclaimed.
Account data is kept until you ask for the account to be deleted. MCP request rows are kept; when an account is deleted, its rows no longer point to it.
Cookies
reflib_user: your signed-in session, 30 days. reflib_oauth: 10 minutes, only while signing in with GitHub or Google. There are no analytics, advertising or tracking cookies, and no third-party scripts.
Who runs it
The server and email are hosted by IONOS. GitHub and Google are involved only if you choose to sign in with them; your accounts there are under their own policies.
Your choices
Delete API keys at any time on your account page. To delete your account or get a copy of what is kept about you, write through the contact form.
If this policy changes, the date above changes. See also the terms.