Observe a public sample, not a confidential photo
Does a Photo Tool Upload Your File? A Bounded Check
To investigate a photo tool’s upload claim, use a non-sensitive sample and observe the browser’s Network panel before, during, and after selection. Inspect requests and payloads rather than judging request size alone. This gives evidence about one observed session, not a guarantee about future behavior, delayed transfers, or every browser component.
By Qingxin Studio, the developer of HushPic · Updated
Start with a sample you can safely disclose
Choose a public image or a neutral file made specifically for this purpose. Do not use a passport, private screenshot, or a photo containing hidden personal fields. Read the tool’s policy and stated local-versus-server workflow before selecting anything.
Write down the exact URL and behavior you are investigating. File reading, processing, analytics, and downloads are separate operations. A site can retrieve parser code while reading an image locally, or make small requests unrelated to that image; seeing any request is not by itself proof of a photo upload.
Record before selection and keep the full request list
In a desktop browser with Chrome DevTools, open Network and make sure recording is active before selecting the public sample. Start with the All request view, without a filter hiding traffic. Enable Preserve log if navigation is part of the task; Chrome documents this as keeping requests across page loads.
Observe selection, processing, result display, and any explicit save step. Do not resend requests, paste console scripts, disable security controls, or use a private file to make traffic easier to spot. If you missed the start, repeat only with the public sample.
Inspect evidence rather than the size column alone
Select relevant requests and review their destination, method, and available Payload information. Chrome documents how payloads expose query parameters and form data. Identify what you can actually read; if a body is encoded or unclear, mark that request unresolved rather than declaring it harmless.
Consider whether traffic starts on selection, whether it carries the sample or derived content, and whether it is simply loading application resources. File size alone cannot establish what was sent. Do not publish raw network logs casually: unrelated account headers or URL parameters may be private.
State the result as a limited observation
A visible request carrying the sample is evidence of transmission in that session. No recognized upload is not proof of permanent non-transmission: delayed behavior, other paths, or components outside the inspected page can remain unexamined. If you cannot resolve the behavior, choose a workflow you trust instead of testing with sensitive material.
Our photo checker is designed to read supported categories locally without uploading the photo; it does not inspect pixels, remove data, or produce verified copies. HushPic processes supported photos on-device, while purchases and diagnostics may connect without photo contents. These product boundaries are not a third-party security certification or a claim that an entire app never networks.
Sources
This guide is published by Qingxin Studio, the developer of HushPic. Product claims describe our supported workflow, not independent certification. Our review checklists are practical first-party guidance; linked platform sources support only the mechanisms they describe. Automatic checks may miss details. Read our content and corrections policy.