Privacy Policy

Public user-manual document pages use Google AdSense to support FCCID.io. Google and its advertising partners may use cookies and similar technologies to deliver and measure ads, including personalized ads where permitted by your choices. See how Google uses information from sites that use its services.

Where applicable, Google displays a consent message on those pages. You can revisit your choices using the privacy and cookie settings link provided with that message. In supported US states, use the Do Not Sell or Share My Personal Information link on the advertising page to open Google's opt-out message.

You can also manage personalized advertising through Google My Ad Center. Blocking Google scripts or cookies may prevent its privacy controls from loading. Contact info@fccid.net if you need help accessing these controls.

The IMEI / TAC lookup accepts a 14-digit IMEI base or a complete 15-digit IMEI. For a 14-digit base it calculates and appends the Luhn check digit; for a complete IMEI it validates the supplied check digit. A visitor may explicitly place either form in a /TAC/ URL; that URL is served in place and its canonical link points to the TAC-only page.

After a visitor completes the CAPTCHA and explicitly requests additional device details, FCCID.io transiently sends the completed IMEI to third-party device compatibility services. Their own privacy terms apply to that transmission. A TAC-only submission does not make these requests. A detail-page refresh prefers a validated IMEI found in indexed FCC evidence and otherwise uses a generated, structurally valid representative IMEI for the TAC.

FCCID.io stores only normalized TAC-level device and compatibility observations, an opaque short-lived job token, and endpoint health counters. It does not store the complete IMEI, and it discards serial-specific blacklist fields rather than publishing or retaining them. Stored observations omit null-like values and combine duplicate values without publicly identifying the compatibility service.

IMEI URL, lookup, and progress responses are marked no-store and noindex, use a no-referrer policy, and contain no advertising or other third-party scripts. FCCID.io does not write the complete IMEI to its application database, analytics events, application logs, or origin access log. The result displays the IMEI and equivalent formats only to the requester so the validation can be understood.

Because an IMEI or 14-digit IMEI base may be part of a visitor-chosen URL, it may still be retained outside FCCID.io by the visitor's browser, network intermediary, DNS or security service, or the CDN that delivers the request. CAPTCHA-protected IMEI submissions continue to the full IMEI validation page, which is private and canonicalized to its TAC-only page. TAC-only detail pages contain device-type data and do not contain an individual device serial number.