Privacy

Browsing without an account

No account, no profile, no tracking cookie for advertising: none is set, because there is no advertising. Anonymous product analytics (PostHog, hosted in the EU) records page views and interactions without building a person profile for signed-out visitors, and it can be blocked without affecting the site.

The site is served through Cloudflare, which sees the request metadata any CDN sees — IP address, user agent, the URL — and applies rate limiting with it. Search queries reach the backend, which uses the forwarded visitor address purely to rate-limit the paid step of a semantic search; it is not stored alongside the query.

What an account stores

Signing in is by emailed magic link or a one-time code. Identity is handled by Supabase, which holds the email address and issues the session token; the rest lives in this project's own PostgreSQL database, keyed by a user id.

• Your email address, and the sign-in timestamps that come with it.
• Interests: the topics, researchers and papers you follow.
• Library: papers you saved, and any notes attached to them.
• Feedback: the thumbs you gave a recommendation, used to rank the next ones.
• Conversations: your assistant chats, including the questions you asked.

Who processes it

Four processors, each for one job: Supabase for authentication and email delivery; PostHog (EU) for product analytics, where a signed-in session is identified by user id; Cloudflare for delivery and abuse protection; and OpenRouter, which routes assistant and summarisation requests to the model that answers them.

That last one matters most: when you ask the assistant a question, the question, the page you asked it from and the relevant paper text are sent to a model provider through OpenRouter in order to produce an answer. Do not paste anything into it you would not want processed by a third-party model. Nothing in this database is sold, and none of it is shared for advertising.

Cookies and local storage

Two things persist in your browser, both functional: the Supabase session cookie that keeps you signed in, and a local-storage flag remembering that you finished or skipped onboarding so the wizard stops reappearing. Clearing site data removes both, and signing out clears the session cookie.

Retention and deletion

Account data is kept while the account exists. Email [email protected] from the address you signed up with to get a copy of what is stored, to correct it, or to have the account and everything keyed to it deleted; deletion is done by hand and confirmed by reply.

Public corpus data — papers, researchers, institutions — is not personal data of yours and is not removed by an account deletion. If a *researcher profile* carrying your name is wrong or you want it removed, that is a separate request and also welcome; see Contact.