Profile: Mantu Kumar ยท Updated
About me
I'm Mantu Kumar, and I build and run LyfPDF from Mumbai, India. I work on the tools, the guides and the fixes you see on this site. LyfPDF is built around one rule: your files are processed in your own browser, not uploaded to a server. If a tool breaks or a guide is wrong, email me at hello@lyfpdf.com.
How I review tools and guides
- Confirm that the described tool and controls exist in the current build.
- Compare the page claim with the actual processing path and known technical limits.
- Run a representative input/output check where practical.
- State material limitations, including rasterization, OCR uncertainty, visual signatures and device memory.
- Review canonical URLs, internal links, structured data and visible dates when a page materially changes.
What I check for each content type
Tool pages are checked against the controls and processing path in the current build. Instructions distinguish visible annotations from source-text editing, drawn signatures from certificate-backed digital signatures, and rasterized output from pages that preserve selectable text. Privacy statements are tied to the browser workflow that is actually implemented, not a generic promise.
Learning guides are organized around a real PDF task, its limits and a verification step. Every guide should link to its parent topic, useful related explanations and the relevant working tool. Comparison content describes selection criteria and trade-offs; it does not invent scores, customer counts or vendor claims.
Safety-sensitive pages covering redaction, metadata, confidential sharing and protected PDFs get an extra limitations pass. They explain what the browser tool changes, what it does not remove, why you should keep the original and when a qualified legal, compliance or records professional may be needed.
Testing standard
For a material tool update, I use representative files and check the downloaded output separately from the on-screen preview. Typical checks include page count, page order, orientation, text selectability, image quality, file size and whether an annotation or redaction survives reopening. Browser and device limits are stated when memory, permissions, extensions or download behavior can affect a result.
What I do not claim
LyfPDF does not publish invented customer numbers, professional qualifications, guaranteed results or claims that every PDF will convert perfectly. The guidance here is educational and task-focused; it is not legal, compliance, medical, financial or archival advice.
Corrections and contact
If a guide is unclear or a tool behaves differently from its description, send the page URL, your browser/device and a short description to hello@lyfpdf.com or use the contact page. Please do not email confidential documents. A factual, safety or workflow correction is made on the page and shown with a new reviewed date. If the evidence is incomplete, the wording is narrowed rather than presenting an assumption as fact.
What I maintain
The PDF Learning Center, the tool workflows, the FAQ, privacy explanations and tool-specific help. I also maintain the help content for the Worksheet Generator, including the Worksheet Generator guide and the shape tracing worksheet guide; class levels there are editable practice suggestions, not curriculum approval. File-processing boundaries and legal limits are explained in About LyfPDF, the Privacy Policy and the Disclaimer.