Your content stays with you.

Local processing

Core detection, validation, generation, rendering and export happen in your browser. This includes guided GS1 building and verification, spreadsheet parsing, scanning, label PDFs and printer-calibration correction. anyscan.download does not intentionally transmit the values you enter or attach code contents to advertising or analytics requests.

Scanned images and camera frames

Uploaded, dropped or pasted PNG, JPEG, WebP, GIF, AVIF, BMP, SVG, HEIC/HEIF and TIFF files are decoded locally. HEIC/HEIF and TIFF use application code and WebAssembly served as anyscan.download static assets and run in an in-browser Worker; the selected image is not sent to a decoding service. SVG files with scripts, linked resources or other active content are rejected before rendering. Camera video is sampled in memory and is neither recorded nor uploaded.

Ordinary site requests

Your browser still requests the site’s HTML, scripts, styles, icons and offline files from anyscan.download. As with an ordinary website visit, the hosting provider may receive technical request metadata such as your IP address, browser information, requested page and request time. The generator does not place your entered values in those request URLs or bodies.

Advertising

On eligible anyscan.download tool pages, one labelled, responsive manual advertisement may appear after the page’s explanatory publisher content. It is included only when the site build is configured with an ADSENSE_SLOT_ID. When configured, the eligible page loads Google’s AdSense script and the manual ad unit. The default build, with no slot configured, contains no AdSense script or ad unit and makes no AdSense ad request.

When advertising is enabled, third-party vendors, including Google, may use cookies, web beacons, IP addresses or other identifiers to serve and measure ads. Google’s use of advertising cookies enables Google and its partners to serve ads based on your prior visits to anyscan.download, other websites, or both. Other third-party ad vendors or networks made available through AdSense may also use cookies or similar technologies where they are enabled.

Advertising providers may receive ordinary web and ad-request metadata, such as your IP address, browser information, page address, and cookie or consent signals, depending on browser, provider, consent and account settings. anyscan.download does not intentionally attach your code contents, scanned values, Wi-Fi details or spreadsheet data to ad requests. Those payloads remain in your browser. Blocking ad requests does not disable the core tools.

You can control or opt out of personalized advertising in Google Ads Settings. You can also review how Google uses data from sites that use its services, Google’s Privacy Policy, and the current Google ad technology providers. Other vendors’ privacy and opt-out choices are available from their own websites.

Privacy, Terms, not-found and other error pages do not include AdSense code. anyscan.download’s supported advertising setup uses the controlled manual placement described above; account-level Auto Ads must be disabled before that placement is enabled. anyscan.download does not implement custom consent logic in the application. Before ads are enabled, the site operator must publish and test an applicable Google-certified consent solution, such as Google Privacy & messaging, and provide a way to revisit privacy and cookie choices where required. This Privacy page remains free of ad tags and consent-message tags. The technical description here is not a claim that one particular legal regime applies or has been satisfied.

Aggregate analytics

Cloudflare may automatically add its Web Analytics performance beacon at the hosting edge. It measures page views and browser performance; anyscan.download does not attach generator input, decoded values, Wi-Fi details, email addresses, phone numbers or spreadsheet contents to it. Cloudflare states that this beacon does not use cookies or browser storage, does not fingerprint visitors, and discards the source IP address at the nearest Cloudflare data center. See Cloudflare’s RUM beacon privacy information.

Any future application-level analytics must likewise be limited to content-free events, such as a page view, selected format, export type or broad batch-size range. Payloads must never be attached to those events.

Storage on your device

Theme, preferred Create mode and format, and settings-only presets may be stored in localStorage. A Labels preset may include printer-calibration measurements. Code values, GS1 fields, spreadsheet rows, labels and decoded content are deliberately excluded from those presets. Offline support caches the app’s static files, not the values entered into the generator.

When you choose Labels while a non-Wi-Fi code is on screen, or send a mapped batch to Labels, the site may temporarily place that value and its label, format, quantity or filename metadata in this tab’s sessionStorage so it survives the navigation. Nothing is written until you make that choice; a code you type and then abandon is never stored. The destination removes the entry when it reads it; the browser also clears session data when the tab session ends. Wi-Fi payloads are never written to this handoff storage. Files you download and images you copy are handled by your browser and operating system.

No account required

Core anyscan.download functionality does not require an account. Advertising and hosting providers may process ordinary request metadata under their own privacy policies.