I’m working on a web app where users can upload documents and view them online. Right now we convert everything to PDF first and show it in an iframe but this is really slow. Users get frustrated waiting for documents to load.
We’re thinking about switching to Google Drive Viewer API to make things faster. But I’m worried about privacy issues. If we use Google’s viewer service, could our private files become public somehow? Is there any risk that documents we display through their API might show up in Google search results later?
Has anyone used this service before? What are the main security risks I should know about when letting Google handle our document viewing?
honestly we’ve been using it for about 6 months now and havent had any major issues. sure, google processes the files but they dont store them permanently - at least thats what their docs say. the speed improvement is worth it imo, our users love how fast everything loads now compared to the old pdf conversion mess. just dont use it for super confidential stuff if your paranoid about google seeing it.
We evaluated Google Drive Viewer last year for a client portal and decided against it after consulting with our legal team. The biggest issue wasn’t about public indexing but rather data residency and control. When you use their viewer API, you’re essentially uploading documents to Google’s infrastructure, even if temporarily. This created problems for us because we handle healthcare data that needs to stay within specific geographic boundaries. Another thing to consider is the potential for service interruptions - we experienced several outages during our testing period where documents simply wouldn’t load, leaving users unable to access their files. The performance gains are real though, so it might work for your use case if privacy isn’t paramount. You could also look into client-side solutions like PDF.js or implement a hybrid approach where users can choose between fast Google viewing or slower private viewing based on document sensitivity.
I implemented Google Drive Viewer in production about two years ago and can share some real experience with it. The documents you send to Google’s viewer service don’t get indexed by their search engine - they’re processed temporarily for viewing purposes only. However, there’s still a privacy trade-off you need to consider. The main concern isn’t about documents becoming publicly searchable, but rather that Google does process your files on their servers during the viewing session. For highly sensitive documents, this might violate certain compliance requirements depending on your industry. We ended up using it for general business documents but kept financial and legal files on our slower internal system. Performance-wise, it’s definitely faster than converting to PDF first. The viewer handles most document formats natively and loads much quicker. Just make sure you’re comfortable with Google’s data processing terms and consider implementing user consent for document viewing if privacy is critical to your users.