Privacy Policy

Last updated: November 9, 2026. This policy covers the FullIMEI website (fullimei.com), the FullIMEI Android app and the FullIMEI iPhone app (both com.fullimei.app). All are operated by StandupCRM LLC, 147 Iroquois Rd, Cumberland, RI 02864, USA. The apps are clients for the same service as the website, so the same rules apply to all of them.

No account needed

Every check on FullIMEI is free and works without an account or a sign-in. We do not ask for your name, postal address or phone number to run a check, and we take no payments.

Optional account (Sign in with Google or Apple)

If you choose to, you can sign in on the account page or in the apps: with Google on the website and in both apps, or with Apple in the iPhone app. The only purpose is to save your check history and the devices you choose to save, so you can see them on your other devices. When you sign in, Google or Apple tells us your email address (with Apple, this can be a private relay address), your name if you share it, and an account identifier. We do not receive your Google or Apple password or anything else from that account, and we do not keep a Google or Apple access token.

While you are signed in, each check you run is also saved to your account (the IMEI, the device name and the lock and blacklist results), and checks made earlier from the same browser or app install are added to it. Devices you save keep their IMEI and the name you give them. We keep you signed in with a sign-in cookie on the website (fi_u) or a sign-in token stored in the app; signing out removes it. We do not use your name or email address for advertising and do not send them to any third party for marketing.

You can delete your account at any time: sign in and choose Delete my account on the account page or in the app. That removes your account, every check saved to it and your saved devices, and signs you out.

What we store for each check

When you run a check — on this website or in one of the apps — our server saves one record containing:

• the full IMEI you entered, and a masked copy of it;
• the device details returned for it: brand, model and device name;
• the carrier-lock status and blacklist status returned for it;
• a visitor identifier — a random value created in your browser or by the app on first use, not tied to your name, your advertising ID or your phone's own IMEI. It lets us tell repeat checks apart, limit abuse and link an email address you later give us to your earlier checks;
• your approximate location: country, region and city. This is derived on our servers from the network (IP) address your request arrives from. We do not save the IP address itself in the record. Neither the website nor the app asks for location permission, and we never collect GPS or precise location;
• your email address, only if you choose to give us one (see below).

An IMEI identifies a device, not a person, but we treat the records above as personal data.

Optional email address

An email address is never required to see a result. We do not collect your email address, name or phone number after a check, and we do not pass any contact details to repair shops or other businesses. If you create an account, the email address you sign in with is used only to run that account.

Scanner, photos and the camera permission

The Android app and the iPhone app ask for the camera permission for one purpose: to scan the IMEI barcode on a phone's box or SIM tray so you do not have to type the number. The camera is used only while the scanner screen is open, the barcode is read on the device itself, and camera images never leave your phone — only the IMEI you then check is sent to us. You can decline the permission and type the IMEI instead.

Separately, in the app or on the website you can pick a photo or screenshot that shows an IMEI (for example the *#06# screen). That one image is sent over an encrypted connection to our server and to the text-recognition model run by our hosting provider, Cloudflare, only to read the digits out of it. The image is processed in memory and is never stored by us — it is not written to our database or to any file, and only the IMEI digits found in it are returned to you. The iPhone app first tries to read the barcode or digits in the image on the device itself, and sends the image as described here only if that finds no IMEI.

Who receives the data

To produce a result, the IMEI and your visitor identifier are sent to our IMEI-status service provider, which queries carrier device databases for that IMEI and keeps its own record of the check. Our service runs on Cloudflare, and our check records are kept in a hosted database (Supabase). These providers process the data on our behalf. We do not sell personal data, and we do not share it with advertisers or data brokers.

How we use data

We use check records to return your result, operate and secure the service, prevent abuse, answer support and deletion requests, and produce aggregate usage counts such as the number of checks run. We do not use the data for advertising and we do not use an advertising identifier.

Security

All traffic between your browser or the app and our servers, and between our servers and the providers named above, is encrypted in transit using HTTPS/TLS. The app only talks to fullimei.com over HTTPS.

Push notifications

The Android app can show notifications from FullIMEI, such as service news or tips. On Android 13 and later it asks for permission first; you can turn notifications off at any time in your phone's settings. To deliver them, the app receives a push token from Google's Firebase Cloud Messaging service and sends it to us, together with the app version, your visitor identifier, whether notifications are allowed and the approximate country of your connection. We use these only to send notifications and to count how many installs can receive them. Uninstalling the app makes the token stop working. To have it deleted sooner, email us as described under Retention and deletion.

App usage data and crash reports

The Android app and the iPhone app send us anonymous usage statistics so we can see which features work and fix what breaks: which features and screens are used (for example “a check was started” or “the scanner was opened”), the app version, the device model and the operating system version, crash reports and error details, and performance timings such as how long the app took to start or a screen took to load. Each event is tied only to a random install ID that the app creates when it is first opened — not your advertising ID, your phone's IMEI or serial number, or any account.

These statistics never contain the IMEIs you check, your results, anything you type, your email address or any other personal data. They go to our own analytics service, hosted on Cloudflare; they are not shared with advertisers or other third parties and are not used to track you across apps or websites. We do not store your IP address with them, and we keep them for no longer than 13 months.

You can turn this off at any time in the app's Settings with the switch “Share anonymous usage data”. When it is off, the app sends one last notice that sharing was turned off, deletes the statistics it has not sent yet, and stops sending usage data and crash reports. If you turn it back on, the app starts over with a new random install ID.

Storage on your device, cookies and analytics

The website keeps your visitor identifier and your recent check history in your browser's local storage; the history stays in your browser and you can clear it on the My checks page. The apps keep the same identifier and your recent results on the device; uninstalling the app (or, on Android, clearing its data) removes them. A link you create to share a result contains only a masked IMEI.

The website uses Google Analytics to measure visits and which features are used; Google sets its own cookies for this. Neither app contains an advertising SDK or a third-party analytics SDK; the apps' own usage statistics are described above. The iPhone app reads barcodes and text with Apple's frameworks built into iOS, on the device, and includes no third-party code. The barcode scanner in the Android app is Google's on-device ML Kit library, which can send Google diagnostic and usage metrics about the library itself (never camera images or IMEIs), as described in Google's ML Kit terms. We do not run third-party advertising trackers.

Retention and deletion

We keep check records for as long as they are needed to operate the service and prevent abuse, or until you ask us to delete them. To have your data deleted, email info@standupcrm.com with the IMEI or IMEIs you checked (and the email address you gave us, if any). We will delete the matching check records, including the visitor identifier, location and email stored with them, and ask our IMEI-status service provider to delete its copy. You do not need an account to make this request, and it applies to both the website and the app.

Children

FullIMEI is a general-audience tool and is not directed to children under 13. We do not knowingly collect personal data from children.

Changes and contact

If this policy changes, we will post the new version on this page with a new date. Questions or requests: info@standupcrm.com, or StandupCRM LLC, 147 Iroquois Rd, Cumberland, RI 02864, USA.