BarcodeSheets

Privacy policy

Last updated: 2026-08-10

1. Site operator

BarcodeSheets.com is operated by TODO_FULL_NAME. For anything in this policy — access, correction, deletion requests, or general privacy questions — contact TODO_EMAIL.

2. The short version

BarcodeSheets is built so that, by default, almost nothing about you or your data reaches us at all: barcode generation, file uploads (CSV/Excel), and label-sheet PDFs are all produced entirely in your browser. The only processing that involves an external party is optional, consent-based analytics, plus the unavoidable technical connection data our hosting provider logs to serve you the page — both explained in detail below.

3. Client-side barcode and file processing

Every barcode you generate — single, bulk from a CSV/Excel file, or a full Avery label-sheet PDF — is rendered locally in your browser using JavaScript/WebAssembly. Files you upload (for bulk or label generation) and the barcode data you type are read and processed on your device only.

No file, spreadsheet, image, or barcode value is ever transmitted to, or stored on, our servers. We have no visibility into, and no record of, what you generate. This applies regardless of your cookie choice below — declining analytics changes nothing about this, and accepting analytics doesn't change it either. The only exception is the entirely optional /api/barcode endpoint, which only ever processes parameters you explicitly put into a URL yourself and copy or request — see its own documentation for details.

4. Cookies and local storage

BarcodeSheets does not set any tracking or advertising cookies. The only browser storage we use ourselves is:

  • bs-consent (localStorage) — records your cookie choice as { analytics: true|false, ts: <timestamp> }, so we don't ask again on every visit. Kept until you change your choice or clear your browser's site data — this value is not shared with anyone.
  • bs-labels-handoff (sessionStorage) — a short-lived, same-tab hand-off used when you send rows into the label-sheet builder (/labels) from either the bulk generator (/bulk) or the SKU generator (/sku-generator). It holds only the barcode data you already entered or generated, exists for the lifetime of that browser tab, is cleared automatically once read, and never leaves your device.
  • bs-bulk-handoff (sessionStorage) — the same kind of short-lived, same-tab hand-off, used only when you send SKUs from the SKU generator (/sku-generator) straight into the bulk generator (/bulk). Same lifetime and cleanup as bs-labels-handoff above — never leaves your device.
  • bs-gs1-notice-dismissed and bs-gs1-notice-shown (both sessionStorage) — remember, for the GS1 licensing notice shown under the preview for EAN-13/UPC-A barcodes, whether you dismissed it (so it doesn't reappear) and whether it's already been shown once this visit (so our analytics don't double-count it if you switch barcode types back and forth). Each holds only the fixed value "1", both are cleared automatically when you close the tab, and neither ever leaves your device.

If you consent to analytics (see next section), Google may set its own cookies to enable that measurement — those are Google's, governed by their own policies, and only ever set after you actively opt in.

5. Analytics (Google Analytics 4)

We use Google Analytics 4 (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland) to understand, in aggregate, which tools and pages are useful — never to identify you individually, and never in connection with any barcode content or uploaded file.

The Google Analytics script is not loaded at all until you click "Accept" in the cookie banner (or enable analytics under "Cookie settings" in the footer) — this is implemented with Google's Consent Mode v2, which defaults every consent signal to denied on page load. Once enabled, we use IP anonymization (anonymize_ip), so your full IP address is never stored by Google Analytics.

This is based on your consent, which you can withdraw at any time via "Cookie settings" in the footer, with effect for the future — withdrawal doesn't affect the lawfulness of processing already carried out based on your earlier consent. Processing may involve a transfer of data to Google LLC in the United States, safeguarded under Google's Standard Contractual Clauses / the EU-U.S. Data Privacy Framework where applicable — see Google's Privacy Policy.

6. Hosting and server log data

This site is hosted on Vercel (Vercel Inc. / Vercel B.V.). Independent of your cookie choice, visiting any page causes your browser to send technical connection data to our hosting infrastructure — IP address, browser type and version, referring page, date/time of the request, and the URL requested — which Vercel processes briefly, in server logs, to deliver the page, keep the service secure, and diagnose abuse or outages. This is standard, unavoidable web-server behavior, not something specific to BarcodeSheets: we do it to operate a reliable, secure website, not to identify visitors individually. See Vercel's Privacy Policy for their retention periods and further detail.

7. Recipients and international transfers

Beyond you and us, the only recipients of any data described above are Google (analytics, only with your consent) and Vercel (hosting, for every visit — unavoidable to serve the site at all). We do not sell data, run advertising, or share anything with data brokers. Both Google and Vercel may process data outside your own country, in particular in the United States; where that happens, it is safeguarded by their respective Standard Contractual Clauses and/or Data Privacy Framework certification.

8. Your privacy rights

Wherever you're located, you can generally ask us to:

  • tell you what data we hold about you;
  • correct data that's inaccurate;
  • delete data we hold about you;
  • restrict or object to how we process it, including analytics;
  • withdraw consent at any time, with no effect on processing already carried out.

Depending on where you're located, laws such as the GDPR, UK GDPR, or CCPA may grant you specific rights along these lines — if any of them apply to you, this policy is intended to honor them, even without citing each one by name. You can also generally lodge a complaint with your local data protection or consumer-protection authority.

Because barcode/file processing never reaches us (§3 above) and we set no tracking cookies without consent, in practice there is usually very little of "your data" on our side to exercise these rights over — but for anything that does apply (e.g. analytics, if you've opted in), contact us at TODO_EMAIL.

9. Changes to this policy

We may update this policy as the site or applicable law changes. The date at the top of this page reflects the last revision; material changes affecting consent-based processing will be reflected in the cookie banner as well.