Cookies

1. What cookies are

A cookie is a small text file a site can ask the browser to store and send back on later requests. Related technologies include local storage, session storage, IndexedDB, pixels, and fingerprinting scripts. Romanian Law 506/2004 and the EU ePrivacy Directive require information — and, for non-essential cookies, consent — before such storage is used.

2. What this application does not do

The File Conversion JavaScript, HTML, and headers do not:

• Call `document.cookie` or send a `Set-Cookie` header from application code.
• Write files, filenames, previews, or identifiers to `localStorage`, `sessionStorage`, or IndexedDB.
• Load analytics, advertising, tag-manager, session-replay, or social pixels.
• Register a service worker that caches user files.
• Use a cookie consent manager, because there is nothing non-essential to consent to.

Conversion state exists only in memory for the current page session. Reset, navigation, or closing the tab drops it.

3. Browser HTTP cache of static assets

Your browser may cache same-origin HTML, CSS, JavaScript, fonts, workers, and images that we published (logo, Open Graph image, icons). That is ordinary HTTP caching of the website, not storage of your photos. HTML is served with `Cache-Control: public, max-age=0, must-revalidate`. Fingerprinted static assets may be cached longer. You can clear cached files in your browser settings.

4. Object URLs and workers (not cookies)

Previews and downloads use `blob:` object URLs. Conversion may run in a same-origin web worker. Those mechanisms keep bytes in the page’s memory. They are revoked or terminated on cleanup. They are not cookies and they are not sent to the operator.

5. Hosting platform

The static artifact is served by Netlify. Application configuration does not enable Netlify Analytics, Identity, or Forms on this site. The operator does not instruct the host to set advertising or analytics cookies.

If a network path, corporate proxy, or platform feature outside this application’s code stores a strictly technical cookie, that storage is not written or read by File Conversion scripts. Connection logs (IP address, user-agent, requested URL) may still be processed to deliver the site, as described in the Privacy policy. That is not a File Conversion cookie.

6. Third-party cookies

Tool routes load only bundled same-origin assets. They do not embed third-party frames that set cookies. The footer link to alexjungean.com opens a different site, which may use its own cookies and scripts (including a contact form). That site is not File Conversion.

7. How you can control cookies

You can block or delete cookies in your browser. Doing so does not change File Conversion’s application behaviour, because the application does not rely on cookies. Blocking all site data may still affect ordinary caching or TLS. Browser vendors document their controls in their own help pages.

8. Changes

If a future release ever sets a cookie or uses local storage, this page will be updated before that behaviour ships, and a consent mechanism will be added if the storage is not strictly necessary. Analytics and upload products are currently prohibited.

9. Contact

Questions: alex.jungean@gmail.com. See also Privacy and Legal notice.