Your images never leave your device.
Reshrimp is built with privacy as a core principle, not an afterthought. Here's exactly how it works.
How it works technically
When you select an image, it stays entirely in your browser's memory. Reshrimp uses the HTML5 Canvas API to read, manipulate, and re-encode your image — all within a single browser tab. No data is sent to any server at any point during processing.
The processed image is generated as a Blob URL, which exists only in your browser's memory. When you download it, the file is saved directly from your browser to your disk. When you close the tab, all data is released.
What we don't do
- We don't upload your images anywhere
- We don't use cookies or local storage for tracking
- We don't run analytics scripts (no Google Analytics, no Plausible, nothing)
- We don't require accounts or collect personal information
- We don't make any network requests after the initial page load
- We don't fingerprint your browser or device
Open source verification
Don't take our word for it — read the source code. Reshrimp is fully open source under the MIT license. Every line of code is available for inspection.
The entire image processing pipeline lives in a single TypeScript file. You can audit it in minutes. Check the GitHub repository to verify our claims.
Third-party services
Reshrimp is hosted on GitHub Pages as a static site. The only third-party service involved is the initial page delivery. After the page loads, everything runs locally.
We load Google Fonts (Bricolage Grotesque and Plus Jakarta Sans) for typography. This is the only external request made after page load. No user data is sent with these requests.