Data handling

Know where the image goes before pressing Run.

Current browser tools read supported files locally. A workspace that needs remote processing must disclose that fact before a transfer begins.

Browser-first tools

The browser File API reads selected files into memory. Canvas, WebAssembly or bundled JavaScript libraries perform the requested operation. Current browser-tool scripts do not submit source pixels, filenames or generated files to ImgNimble.

Temporary files

Public browser tools do not require server uploads. The application includes protected temporary directories and an hourly cleanup command so any future secure processing workflow can enforce a documented deletion window. The relevant tool page must state the processing method and retention period before upload.

Accounts and contact requests

Member records contain an email address, password hash, plan state and usage allowances. Contact messages are stored so the team can respond. Tool input is not placed in URLs, analytics events or ordinary usage logs.

Downloads

Generated downloads are assembled in the browser. Closing the tab clears in-memory results. Downloaded copies remain wherever the browser saves them, which is outside ImgNimble’s control.