[ STUDIO ]IMAGE // TOOLS
[ LEGAL ]•[ PRIVACY POLICY ]•[ ZERO-DISK DATA PRIVACY ]

PRIVACY POLICY

LAST UPDATED: NOVEMBER 2026 // EFFECTIVE IMMEDIATELY

[ 01: ZERO DISK STORAGE & ZERO IMAGE RETENTION ]

At Image Studio, privacy is an architectural guarantee rather than an afterthought. When you compress, convert, or remove the background of an image, all processing occurs strictly inside volatile RAM memory buffers (via Python's io.BytesIO).

Your uploaded images, converted files, and processed graphics are NEVER saved, cached, written, or retained on any hard drive or persistent disk storage. Once the streaming response completes and delivers your file back to your browser, all image bytes are immediately released and wiped from volatile system memory.

[ 02: ANONYMOUS OPERATIONAL TELEMETRY ]

To protect our infrastructure against distributed Denial of Service (DDoS) attacks, automated scraping abuse, and excessive resource exhaustion, our backend records minimal, non-identifying operational audit logs into an isolated database table:

  • Client IP address (collected for real-time abuse mitigation and rate-limiting)
  • User-Agent string (to identify device class and browser engine)
  • Action type performed (e.g., compress, convert, remove-bg)
  • File format and byte sizes (e.g., original size, processed size, compression ratio)
  • Processing time duration in milliseconds
  • Timestamp of execution

This telemetry data is stored securely in an isolated PostgreSQL instance, is strictly decoupled from any identity records, and is never sold, shared, or matched with personal profiles.

[ 03: ZERO COOKIES & ZERO CROSS-SITE TRACKING ]

Image Studio does not place third-party advertising cookies, browser fingerprinting scripts, or behavioral analytics trackers on your machine. We do not participate in cross-site ad networks.

Any temporary state stored in your browser (such as images queued between the Converter and Compressor) is managed entirely via your local client-side IndexedDB storage, which never leaves your local browser sandbox.

[ 04: COMPLIANCE & SECURITY CONTACT ]

Our infrastructure follows industry best practices for transport layer security (TLS 1.3 encryption for all network transfers) and automatic container recycling. For questions, audits, or data privacy requests, you may contact our engineering team via the repository channels.