How ImgShield handles local checks, optional enhanced detection, account data, feedback, and cookie choices.
Local checks first
Text checks run in the browser. Image checks start locally; when a local image result is uncertain, the current file may be sent through ImgShield's same-origin backend to Sightengine for an additional pixel-model signal. API keys are not exposed to the browser.
Accounts, feedback, and payments
We process the account information needed for sign-in, feedback details needed to respond or prevent abuse, and payment or entitlement records needed to provide a selected plan. Payment credentials are handled by the hosted payment provider, not stored by ImgShield.
Cookies and choices
Necessary cookies support sign-in and security. Analytics loads only after consent. You can decline analytics cookies and continue using the detector; use the cookie controls on this site to change your choice.