Random IMEI privacy policy
Last updated: August 5, 2026
Random IMEI is an independent test-data utility maintained by the Random IMEI Editorial Team. This policy describes the data flows in the generator, validator, optional browser history, analytics, advertising and email contact workflow.
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.
2. Browser storage
The optional History panel stores generated results in your browser's local storage. 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. Security and preference storage is treated as necessary. Google Consent Mode v2 sets analytics and advertising storage, ad user data and ad personalization to denied before Google tags load; only the certified consent platform may update those signals.
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.
Error monitoring
To keep the site reliable, we use Sentry, an error-monitoring service, to receive a sanitized report when browser code fails. A report may contain the error category, code location, page path without query parameters or fragments, site domain, and deployment version.
Before transmission, our code removes error messages, tool inputs and outputs, form values, user details, cookies, headers, request bodies, interaction history, and stack-frame variables. Session replay, performance tracing, logs, and metrics are disabled. Sentry necessarily receives connection data such as an IP address when accepting the report and processes it as our service provider. Read Sentry's privacy notice.
4. Google Analytics, Tag Manager and AdSense
Google Tag Manager can load after a short delay, but Consent Mode starts with analytics and advertising consent denied. Google Analytics and advertising behavior must follow the consent signals supplied by the certified consent platform and the choices available in your region.
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 other directory 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. 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.
6. 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.
7. 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.
8. 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.