Contact
The fastest way to reach the site is by email. Messages are read by a real person and answered as time allows — usually within a few working days.
General contact
Email: [email protected]
What to include
A short, specific message is more likely to get a useful reply than a generic one. Some pointers:
- Bug reports. Describe what you tried, what happened, and what you expected. The browser and browser version help. Please do not attach the PDF that triggered the bug — describe its rough shape instead (single column or two column, scanned or born-digital, approximate page count, presence of a references section).
- Corrections to a guide. Quote the sentence you think is wrong and, if possible, link to a primary source for the correct version.
- Feature requests. Describe the workflow you are trying to support, not only the feature you have in mind. The underlying need is often easier to address than the specific solution.
- Partnership and integration questions. A one-paragraph description of the project and the integration you are imagining is enough to start the conversation.
Privacy and abuse
For privacy questions, data-removal requests, or anything covered by the privacy policy, write to the same address with "Privacy" in the subject line so the message is easy to triage. Reports of abuse or security issues are also welcome and treated as priority.
What this email is not
The address is not a help desk for general PDF questions, a place to send academic papers for hand processing, or a route to obtain extracted metadata for files you cannot open yourself. The tool is designed precisely so visitors can do that work themselves in their own browser.
Response times
Replies are best-effort. During quiet weeks they arrive within a couple of working days. During busier periods, especially around academic deadlines, the queue can stretch longer. Repeat messages on the same thread do not move it up the queue and may slow it down.