Your images.
Your device.

01 / SCOPE

What this policy covers

This policy describes the Image Studio website and its browser tools for compression, resizing, descriptions, rights metadata and publishing code. It covers the implementation currently included in this project.

Image Studio does not provide user accounts, cloud image storage, a public gallery or a payment flow. You do not need to provide a name or email address to process an image. The optional creator and copyright fields describe the image; they are not account registration fields.

The Terms of Use explain your responsibility for the images and rights information you choose to publish. Using the separate command-line tool runs on the computer where you execute it; browser storage details below concern the website.

02 / YOUR WORKSPACE

Images & the details you enter

When you select or drop a file, the browser reads its contents, decodes the image and creates a local preview. Compression, resizing and output checks run on your device using the browser image engine. Batch files are processed sequentially.

Image Payloads (0 Bytes Uploaded): the processing workflow does not send your selected images, filenames, pixels or embedded metadata to an image-processing server. The included example image is fetched from this website only when you choose to load the example.

Images & filenames

Used to make previews, calculate dimensions and file sizes, and name your exports.

Alt text & image URLs

Used to generate your publishing HTML and structured data. Typing an image URL does not fetch that remote image.

Creator & rights

Used for supported publication metadata and your publishing report. These fields are optional.

Quality & dimensions

Used locally to configure the encoder and measure the result.

These values remain in the active workspace unless you copy, download or publish them yourself. There is no server-side image library for the tool to retrieve later.

03 / EMBEDDED INFORMATION

Metadata can be personal.

Source files can contain creator names, copyright statements, camera details and location information. The tool reads supported image information locally. Its default publication mode reconstructs supported descriptive and rights fields in the output; it does not promise to preserve every original metadata field.

Choose Remove embedded metadata in the image settings to export without the publication metadata. This also removes embedded creator and copyright information from that output. Original files are not rewritten.

Alt text belongs in the HTML for your website. Removing embedded metadata does not erase text you separately copy into HTML or a publishing report. For a batch, review the shared rights option before applying one creator or license to multiple files.

04 / WHAT YOU TAKE WITH YOU

Downloads, reports & clipboard

Image downloads and batch ZIP archives are assembled locally. Batch exports can include image files, individual reports and a manifest containing filenames, measurements and supplied publishing information. A separate publishing report can include the final URL, alt text, creator and license links.

Pressing Copy code asks the browser to write the displayed publishing code to your clipboard. The tool does not monitor your clipboard. Tag text pasted into a field is read only as part of that paste action.

After a download, the file is managed by your browser and operating system. Cloud-synced download folders, clipboard syncing, device backups and any website where you paste the code have their own handling of that data. Image Studio cannot erase those copies.

Adding a final image URL prepares code for you to publish. It does not upload an image to that URL or deploy changes to your website.

05 / YOUR BROWSER

Cookies & browser storage

Tracking Cookies (Zero Cookies): the current application code does not set cookies and includes no third-party analytics, advertising pixels, session replay or fingerprinting library.

The workspace currently does not write your images, descriptions or quality settings to localStorage, sessionStorage or IndexedDB. Reloading the page resets the working session. There is no service worker saving your image files for later use.

Your browser may cache ordinary website assets such as scripts, styles, illustrations and the locally hosted Manrope font. Locally Hosted Fonts (Zero CDN Calls): the font is served from this website, without a request to Google Fonts or another font provider.

Browser caching of the website is different from storing the images you selected. Clearing site data or the browser cache can remove cached website assets; downloaded files must be managed separately.

06 / WEBSITE DELIVERY

Static Hosting Logs Transparency

Your browser must request the website's HTML, CSS, JavaScript, fonts and illustrations from the host to open the tool. These normal requests expose connection information to the hosting provider, even though image processing is local.

Depending on the deployed host and its settings, operational logs may include an IP address, requested URL, timestamp, browser user agent, referrer and response status. Hosting retention periods and access controls depend on that deployment; this project does not establish a fixed server-log retention period.

The browser workspace has no image upload API or remote processing queue. Local processing does not prevent a hosting provider from logging ordinary visits to the website.

07 / CLEARING YOUR WORK

Data Retention and Erasure

Your selected images, decoded previews, current settings and generated results are held for the active browser session. The application releases temporary image URLs when replacing images or results and on page unload. Exact memory reclamation is controlled by the browser.

Reload or close the page to end the working session. There is no cloud image history or saved workspace to delete from this application. Your original source files remain where you selected them.

This does not delete downloads, copied text, browser session recovery data, device backups or copies you shared elsewhere. On a shared device, clear downloaded exports and your clipboard when you finish. Hosting logs and support messages follow separate handling, described in this policy.

08 / PRACTICAL SAFETY

Local processing & device security

Keeping file processing in the browser reduces the need to transmit images to a remote processor. It does not protect against an untrusted browser extension, a compromised device, screen recording or someone with access to your downloads.

For sensitive work, use a trusted browser and device, keep them updated, and check the address before opening files. A deployed site should be accessed over HTTPS. Browser memory and image limits can cause large or malformed files to fail; the Help page describes supported formats and limits.

Privacy controls and metadata choices are separate from the publishing readiness indicator. That indicator measures completion of five workspace checks; it is not a privacy certification or a guarantee about an exported image.

09 / CONTACTING SUPPORT

Messages you choose to send

The Contact page opens your email application. There is no built-in support form or automatic upload of your workspace. Sending email shares the message, sender details and any attachments through your email provider and the recipient's mail system.

Start a bug report with the browser version, image format, approximate dimensions and visible error message. Avoid sending private originals, license documents or screenshots containing personal details unless they are needed. A public repository issue is visible to other people; remove personal information before posting.

A support conversation can contain information you voluntarily provide. The browser tool's session-only behavior does not automatically delete an email or a public issue. Ask about the specific conversation through the same contact channel.

10 / LEAVING THE SITE

External links & publishing

Guides and help pages link to independent documentation, standards and open-source projects. Opening an external link connects you to that website, which has its own privacy practices.

License URLs and final image URLs you include in an export can become public when you publish the generated code or image. Make sure they are intended for publication. Your own website, hosting platform and any services it uses control what happens after you upload or embed the result.

11 / YOUR CONTROLS

Decide what to keep & share.

• Use the tool without an account. Start with a file or the included example.
• Leave optional identity fields blank. Only add creator and rights information you intend to include.
• Choose the metadata mode. Review the tradeoff between retaining publication credits and stripping embedded data.
• Review every export. Check the visible image, filename, report and publishing code.
• End your session. Reload or close the page, and manage downloads and copied text on your device.
• Ask about information you sent. Use the Contact page for questions about a support conversation or the website.

Any rights relating to information processed by a deployed website depend on the applicable law and the operator's circumstances. This local tool cannot identify or delete a host's logs solely from an image file, because image contents are not used to identify a visitor.

12 / KEEPING THIS ACCURATE

Updates & privacy questions

Last updated: November 5, 2026. If the application adds accounts, analytics, remote processing or persistent workspace storage, this policy needs to change with that behavior. Read this page again after substantial product updates.

For questions about how the current tool handles data, use the Contact page. Describe the feature or request you are asking about without attaching private images by default.