Skip to content
Trust and Security

Is TryDocsy Safe?

Yes, TryDocsy is safe. Every tool runs locally in your browser using client-side JavaScript, WebAssembly, and native browser APIs. Your files never upload to a server, are never stored in any database, and cannot be accessed by our team or third parties. You can verify this in your browser Network tab.

Last updated:

How TryDocsy Protects Your Files

Our security model relies on one fundamental principle: when a file never leaves your device, it cannot be leaked, intercepted, or stored.

No upload to servers

Your files are processed on your device. They are never sent to, stored on, or seen by a server.

Works offline

A tool you have loaded once keeps running in airplane mode, proving that processing happens on your device.

Zero file visibility

Because processing is local, the contents of your documents are never visible to our team or third parties.

No account required

No email address, no sign-up form, and no user profile. You can process documents anonymously.

HTTPS and strict CSP

The site is served over encrypted HTTPS with HSTS and an audited Content Security Policy.

Verifiable in DevTools

You can check the Network tab or disconnect from Wi-Fi to confirm zero bytes leave your browser.

Does TryDocsy upload my files?

No. Traditional online converters upload your files to remote cloud servers, process them remotely, and return a download link. While your document sits on external servers, it may be cached or logged. TryDocsy functions differently: our processing code runs inside your browser sandbox using the HTML5 Canvas API, the File API, Web Workers, and WebAssembly.

As a result, your file never makes an upload network request. Here are three straightforward ways to confirm this:

1

Open the Network tab

Press F12 (or right-click and choose Inspect) to open Developer Tools. Click on Network and filter by Fetch/XHR. You will see zero requests containing file contents.

2

Switch to airplane mode

Disconnect from the internet, then compress or convert a document. It continues to process because execution takes place on your device.

3

Watch the address bar

Processing finishes without an upload progress bar, because there is no round-trip communication with a remote cloud server.

Honest Engineering Limitations

What our tools can't do (yet)

Building client-side browser tools means respecting what web standards and browser engines can do. Rather than hiding technical constraints, we state them openly:

Re-renders pages as images (text is no longer selectable)

To reduce file sizes to strict kilobyte targets, our compressor renders each page to a canvas image and recompiles it. This shrinks heavy vector graphics and scanned pages, but text becomes non-selectable. If you need searchable vector text, use desktop vector optimization software.

Covers old text it can't reach, such as text in an embedded form

Edited text is deleted from the page's content stream, in simple and composite fonts alike. Text stored outside that stream, such as inside an embedded form (Form XObject), can't be reached this way: the tool overlays a background patch matching the page color, prints the new text on top, and tells you after download that the original may still be found by search or copy.

Rasterize rendered views into image pages

Both tools convert document layouts into rendered canvas views and compile them into PDF pages. While this produces visually accurate layouts, it creates image-based pages rather than native PDF vector text and active links.

Wraps a high-resolution raster image inside an SVG container

The tool extracts PDF pages as high-resolution bitmap images and embeds them inside an SVG wrapper. It does not parse or convert underlying PDF vector stroke commands into native SVG path vectors.

Safari-only for native client decoding

HEIC photo decoding requires native operating-system codecs present in Apple Safari. Browsers lacking native HEIC support (such as Chrome, Edge, and Firefox without OS extensions) cannot decode HEIC files in client-side JavaScript.

Permission flags rely on the viewer

Print, copy and edit restrictions are permission flags inside the encrypted file. Compliant PDF viewers honor them, but software that ignores the flags can still print or copy a file it can open. Only the open password actually keeps the contents unreadable.

Third-party services we use

TryDocsy relies on standard web infrastructure providers for hosting, contact delivery, analytics, and advertising. The table below discloses what each provider receives and confirms that your document contents are never transmitted:

Third-party service providers, purposes, and data disclosures
ProviderPurposeWhat they receiveWhat they NEVER receivePolicy
NetlifyWebsite hosting, global CDN distribution, and edge routingClient IP address, HTTP headers (user agent), and requested URL pathsDocument contents, file names, or personal filesPrivacy Policy
ResendTransactional delivery of contact form submissions (/api/contact)Name, email address, subject line, and message text submitted via the contact formAny files processed in tools, or documents on your devicePrivacy Policy
ImprovMXEmail forwarding for messages sent to @trydocsy.com support addressesSender email address, recipient address, email subject, and message contentAny files processed on the websitePrivacy Policy
Google Analytics (GA4)Anonymous website usage measurement and tool adoption trendsAnonymous page views, device category, and anonymous tool event tags (tool name, file extension, coarse size bucket)Document contents, document text, file names, or user identitiesPrivacy Policy
Google AdSenseContextual and display advertising to support free hostingStandard advertising cookies, IP address, and browser metadata per Google advertising standardsFiles, file names, or document textPrivacy Policy

