Privacy policy
Last updated: 13 October 2026
What BRIDGE collects when you use it, why, who else receives it, who can see your work, and how to ask us to delete it. Plain language, no small print.
Who runs BRIDGE
BRIDGE is a student project of team P-046 in the AI20K Build Phase Cohort 4. It is not a company. It is a free research tool.
We decide what is collected and why. For any question about your data, use the contact page or write to Trần Đại Nhân at nhantd.dev@gmail.com.
What we collect
Your account. When you sign in we keep your e-mail address, your name, the address of your profile picture, the time of your last sign-in and an identifier from our sign-in provider, Clerk. An account made before Clerk sign-in may also hold a salted hash of its password, never the password itself. For each signed-in browser we keep the browser name text (the user agent), so the account page can list your sessions.
Your work. The topics and questions you type, the reviews made from them, the papers you save with notes and folders, your drafts, the citation checks of your text, the repository links you check, and the PDFs you upload (a research proposal or the PDF of a paper). Your use of credits is counted per account.
Contact tickets. If you send one: your name, subject and message, the page you were on, your e-mail address if you gave one, and your account number if you were signed in. We do not store your IP address, only a keyed hash that cannot be turned back into the address, which is enough to see that two tickets came from one address.
What we do not collect. BRIDGE takes no payments yet, so we hold no card or bank details. We do not sell your data and we show no advertising.
Sign-in, and Google
Sign-in is run by Clerk (clerk.com). Clerk checks who you are and keeps its own record of your sign-in. Its policy is at https://clerk.com/legal/privacy.
If you choose Google, Clerk receives your name, e-mail address and profile picture from Google, the basic profile only, and passes them to us. BRIDGE does not ask Google for anything else, not your contacts, your Drive, your Gmail or your calendar.
Who can see your work
Reviews and repository audits are open by default. Anyone who has the link can read one, and a review appears with its topic in the list of recent reviews. Its creator can hide it from the list, but the link still opens it. Only the creator, and the administrators of the site, can change, stop or ask questions on a review. So do not put into a topic anything you do not want others to read.
A review started from a research proposal is private: only its creator and the administrators can read it. The proposal itself, the text read from a PDF you upload, your drafts, your library and your citation checks are visible to you and to the administrators only.
Who else receives data
We send data to these services only to provide BRIDGE:
OpenAI receives the text you type or upload and the text of papers, so that its models can screen papers, read them, check citations and write the review. OpenAI's own terms apply to it: https://openai.com/policies.
Semantic Scholar, OpenAlex, arXiv, PubMed and Crossref receive the search queries and paper identifiers we send to find papers and to check citations. Publisher and repository sites are fetched for the open-access text of papers, and Hugging Face is asked about the datasets that papers use.
GitHub is where a repository you name is downloaded from. BRIDGE reads its files and never runs its code.
Clerk runs sign-in, as described above.
PostHog receives usage measurement, when it is switched on (see below).
Gmail carries the e-mail that delivers a contact ticket to the team.
Cookies and browser storage
litreview_session keeps you signed in. It lasts up to 30 days and scripts on the page cannot read it.
Clerk sets its own cookies and storage to run sign-in. Its policy describes them.
litreview-lang lasts one year and remembers whether you read English or Vietnamese.
litreview_device lasts one year, is sent only to the sign-in address, and is a security mark that helps tell a browser that signed in with a password before from someone guessing passwords.
Local storage in your browser keeps your choices: the language, whether the side panel is folded, the papers you marked, text you were typing and have not sent, and your measurement choice. It stays in your browser.
We set no advertising cookies and do not follow you across other sites.
Usage measurement
When the team has switched it on, BRIDGE uses PostHog, in its EU cloud, to count page views, clicks, errors and a few named events such as starting a review. It records where you click, not the text of the page, and every text and input is masked in a screen recording. Page addresses lose review ids and everything after a question mark. It is never meant to hold your topic, your paper titles or your e-mail address.
If you are signed in, the events carry an id made from your account number with a secret key, so PostHog never sees your e-mail address or your account number.
Measurement stays off when your browser sends Do Not Track or Global Privacy Control. You can also turn it off with the switch in the account menu, or in the notice shown on your first visit.
Our server also sends its own error reports to PostHog: the type of the error and where in the code it happened, with e-mail addresses and web query strings removed.
How long we keep it
Your account, reviews, library, drafts, uploaded PDFs and tickets stay until you ask us to delete them. There is no delete button yet, so ask on the contact page or by e-mail.
A sign-in session lasts up to 30 days, or until you sign out.
The data of the site is backed up every night and the 14 newest copies are kept. Data we delete leaves the backups as the older copies are replaced.
Your choices
You can ask us for a copy of your data, a correction, or the deletion of your account and its work, on the contact page or by e-mail. A person on the team reads every request.
You can turn measurement off, clear cookies, and sign out the other browsers from the account page.
BRIDGE is for research work. Please do not put sensitive personal data, such as health or identity documents, into topics, drafts or uploads.
Changes to this page
When this page changes, the date at the top changes with it.