100% Client-Side In-Browser Processing
All utilities execute entirely in your local browser memory via HTML5 Canvas and typed arrays. No user files are uploaded to any server.
Zero Logs & Zero File Storage
We do not run storage buckets, databases, or logging pipelines for your images. Closing the browser tab automatically wipes all temporary buffers.
1. Local In-Memory File Processing
Pixora operates entirely within your browser client environment. When you drop or select image files, they are decoded and processed exclusively in your device’s local memory (RAM) using HTML5 Canvas, TypedArrays, and Web APIs. Your images are never streamed, uploaded, or transmitted across the network to our servers or any third-party infrastructure.
2. Zero External Network Requests & Analytics
Our image processing tools make zero outbound API calls. Pixora contains no third-party tracking analytics (such as Google Analytics or Meta Pixel) and no session recording scripts. Every inspection, compression, and edit cycle completes locally without transmitting telemetry.
3. Zero Cookie Architecture
Pixora is fundamentally cookie-free. We do not set, read, or inspect advertising cookies, tracking tokens, or persistent session identifiers.
4. Browser Local Storage Transparency
Pixora uses browser localStorage strictly to preserve your UI preferences locally. We never store personal identity information:
- app_lang: Selected interface language (ar or en).
- app_theme: Visual theme preference (light or dark).
- lifetime_bytes_saved: Estimated cumulative bytes saved by local compression for the savings widget.
- lifetime_images_compressed: Total count of locally processed images to update your personal savings counter.
5. GPS Geolocation & EXIF Handling
In the EXIF Privacy Cleaner, binary metadata segments (such as APP1) are excised directly from the file header without pixel recompression. In the EXIF Inspector, headers are parsed in memory to display camera telemetry and map links to you alone. GPS coordinates and camera serial numbers are never cached, recorded, or transmitted.
6. Self-Hosted Fonts & Asset Privacy
To prevent IP address telemetry, all IBM Plex typography files are hosted directly within the application domain. Pixora makes zero requests to Google Fonts or foreign CDN servers.
7. Browser Sandbox & Hardware Limitations
Because computation runs locally on your client hardware, file capacity and batch throughput are bounded by your browser tab’s available memory allocation (typically 2GB–4GB on modern engines). Processing exceptionally massive resolutions or hundreds of images in a single batch may cause temporary slowdowns or tab crashes if system memory is exhausted. We recommend batches of 20 to 50 images for peak stability.
8. Outbound External Links
Our site contains links to the developer’s social channels, the 3BQRIINO parent site, and an optional InstaPay tip link. Following external links takes you to third-party services governed by their respective privacy policies.