Contact Us
One address, and a straight answer about what to send and how long a reply takes.
Everything reaches the same inbox: [email protected].
There is no contact form, no live chat, and no support ticket system. Adding one would suggest a support desk that does not exist — this is a small independent project, and email is what actually gets read.
Putting the category in the subject line genuinely helps: bug, security, rights, press, or feedback.
What to expect
Messages are usually reviewed within 2-5 business days. Security reports and rights complaints get looked at first. General feedback is read but may not receive an individual reply, and we would rather tell you that than leave you waiting on one. Nobody is on call here, so a message sent on a Friday evening will sit until the following week.
Bug reports
A tool that fails is worth reporting, and a good report is often the difference between a fix and a shrug. Please include:
- Which tool — video, slides, PPTX, infographic, Gemini image, audio, or metadata.
- Your browser and version, and your operating system. Engine behaviour differs meaningfully between Chrome, Safari, and Firefox, and between desktop and mobile.
- The file type and size — for example "a 240 MB 1080p MP4" or "a 38-page PDF". Size matters because a browser tab has a finite memory budget.
- Whether the console showed an error. Open developer tools, select the Console tab, reproduce the problem, and copy anything in red. This is the single most useful thing you can send.
- What you expected and what happened instead — the watermark left behind, a stuck progress bar, a failed download, a mangled output.
Please do not attach the file itself. We do not want it, we have no system built to receive it, and the project's whole premise is that your files never come to us. A screenshot of the affected area, with anything sensitive cropped out, is more than enough.
Before writing, two things are worth a quick check: whether the file is under the size cap (500 MB desktop, 100 MB mobile), and whether an ad blocker or script blocker is preventing the engine libraries from loading. Those two account for most reports.
Security issues
Vulnerabilities and anything about how the client-side code behaves go to the same address, with security in the subject. The security page lists exactly what to include, what falls outside scope, and states plainly that this is not a paid bug bounty. Please read it before you invest time in a report.
Rights and abuse concerns
If you believe this tool has been used against your rights — for example to strip your watermark from work that is being redistributed — send the affected URL or material and a description of the concern. We will respond.
One thing to understand before you write: files are processed inside the visitor's own browser and never reach us. We hold no logs of what anyone processed, no accounts, and no copies. So we cannot identify a user, remove a file, or reverse anything that has already been done. Where the material is hosted on another platform, the effective remedy is with that host, and we will say so rather than imply powers we do not have. The acceptable use policy explains where the line sits.
Privacy questions and data requests
The privacy policy answers most of these, including which third parties receive data and how to opt out of personalised advertising. For anything it does not cover, or a formal data request, email the address above.
An honest note on data requests: with no accounts and no file storage, the answer to "what do you hold about me" is almost always "nothing we can tie to you" — the analytics and advertising identifiers involved are managed by Google, not by us, and the privacy policy links to Google's own controls.
Corrections to the site
If an article, a specification, or a claim on this site is wrong or out of date, tell us. Technical accuracy is the thing this project is judged on, and a correction with a source attached will be acted on. The maintainer page explains who works on this and how articles are researched.
Press and partnerships
Questions about how the engines work, requests for technical detail, or proposals are welcome — put press in the subject line. What is already public may save you a message: about documents each engine in technical detail, and the changelog is a dated record of what has shipped.
Not affiliated with Google
NotebookLM Remover is an independent project, not affiliated with, endorsed by, or sponsored by Google, NotebookLM, Gemini Notebook, or Gemini. We cannot help with a Google account, a NotebookLM subscription, or a Gemini billing issue, and messages about those need to go to Google directly.