CS

Privacy Policy

Effective Date: October 14, 2026 | Last Updated: October 14, 2026

Creative Suite operates on a local, browser-first computing architecture. This Privacy Policy transparently details how files and data are handled during your use of our 20 browser utilities, the technical lifecycle of in-memory assets, network data flows, and our prospective monetization policies.

1. Client-Side File Processing & Memory Lifecycle

The core utility features of Creative Suite (including image resizing, document conversion, PDF merging/splitting, and media compression) execute entirely within your client web browser.

  • Volatile Memory Ingestion: When you select or drag a file into a tool, the file is loaded into your browser's volatile RAM as an in-memory ArrayBuffer or Blob object.
  • Zero File Upload: Your file bytes are never transmitted across a network socket, HTTP POST/PUT request, WebSocket, or remote server API. All parsing and synthesis occur locally via JavaScript, HTML5 Canvas, and WebAssembly.
  • Object URL Cleanup: Downloadable conversion outputs are encapsulated using temporary browser object URLs (URL.createObjectURL). These references are systematically revoked (URL.revokeObjectURL) upon resetting the tool, uploading a new file, or navigating away.
  • Session Clearing: Refreshing or closing your browser tab immediately frees the allocated heap memory and permanently purges processed file data from volatile RAM.

Important Reality: While local in-memory processing prevents cloud data breaches, no software can guarantee absolute device-level privacy against malicious browser extensions, compromised operating systems, or local malware active on your computer.

2. Network Data Flows & Edge Infrastructure Logs

Our application assets (HTML documents, CSS stylesheets, client JavaScript bundles, and WebAssembly binaries) are delivered via static edge hosting infrastructure.

When your browser requests page files from our hosting provider, standard HTTP/HTTPS request headers are received by edge CDN servers. These standard edge access logs may record:

  • Your client IP address (used for geographic routing and rate limiting).
  • Date, time, and requested URL path.
  • Browser user-agent string and referring URL.
  • HTTP response status and transferred byte size.

These diagnostic logs are maintained by the edge hosting provider for network telemetry, DDoS mitigation, and operational security, and never contain the contents of the files you manipulate locally.

3. File Metadata & EXIF Disclosures

Different utilities handle embedded file metadata according to their technical transformation path:

  • Canvas Image Tools: Operations using HTML5 Canvas 2D (such as image compression, cropping, rotation, and photo editing) decode pixel matrices directly. Canvas re-encoding automatically strips camera EXIF tags, GPS location markers, and hardware serial numbers on export.
  • Vector PDF Tools: Direct stream-copying utilities (such as Merge & Split PDF) replicate native PDF page dictionaries without re-rasterizing. Existing document metadata (such as original author or creation timestamp) embedded within source PDFs is preserved in the output file.

We do not guarantee universal EXIF or metadata stripping across all possible file formats and workflows.

4. Cookies, Tracking & Future Advertising

Current State: Creative Suite currently sets zero tracking cookies, uses zero marketing pixels, and executes zero analytics scripts. You can use all core utilities anonymously without creating an account.

Future Advertising Integration: To sustain free access to our utilities, we plan to partner with certified advertising networks (such as Google AdSense) in future releases. When advertising is enabled:

  • A Google-certified Consent Management Platform (CMP) compliant with IAB Europe TCF v2.3 / v2.4 and Google Consent Mode v2 will be presented to visitors from jurisdictions with privacy consent requirements (such as the EU/EEA/UK under GDPR/ePrivacy and California under CPRA).
  • Advertising partners may use cookies or web beacons to serve non-personalized or personalized ads based on consent.
  • Ad network scripts will remain completely isolated from our in-browser file transformation sandboxes. Advertising partners will never have access to your local files or converted content.

5. External Scripts & Localized Workers

To prevent unexpected third-party telemetry, all processing worker scripts (including the PDF.js WebAssembly worker /pdf.worker.min.mjs) are hosted directly on our same-origin static infrastructure. Our HTML to Image tool includes an active sanitizer that strips external HTTP/HTTPS assets and inline scripts to prevent cross-origin tracking and canvas tainting.

6. Data Controller & Inquiries

For questions regarding this Privacy Policy, please contact our designated privacy representative:

Data Controller: [REQUIRES OWNER INPUT: Legal Entity / Developer Name]

Privacy Email: [REQUIRES OWNER INPUT: Privacy Contact Email]

Mailing Address: [REQUIRES OWNER INPUT: Physical / Mailing Address]

You may also reach our team via our Contact page.