Glossary

Key terms used throughout the DeviceAssure documentation.

TAC (Type Allocation Code): The first 8 digits of an IMEI number, assigned by the GSMA. The TAC identifies the device make and model. DeviceAssure uses the TAC to cross-reference a device's claimed identity against the GSMA's global device database.
IMEI (International Mobile Equipment Identity): A unique 15-digit number assigned to every mobile device. The first 8 digits form the TAC. DeviceAssure can optionally verify an IMEI against the GSMA Block List to check if a device has been reported stolen.
GSMA (Global System for Mobile Communications Association): The international trade body representing mobile network operators and related companies. The GSMA maintains the global TAC database and the Device Check / Block List service used by DeviceAssure for IMEI verification.
Client-Hints: A set of HTTP request headers that allow a browser to share device and browser information with a web server. Chromium-based browsers (Chrome, Edge, Opera) support client-hints, which provide more detailed device identification data. Client-hints require a secure context (HTTPS) to function.
Client to Server (C2S): An integration method where the DeviceAssure library collects device data and sends it directly to the DeviceAssure API for validation. Results are returned to the client application. See How It Works.
Server to Server (S2S): An integration method where the DeviceAssure library collects device data, but your own server sends it to the DeviceAssure API for validation. Results are returned to your server. See How It Works.
PII (Personally Identifiable Information): Data that can identify a specific individual, such as name, email address, or phone number. DeviceAssure libraries do not collect PII.
Callback URL: A URL configured on your licence that receives a copy of every validation result. This allows you to aggregate results for analysis or feed them into a separate service.
Secure Context: A browser environment where certain security-sensitive features are available - typically when the page is served over HTTPS. Client-hints and some other browser APIs used by DeviceAssure require a secure context.
Licence Key: A unique key provided by DeviceAtlas that authenticates your requests to the DeviceAssure service. Required for all validation requests, with usage quotas configured per licence.