Privacy Policy & Trust Disclosure

1. What We Process

Privacy Photo Studio is designed for preparing official passport photos, visa photos, document signatures, and print sheets. In using these tools, the following artifacts exist temporarily in your client device's memory:

• Uploaded Photographs: Digital image files (JPEG, PNG, WebP) selected from your device.
• Signatures: Scanned or photographed signatures for cropping and background cleaning.
• Derived Outputs: Scaled bitmaps, cropped portraits, annotated copies, and generated printable PDF documents.

These items reside strictly within your web browser's volatile working memory (RAM, HTML5 Canvas elements, and Web Worker buffers). The application does not transmit your images to application servers.

2. How Image Processing Works

Our image-processing architecture operates entirely on a client-side execution model:

1. File Ingestion: When you select a photo, your browser reads the file bytes locally. The ingestion engine verifies format signatures and decodes pixels onto an in-memory canvas.
2. Spatial Transformations: Cropping, zooming, aspect ratio adjustments, and 90° discrete rotations are computed locally in the browser.
3. Optional Enhancements: Background adjustments, text strip annotations, and target-size compressions are calculated on your device CPU/GPU.
4. Local Export & Download: When you click "Download", your browser creates a temporary local object URL from in-memory bytes and saves the file directly to your device's Downloads folder.

3. Background Removal & AI Model Downloads

When you use the optional "Make Background White" or standalone "Background Remover" capabilities, the platform employs the open-source client-side library @imgly/background-removal (v1.7.0).

It is important to understand the technical distinction between model asset downloads and image uploads:

4. File Compression, Conversion & Annotations

All supplementary utility operations are performed locally:

• Photo Compressor: Bounded binary search algorithms test encoding quality directly on in-memory canvases to reach target file sizes (e.g. 20 KB, 50 KB, 100 KB) without uploading.
• Signature Resizer: Contrast thresholding and bounding-box auto-cropping operate directly on canvas pixel arrays.
• Name & Date Annotations: Text strips are rendered onto new derived canvases while keeping your original uploaded file unmodified.
• Photo Converter: Dimensional resizing (mm, inches, pixels) and DPI recalculations execute natively using HTML5 Canvas.

5. Generated Print Sheets & PDFs

Multi-photo print layouts (A4, 4×6 inch, 5×7 inch) are computed mathematically in your browser to maintain physical millimeter precision. PDF documents are assembled locally using the pdf-lib JavaScript library. Generated PDF binary streams are saved directly to your local file system without server transit.

6. Data We Receive: Application vs. Infrastructure

To maintain technical truth and transparency, we clearly separate application-level behavior from hosting-level infrastructure behavior:

Standard HTTP transport logs are generated automatically by web server and CDN infrastructure to deliver web assets and protect against denial-of-service attacks. The application does not control infrastructure log retention schedules.

7. Third-Party Services & Dependencies

We maintain an extremely conservative dependency footprint:

We do not load third-party advertising SDKs, session recording trackers, social media widgets, or invasive user tracking scripts.

8. Cookies & Browser Storage

• Cookies: We use zero cookies (no tracking cookies, no session cookies, no advertising cookies).
• Local Storage: We use browser localStorage solely to remember your preferred visual theme (theme: 'light' or theme: 'dark') across visits. No image data, session tokens, or personal identifiers are stored.
• Session Storage / IndexedDB: Not used by this application.

9. Data Retention

Application Data: The application does not intentionally upload or persist uploaded photos, signatures, or documents on its application servers. In-memory canvases and object URLs are volatile and are released when you close or refresh the browser tab.

Telemetry Metrics: If product analytics is enabled in production, minimal aggregated event metrics sent to the configured external HTTPS endpoint are retained according to the receiving infrastructure's automated rolling retention policy (e.g. 30 days) and contain zero personal identifiers or image data.

Infrastructure Logs: Web server and CDN access logs are managed according to the hosting provider's standard security and retention policies.

10. User Controls & Rights

Because we do not require accounts, store user profiles, or maintain a database of uploaded photographs, there are no stored user records to access, rectify, or delete.

You retain complete control over your files on your local device:

• You can clear all session memory at any time by closing or refreshing your browser tab.
• You can remove your theme preference by clearing your browser's local storage.
• You control where exported photos and PDFs are saved on your computer or mobile device.
• Do Not Track (DNT): If your browser sends a Do Not Track header or signal (navigator.doNotTrack === '1'), all aggregate product telemetry is automatically disabled.

11. Contact Regarding Privacy

If you have questions, feedback, or concerns regarding our privacy practices or technical architecture, please contact us: