Privacy notice

What we collect

• Account data: email address, password (stored only as a salted hash), and, if you fill it in, your name, institution, position, discipline and research areas.
• Research content: projects, documents, uploads, notes, evidence records, claims, approvals and version history you create in the workspace.
• Operational logs: timestamps, the action taken and which project it touched, kept so that changes can be attributed.

What leaves this service

• Literature lookups. When you search, resolve a DOI or look up an ORCID, only the query you typed is sent to the relevant public index (PubMed, Europe PMC, Crossref, Semantic Scholar, arXiv or OpenAlex). No project content is attached.
• Language model calls. When a configured provider is used, the passage or instruction you explicitly selected is sent to that provider. Editor rewrites send only the selected text — not your whole document, not your project state.

We do not sell data, do not use your research content for advertising, and do not train models on it.

Who can see your work

Projects, documents and uploads are scoped to their owner. Another signed-in user cannot read, download or modify them. Administrators of your deployment can manage accounts and can see operational metadata; they do not read your documents as part of normal operation.

Uploads

Files are checked for extension, declared type and content signature before storage, and are capped in size. A file that does not match its declared type is rejected. Extracted text is used to make the file searchable and quotable inside your own project.

Retention and deletion

Your content is kept while your account exists. You can delete individual uploaded files from the workspace at any time. To have your account and its projects removed, contact the administrator of the deployment you use.

Cookies and local storage

We use browser local storage to keep you signed in and to remember your light/dark theme choice. There are no advertising or cross-site tracking cookies.

Security

Requests are authenticated with signed bearer tokens, access to another user's project returns no data at all, authentication and chat endpoints are rate limited, and every project change is recorded as an immutable, hashed version.

Contact

Questions about this notice should go to the administrator of the deployment you use.