Last reviewed 2026-06-06Free public siteNo saved classification workspace

Privacy policy.

NACE.codes is a free public reference site. We keep the service focused on public NACE reference data and only use limited technical logs needed to operate, secure, and improve the site.

Source library Privacy JSON

Public data scope

Public API access is protected with rate limits and scoped keys where needed. NACE.codes only uses lookup, export, and API activity needed to operate the reference site.

Retention scope

How public lookup, export, and API activity is handled.

Current retention covers reference cache, source metadata, and technical logs used for reliability and abuse prevention. NACE.codes does not save your classification work.

CSV and XLSX imports are used only to read code lists for conversion. Uploaded files are not saved.

Current deletion scope

What users can expect from the simplified public site.

- NACE.codes does not save your classification work.

- Uploaded conversion files are not saved.

- Browser users can clear local browser history, cookies, and cached pages.

Data handling map

Public reference data, lookup activity, conversion uploads, and API logs are handled separately.

Public reference data

Official NACE codes, source documents, public mappings, source metadata

Public, cached, and versioned with source attribution.

Lookup and conversion activity

search terms, requested code pages, conversion inputs, download requests

Used to return the requested page, result, file, or API response. Conversion uploads are not stored.

API and search logs

request IDs, API key environment, rate-limit events, requested endpoint

Used for reliability, abuse prevention, and rate-limit enforcement.

Security controls

Current controls are focused on public browsing, scoped API access, rate limiting, and safe file conversion.

Authentication

Required only for scoped API access where stricter limits or protected endpoints are needed.

Role-based access control

Public readers and scoped API callers stay separated.

Public data boundary

Public readers and API callers receive reference data, not private workspaces or saved user decisions.

API rate limiting

Per-key and anonymous endpoint-level limits protect public APIs.

Encryption

Traffic uses encryption in transit.

What is not saved

How the simplified public site treats visitor activity.

API and security logs are retained only as needed for reliability and abuse prevention.

Public reference records remain versioned so pages and API responses can be reproduced.

Loading NACE reference