Contact
There is exactly one way to reach this project: email guweiicy@gmail.com. This page explains why there is no contact form, what to put in a message so that it can be acted on, how to report a security problem, and which parts of the tool we cannot help you recover.
Last updated:
Email guweiicy@gmail.com is the only contact channel. There is no contact form, no chat widget, no ticket system and no phone number, because the site is a set of static files with no backend: a form would have nowhere to post to, unless we added a server, and adding one would undo the reason this tool exists.
Why there is no form
A form needs an endpoint, an endpoint needs a server, and a server is the thing this project is built to avoid. The alternative would be a third-party form service, which means handing your message and your IP address to another company and putting a script from that company on a page of a site that claims to have one external host. Neither is worth it for a mailbox that already works.
The address is a normal mailbox. Mail you send is read by a person, kept only as long as it takes to answer and to keep a record of the fix, and deleted if you ask for that. It is not added to a mailing list, because there is no mailing list, and it is not used for marketing.
What to include, by kind of report
| Kind of report | What to include |
|---|---|
| A bug: an import fails, an answer is empty, a button does nothing | Browser name and full version (Chrome 140, Safari 18, for example), your operating system, the file type, the file size, and the exact wording of the message shown, with its code if one appears (FILE_TOO_LARGE, PDF_ENCRYPTED, PDF_NO_TEXT_LAYER, LEGACY_DOC, UNSUPPORTED_FORMAT, MODEL_LOAD_FAILED). If a document was involved, the kind of document is enough — never send the document itself. |
| A wrong or missing model, licence or number on the models page | The model name and the figure you checked, with a link to the upstream model page you compared against. Numbers on our side are meant to match the model page, so a mismatch is our error. |
| A retrieval problem: the answer missed a passage you know exists | The document type, roughly how long it is, the wording of the question, and whether the passage appears in the citations. That last point separates a search problem from a reading problem. |
| A privacy question, or a deletion request for an email you sent | The question, and for a deletion request the address and subject line you used, so the right message can be found and removed. |
| An accessibility problem | The page or panel, the assistive technology and version, and what happened instead of what you expected. If a screen reader announced something twice or not at all, the exact wording you heard is the most useful part. |
| A correction to anything written on the site | The page, the sentence, and the source that contradicts it. Corrections that cite a primary source are applied fastest. |
Reporting a security problem
If you find a way to make the tool send document content, questions or answers off the device, or a way to read another site’s or another user’s data through this site, that is the highest priority class of report and it should be sent to guweiicy@gmail.com with “security” in the subject line. Include the browser and version, the steps that reproduce it, and what you observed in DevTools if you saw traffic that should not exist. Please do not test against other people’s data, and do not run automated scans against the hosting provider.
There is no bug bounty programme, no reward fund and no legal contract behind this address, and we would rather say that up front than imply a payment that does not exist. What we can offer is a real fix, described in the changelog, and credit in the entry if you want it.
One clarification that saves time on both sides: a cross-site scripting report that requires the attacker to already control code running in your own page, or a report that the local index can be read by someone who has full access to your browser profile, is a real limitation of a browser-local tool rather than a remote vulnerability. It is worth writing down anyway — the security page describes this boundary — but it is handled as a documentation gap, not as an incident.
What we cannot help with
- Recovering an index. If site data was cleared, the browser profile was reset, or the machine was replaced, the chunks and vectors are gone and there is no copy anywhere to restore from. Re-importing the files is the only route back.
- Reading a document for you. There is no server that can open your file, so a “here is my PDF, what does it say” email cannot be answered from this end.
- Account problems. There are no accounts, so there is no password to reset, no profile to delete and no login to unblock.
- Billing questions. There is no payment anywhere in this project, including for the optional generation model, which is downloaded from a public host and costs nothing.
- Guaranteeing an answer’s accuracy. A reply can explain why an answer was produced and which settings change it, but the check against the source document is yours.
Response times
No response time is promised. There is no service level agreement, no support contract, no ticket queue with a clock, no on-call rotation and no business hours; this is one developer and a small number of contributors working on it around other work. Security reports are read first and answers about the pipeline usually take the longest, because a useful reply means reproducing the case rather than guessing at it. If a message goes unanswered, sending it again after a couple of weeks is fine and not rude.
Languages
Write in Chinese or English, the two languages the site is published in. Anything else can be sent, but a reply in the same language cannot be guaranteed. Messages about the Chinese pages can be written in Chinese even when describing English terminology: the interface strings exist in both languages, so quoting the Chinese wording is enough to locate them.
If you would rather not email
Every claim on this site is written to be verifiable without contacting anyone. The about page lists the two-minute checks: watch the network panel while adding a file, go offline and ask a question, look at IndexedDB and Cache Storage, and search the page source for scripts that should not be there. A failed check is the most useful thing you can bring to the mailbox, and it is the only kind of report we can act on without asking you for a document.