Data handling
Know where the image goes before pressing Run.
ImgNimble separates browser-local work, signed VPS jobs and paid provider jobs so the processing boundary is visible before transfer.
Last updated 3 October 2026.
Browser-local tools
The browser File API, Canvas and bundled JavaScript libraries perform the operation in the tab. Source pixels and generated downloads are not intentionally submitted to ImgNimble by these tools.
VPS worker tools
CPU-heavy jobs are stored in a private job directory, validated by MIME/extension/size rules and sent through an HMAC-signed worker request. Results are returned through an expiring signed URL. The supplied hourly cleanup removes worker job directories after the configured retention period.
Paid provider tools
Generative requests require PLUS access, moderation and an explicitly configured provider. Temporary provider input links are signed and short-lived. Provider keys are never exposed to browser JavaScript.
Accounts, analytics and URLs
Member records hold account and credit state. Tool source contents are not placed in URLs. Google Analytics 4 measures visits with Consent Mode v2: it is off by default in the EEA, the UK and Switzerland, and on elsewhere unless you choose “Necessary only”. Advertising cookies need your consent.
Downloads
Browser outputs are created locally. Worker/provider outputs use private expiring result links. Once a user downloads a copy, the browser’s saved file is outside ImgNimble’s control.