We do not upload or store your images
When you choose or drop an image into Normal Map Maker, the file is read directly by browser APIs on your device. The website does not send the file to an application server, cloud storage bucket, image-processing API, content-delivery upload service or third-party AI provider. We do not receive a copy of the source image, and we cannot view, recover or restore it for you.
Generated normal, height, roughness, metallic, ambient occlusion and ORM maps are also created locally. They are not uploaded after generation and are not stored in a project database. Downloads are assembled on your device and delivered through a temporary browser URL. This local-first architecture is a product constraint, not merely a promise in this policy.
- No source-image upload endpoint
- No server-side image processing
- No cloud project library
- No image or generated-map retention
What happens inside the browser
The active tab decodes the selected file and places working pixels in volatile memory. A Web Worker performs texture calculations and encoding away from the main interface thread. Canvas and WebGL display the 2D and 3D previews. These browser resources exist only to operate the tool in the current session; they are not a remote workspace and they do not create a server backup.
Normal Map Maker does not write source-image pixels, generated texture pixels, filenames or parameter values to localStorage, IndexedDB or cookies. The tool may hold temporary data in RAM while a project is open. Replacing the source, reloading the page or closing the tab releases that working session according to the browser's own memory management. Because we keep no project copy, reopening the site starts with an empty workspace.
Downloads and temporary object URLs
When you request a PNG or ZIP, the browser encodes the file locally and creates a short-lived object URL so it can start the download. The object URL refers to data already held by your browser; it is not a public web address and is not accessible from our server. The application revokes that URL shortly after the download begins.
The downloaded file is saved wherever your browser and operating system are configured to save downloads. After that point, storage, backup, synchronization and deletion are controlled by your device, browser profile or organization. Normal Map Maker does not receive notification of the file contents and cannot delete a file from your computer.
No accounts, image history or project database
The current product has no registration, sign-in, user profile or cloud project feature. There is no image history associated with an email address or device identifier. We do not offer a restore button because there is no server-side project state to restore. This also means the tool does not need your name, email address, company name or payment information to process a texture.
If a future version adds optional accounts, cloud projects or server-based features, those features would require a separate, clearly disclosed data flow and an updated privacy policy before launch. Local processing would remain distinguishable from any optional cloud feature. We would not silently change the existing file picker into an upload mechanism.
Analytics boundaries
A deployed version may use privacy-respecting aggregate analytics to understand page traffic, browser performance and broad tool completion events. Acceptable events include a page view, an anonymous indication that the sample was opened, or a count of completed exports. Analytics must not include image pixels, generated files, local filenames, image dimensions linked to an individual, texture parameters or the contents of a ZIP.
We do not use image content for advertising profiles, model training, biometric analysis or dataset creation. We do not sell or license user images because we never receive them. If analytics are enabled, they must be configured as site measurement rather than a mechanism for recreating individual creative activity.
Application assets and network requests
Opening the website requires ordinary network requests for the HTML, JavaScript, styles and other static application assets. Following a guide or an external link also creates the normal request associated with visiting that destination. Those requests are separate from texture processing. Selecting, calculating, previewing and exporting an image should not create an image upload request.
You can verify this behavior with the Network panel in browser developer tools. Clear the request list, choose an image and adjust the controls. The texture operations continue in the tab without a request containing the image file. Browser extensions, security software, managed-device agents and operating-system backup tools are outside the website's control and may have their own data practices.
Security and device responsibility
Local processing reduces exposure to an online image service, but it does not replace device security. Anyone with access to your unlocked computer, downloads folder, screenshots, browser debugging session or synchronized storage may be able to access files that you handle. Use an approved device and browser profile when working with confidential client art or unreleased game assets.
Keep the browser updated, review installed extensions and follow your organization's information-security rules. If policy forbids web tools entirely, local processing does not override that restriction. The privacy claim here is specific: Normal Map Maker itself does not transmit or store the image through its application architecture.
Questions and policy changes
Privacy questions should identify the page or behavior being discussed, but should never include a confidential source image. Because we do not possess user projects, support cannot recover lost files or inspect a failed texture unless you independently choose to share a non-sensitive reproduction through a future support channel.
Material changes to image handling would be reflected in this page before the changed feature is offered. The no-upload and no-storage statements apply to the current local texture workspace. A revision date and contact route can be added when the production domain and support mailbox are configured.