Random IMEI privacy policy

1. Generator and validator data

Generator selections and the requested batch size are sent to the Random IMEI server. The server creates a batch, places it in the current Symfony session for the one redirect needed to display the result, and removes that payload when it is read. The application does not intentionally write generated batches to a database.

IMEI validation calculations run in your browser. The validator checks normalization, length, digit content and the Luhn checksum; it does not send the entered IMEI to a Random IMEI validation API, include or query a TAC-to-model catalog, or contact GSMA, a carrier, a manufacturer or a blocklist.

QA lab files

The QA lab runs CSV parsing and validation in your browser. Selecting a CSV file reads it locally; the lab does not upload its contents to the server. When you choose “Check this batch in the QA lab” on a generator result, the browser temporarily puts the CSV in session storage to carry it to the lab. The lab removes that stored copy when it reads it; closing the tab also ends that browser storage session. The downloadable example also runs locally and makes no registry lookups. This does not remove the page-level analytics, hosting and security processing described below.

2. Browser storage

The History panel automatically stores up to 20 generated batches in your browser's local storage when results are displayed. You can clear that history from the panel. The site also stores your color-theme preference locally so it persists between visits. Clearing site data in your browser removes these values.

Symfony may use a session cookie to keep a generator request linked to its one-time result. The site sets functionality and security storage signals to granted. Before Google tags load, Google Consent Mode v2 sets analytics storage, advertising storage, ad user data and ad personalization to denied in the European Economic Area, the United Kingdom and Switzerland. Outside those regions, the current defaults for those four signals are granted. The consent platform can update the signals following the choices it presents.

3. Hosting and security logs

The web server and hosting infrastructure may process request information such as IP address, timestamp, requested URL, user agent, response status and security events. This information is used to deliver the site, diagnose failures and protect it from abuse. Retention depends on operational and security needs; Random IMEI does not claim a fixed deletion period that it cannot independently verify.

4. Google Analytics, Tag Manager and AdSense

Google Tag Manager can load after a short delay. The initial analytics and advertising signals depend on region as described above; they are not denied globally. Google tags read those signals and any updates supplied by the consent platform. A denied storage signal is not a promise that no network requests occur: Google may use requests without cookies for measurement where its configuration permits.

Content-rich pages may include the Google AdSense tag. Google can process device, network and page-view information to provide, limit, secure and measure advertising, and may use cookies or similar storage where permitted. Legal, contact, sitemap and cheat-sheet index pages, device guides and one-time generator result pages do not load the AdSense tag. Learn how Google uses information from publisher sites in Google's partner-sites notice.

Random IMEI uses Google's certified consent platform, with a consent message published for randomimei.com through Google Privacy & messaging. Advertising remains subject to the choices shown in that message and to applicable regional requirements.

5. RandomIMEI app for Android and iOS

The RandomIMEI app generates, validates and decodes IMEIs on your device. It has no account and no analytics SDK. Generated batches, validation input, bulk-check lists and saved IMEIs are processed on the device and are not sent to Random IMEI. Saved entries (the IMEI, its optional label and note, the catalog label and the creation time), display preferences and the product identifier of an active Pro subscription are kept in the app's storage on your device. You can delete saved entries one by one or all at once in the app; deleting the app removes its local data.

The free version shows ads served by Google AdMob through the Google Mobile Ads SDK. Google states that the SDK collects and shares, for advertising, analytics and fraud prevention:

• the IP address, which may be used to estimate the device's general location;
• app interactions such as app launches, taps and video views, and information about the ads shown;
• diagnostic information such as crash logs, app launch time, hang rate and energy usage; and
• device identifiers: on Android the advertising ID and app set ID, and on iOS the advertising identifier (IDFA, only if you allow tracking) or identifiers limited to the developer's apps.

Google says this data is encrypted in transit. See Google's Google Play data disclosure and App Store data disclosure for the SDK's current details, and how Google uses information in Google's partner-sites notice.

Where required, the app uses Google's User Messaging Platform (UMP) to ask for your consent choices before requesting ads, and shows a “Privacy choices” entry in Settings when you need a way to change them. On iOS, the app asks for permission through Apple's App Tracking Transparency prompt before the advertising identifier can be used; if you decline, ads are still shown without it. You can reset or delete the Android advertising ID in Android's settings, and change tracking permission in iOS Settings at any time. Non-personalised and limited ads can still use data such as the IP address to deliver an ad and prevent fraud. An active Pro subscription removes all ads from the app.

Pro subscriptions are sold, renewed, restored and cancelled through Google Play Billing or the Apple App Store, which process your store account, purchase and payment information under their own terms. Random IMEI does not receive payment details and does not send purchase receipts to a Random IMEI server.

On launch, the app makes a best-effort request to randomimei.com/api/app-version to learn whether an important update is available. The request carries only the platform name; it contains no IMEI, saved data or advertising identifier, but the hosting and security providers receive standard request metadata such as the IP address, as described in section 3. Links that you open from the app (the website, this policy, support email) leave the app.

The app is a utility for adults and developers and is not directed at children under 13.

6. Contact messages

The contact form opens your own email application using a mailto: link; it does not submit the form to a Random IMEI web endpoint. If you send an email, your email provider and ours process the address, headers and message content needed to deliver and answer it. Correspondence is kept only as needed to respond, maintain support history, prevent abuse or meet legal obligations.

7. Sharing and international processing

Random IMEI does not sell personal information. Data may be processed by infrastructure and service providers needed to host, secure, measure or monetize the site, including Google when its services are enabled. Those providers may process data in countries other than yours under their own legal safeguards and policies.

8. Your choices and rights

You can use the certified consent message when it is presented, clear local history and site data, block cookies in your browser, or contact us about personal data contained in support correspondence. Depending on your location, you may also have rights to access, correct, delete, restrict or object to processing and to complain to a data-protection authority.

9. Contact and changes

Privacy questions and requests can be sent to support@randomimei.com. Material changes will update the revision date shown at the top of this page.