TryDocsy vs. typical upload-based tools

The fundamental difference between private tools and server-based converters is where the processing occurs. Here is how TryDocsy compares to traditional online utilities:

Comparison of TryDocsy and typical upload-based online tools across privacy and usage features
FeatureTryDocsyTypical online tool
Where your file is processedIn your browser, on your deviceUploaded to their remote server
Does the file leave your device?No: zero upload bytesYes: every single time
Server-side file retentionNone: files never touch a serverTemporary server cache (retention varies)
Account or email requiredNo sign-up or email neededFrequently required for full features
Works without internet connectionYes, for tools previously loadedNo: requires active connection
Watermarks or daily limitsNone: unlimited free conversionsCommon limits on free tiers

What data do we collect?

We never collect, read, or store the contents of your files. That is technically impossible in our architecture because your documents remain on your device. We use Google Analytics to count page views and anonymous tool events: which tool ran, the file extension, and a coarse size category. That measures tool adoption without exposing file names or document text. The site displays Google AdSense ads, and Google may set cookies to serve them (see our privacy policy to opt out). There is no account registration, no email requirement, and no user tracking profile created from your files.

On the transport level, the entire site is delivered over encrypted HTTPS with HSTS and secured with a strict Content Security Policy, ensuring resources only load from verified domains. For additional legal terms, read our Privacy Policy and our Editorial Policy.

Try a private tool now

Every tool runs locally in your browser. Open any tool and inspect the Network tab to verify zero uploads:

Frequently Asked Questions

Is TryDocsy safe to use?

Yes. TryDocsy is safe because every tool runs entirely inside your web browser using client-side code. Your files are read, converted, and downloaded on your own device. They are never uploaded to, stored on, or seen by any server. There is no account to create, and no document leaves your computer or phone.

Does TryDocsy upload my files to a server?

No. Unlike conventional document websites, TryDocsy never uploads your files. All processing occurs locally with browser APIs: the HTML5 Canvas API, the File API, Web Workers, and WebAssembly. You can verify this directly: open your browser Network tab before running a tool, or switch your device to airplane mode. The tool continues to work because your file is never transmitted across the network.

What data does TryDocsy collect?

TryDocsy never receives, reads, or stores your files. Google Analytics records page views and anonymous tool event tags (the tool name, the file extension, and a coarse size bucket), never file names or document contents. The site displays Google AdSense ads, and Google may set cookies to serve them; our privacy policy explains how to opt out. We do not require an email, account, or login.

Can I use TryDocsy offline?

Yes, for tools you have already used while online. Because tools run in your browser, the service worker caches the pages and tool code your browser has fetched, so a tool you have loaded continues to work without an active internet connection. OCR language data downloads the first time you run OCR, and background removal loads its neural network weights from staticimgly.com on first use. Working offline is practical proof that nothing is uploaded: a tool that required an external server could not function in airplane mode.

Is it safe to compress or merge confidential PDFs on TryDocsy?

Yes. Confidential contracts, identity documents, bank statements, and personal records are safe to process on TryDocsy because they never leave your device. There is no server upload pipeline where files could be intercepted, cached, or exposed.

How is TryDocsy different from typical online tools?

Most free document sites upload your file to remote cloud instances, process it on their servers, and send a download link back. During that transfer, your document temporarily lives on a remote computer you do not control. TryDocsy runs the code directly in your browser, keeping the document with you the entire time. There is no upload, no remote copy, and no data retention.

Why is TryDocsy free if files are processed privately?

Client-side processing is more affordable to operate because we do not pay for heavy cloud server infrastructure to process documents: your own computer or phone handles the work. That allows us to offer tools for free, with no watermarks, no daily task limits, and no subscriptions. Tools enforce local file-size caps (such as 20 MB for images and 100 MB for PDFs) to keep browser memory stable.

Related reading