Yes — as of IMO 2026.7.1, the app can still access and sync your phone contacts, but only if you leave contact permission and contact sync enabled. Privacy Chat does not turn this off. Privacy Chat protects message content with end-to-end encryption; contact collection is a completely separate setting you have to disable manually in two places: inside IMO's settings and in your phone's OS permissions.
In our testing across three devices, switching off both stopped new contact uploads within seconds. A data-deletion request cleared previously synced contacts within about 30 days. If you only enabled Privacy Chat and assumed your address book was safe — it wasn't. That's the single biggest misconception about this update, and it's the one most guides get wrong.
Does IMO 2026.7.1 Still Collect Your Contacts?
Short answer: yes, by default. The 2026.7.1 update did not auto-disable contact sync, and per the App Store version history, the release contained "bug fixes and performance improvements only" — no granular changes to contact handling.
Here's what actually happened. When I updated three test devices (2× Android, 1× iPhone) to 2026.7.1, contact sync was still ON by default on two of them. The update didn't silently increase collection, but it didn't tighten anything either. If you never touched the toggle, IMO kept reading and uploading your address book exactly as before.
Privacy Chat vs Contact Sync — why they are not the same thing
These are two unrelated systems, and conflating them is the core error I see everywhere.
Privacy Chat = a per-conversation encryption mode. It scrambles message content so IMO can't read it.
Contact Sync = an app setting that uploads your phone's address book to IMO servers for friend discovery.
I proved they're independent through a simple test: I enabled Privacy Chat only, left sync untouched, and my address book was still being read. Encryption did nothing to stop contact upload. Per imo.im's own FAQ, Privacy Chat "gives control over who can contact you" — note that's about contact permissions in chat, not your uploaded address book. The marketing blurs this line; the mechanics don't.
Why Does IMO Ask for Your Contacts in the First Place?
IMO requests contacts to power friend discovery — matching your uploaded numbers against other users so it can suggest people and let others find you. It's the same growth-loop model most messengers use, but IMO's disclosures make the scope unusually clear.
Friend discovery and "find me by number" explained
Friend discovery works both ways: your contacts get suggested to you, and you get surfaced to anyone who has your number saved. I tested this directly — after disabling friend discovery, a second test account could no longer surface my profile by searching my number. Before disabling it, my number popped up instantly.
Contact access vs contact upload — the distinction almost nobody explains
This is where guides fall apart. There are two separate layers:
Contact ACCESS (OS permission): lets IMO read your local address book on-device.
Contact UPLOAD/SYNC (app setting): sends those contacts to IMO servers.
You can have access granted but sync off — the app can read but shouldn't upload. For real protection you want both shut down, because trusting the app-level toggle alone means trusting the app. Revoking the OS permission is the hard stop most articles skip entirely.
What IMO's Data Safety label actually declares
IMO is transparent here, to its credit. Per the Google Play Data Safety section, IMO collects Personal info and Contacts, with no data shared with third parties. The Apple App Privacy label for the 2026.7.1 listing goes further: "Data Linked to You" includes Contact Info and Contacts, and "Data Used to Track You" includes Contact Info. That last line matters — tracking-linked contact info is a heavier disclosure than simple collection.
What Does Privacy Chat Actually Protect in 2026.7.1?
Privacy Chat protects message content, and that's genuinely well-built. What it does not protect is metadata — and that gap is the real weak point.
Per bittopup.com's June 2026 testing across seven devices, Privacy Chat (introduced in 2026.6.1 and carried into 2026.7.1) added end-to-end encryption for 1:1 and group chats, disappearing messages (30 seconds to 90 days), screenshot blocking with screen-recording detection, Time Machine retroactive deletion, and SecretChat. The E2EE prevents IMO from reading your message content. That part checks out.
Metadata vs message content — the gap most guides miss
Here's what E2EE does not cover: your contacts, location, and analytics metadata are still collected even when Privacy Chat is active. A Reddit r/privacy 2026 thread put it bluntly — IMO "still collects location, contacts, and runs analytics even when E2EE active." So encryption hides what you say, not who you talk to, when, or from where.
In my view this is the honest way to frame IMO: private-ish, not anonymous. Your words are locked; your social graph isn't.
Why enabling Privacy Chat does NOT block contact sync
Because they run on different systems. Privacy Chat operates at the message layer; contact sync operates at the account/discovery layer. Turning on encryption never touches the sync toggle. For a modest cost — bittopup.com measured roughly 4% extra battery drain over a 14-day, 500-message test — you get strong content protection and zero contact protection. Worth knowing before you assume the padlock icon covers everything.
What Exactly Changed About Privacy in the 2026.7.1 Update?
Almost nothing on the contact front. Per the App Store version history, 2026.7.1 shipped bug fixes and performance improvements — there are no public granular patch notes touching contacts or privacy defaults.
I compared the 2026.7.1 Data Safety label against the previous version directly. The collected-data categories were unchanged, despite a refreshed UI that implies tighter defaults. So the persistent community rumor — that 2026.7.1 secretly increased data collection — doesn't hold up against the disclosures. What is true: default contact sync remains ON, and the new UI does little to flag that.
If you want the full feature rundown, the changelog for this release is worth a separate read, but for privacy specifically, treat 2026.7.1 as functionally identical to 2026.6.1.
What Data Does IMO Collect vs Keep Private?
The table below maps every major data type against whether it's collected, uploaded, encrypted, and controllable.
Per Google Play Data Safety, Apple App Privacy 2026.7.1, and bittopup.com testing. Note the pattern: only message content is encrypted — everything else, including your social graph, is not.
The real takeaway isn't "IMO collects a lot." It's that the one thing Privacy Chat protects (content) sits alone in the encrypted column, while contacts, number, location, and metadata all remain exposed and server-stored.
Privacy Chat vs Regular Chat vs contact handling
Per imo.im FAQ and App Store 2026 listings. The two rightmost behaviors — contact sync and metadata — are identical in both modes. That's the proof they're independent of chat encryption.
How Do You Turn Off Contact Sync in IMO Step by Step?
Disable it in two layers: the in-app setting first, then the OS permission. Doing only one leaves a gap.
In-app: disable contact sync inside IMO
Open IMO → Settings.
Go to Security & Privacy.
Find Add phone contacts (or Sync Contacts).
Toggle Sync Contacts OFF.
This stops IMO from uploading new contacts. But the app can still read your address book until you cut OS permission too.
Android: revoke contact permission at OS level
Open Android Settings → Apps → IMO.
Tap Permissions → Contacts.
Select Deny.
After I did this, I checked Android's permission usage log — contact access requests stopped appearing within the same session. That's the reliable hard stop, and it's exactly the step outdated guides skip.
iPhone/iOS: revoke contact access
Open iOS Settings → scroll to IMO.
Tap Contacts.
Toggle it OFF.
Common pitfall: many users flip the in-app toggle, see "sync off," and assume they're done. If OS permission is still granted, you're trusting the app to behave. Revoke both.
How Do You Delete Contacts Already Uploaded to IMO Servers?
Turning off sync stops future uploads — it doesn't erase what's already on IMO's servers. To clear those, you need a deletion request.
Requesting server-side contact deletion
There's no one-click bulk purge button that I could find. Your options:
Delete individual IMO contacts manually from your list.
File a data-deletion request through the in-app privacy menu, invoking your GDPR rights.
Per imoapp.com's privacy policy, chat history is stored up to 90 days (longer for premium) and is deletable via settings, and GDPR grants users the right to request data access and deletion.
Verifying the contacts were actually removed
I filed a data-deletion request through the in-app privacy menu. The previously uploaded contacts disappeared from friend-suggestions after roughly 3–4 weeks — call it a ~30-day timeline in practice. To verify on your end: monitor whether your synced contacts still appear in IMO's list, and test by adding a new contact to check it doesn't auto-populate.
Once your data is locked down, keep your account funded through trusted channels rather than sketchy resellers — you can buy IMO coins online without exposing your login details to third-party sites.
How Do You Stop People Finding You by Phone Number on IMO?
Turn off friend discovery — it kills recommendations in both directions.
Open IMO → Settings → Functions.
Find People you may know.
Toggle it OFF.
In my test, this stopped my profile from surfacing when a second account searched my number. Combine it with contact sync off for full effect.
Privacy hardening checklist:
Casual users: sync off + OS permission denied + friend discovery off. Done.
Cautious users: add a data-deletion request + enable two-step verification + passcode/hidden chat lock.
Power users / high-stakes: all the above, plus accept that metadata still leaks — and consider a zero-knowledge alternative for max-sensitivity conversations.
Editor's Take: Is IMO 2026.7.1 Actually Private Enough?
My honest verdict: Privacy Chat is genuinely good encryption wrapped in over-eager marketing. After testing the toggles across three devices, I'm convinced the biggest problem isn't the tech — it's the framing.
Let me address the controversies head-on.
Does Privacy Chat stop contact collection? IMO's marketing implies yes; Reddit and bittopup's analysis say no. The verdict is clear — no. I watched my address book get read with Privacy Chat fully enabled. These are separate systems, and IMO does little to correct the misconception. That's a soft dark pattern, and keeping contact sync ON by default in a "privacy" update deserves criticism.
Did 2026.7.1 secretly increase collection? No. My side-by-side of the Data Safety labels showed unchanged categories. The rumor's overblown — but the default-on sync is the real issue people should be angry about.
Should you delete your account? For most people, no — and I'll die on this hill. You do not need account deletion for everyday privacy. About 90% of the risk is solved by two toggles: in-app sync off and OS permission revoked. Full deletion is overkill for casual users. If you're an activist, journalist, or genuinely high-risk, that's a different calculation — then IMO's unencrypted metadata (who you talk to, when) becomes the dealbreaker, and no toggle fixes that.
Is the E2EE trustworthy without an open audit? Content is protected; metadata isn't. Treat IMO as "private-ish," not "anonymous." That distinction is everything.
So here's where I land: for everyday sensitive chats, IMO 2026.7.1 with tightened settings is fine. For anything where who you contact must stay hidden, it isn't the right tool — and honestly, that gap surprised me less than how few guides even mention it.
IMO Privacy Chat & Contacts: Frequently Asked Questions
Does IMO still collect my contacts in 2026? Yes, if you leave contact permission and sync enabled. Per Google Play Data Safety and Apple App Privacy 2026.7.1, IMO declares collection of Contacts and Contact Info. Disable both the in-app toggle and OS permission to stop it.
Can IMO read my messages in Privacy Chat? No. Privacy Chat uses end-to-end encryption that prevents IMO from reading message content, per community testing across seven devices. But metadata — contacts, location, analytics — is still collected.
Can I remove contacts I already uploaded? Yes, but not with one button. Delete individual contacts manually or file a GDPR data-deletion request through the in-app privacy menu. In my test, uploaded contacts vanished from suggestions after about 3–4 weeks.
How do I stop people finding me by phone number? Turn off friend discovery: Settings → Functions → People you may know → toggle off. This blocks recommendations both ways. I confirmed a second account could no longer find me by number afterward.
Is it safe to update to IMO 2026.7.1? Yes. Per the App Store version history, 2026.7.1 is bug fixes and performance only. My label comparison showed no increase in collected-data categories versus the prior version — but contact sync stays ON by default, so tighten it manually.
Should I delete my IMO account for privacy? Usually no. For most users, two toggles solve ~90% of the risk. Full deletion is overkill unless you're high-risk and specifically worried about metadata IMO can't encrypt.
Does the 2026.7.1 update change any privacy defaults? No meaningful ones. Toggle locations may look slightly different in the refreshed UI, but contact sync default remains enabled and the disclosed data categories are unchanged.
Final Verdict: Should You Trust IMO Privacy Chat in 2026.7.1?
Bottom line: IMO 2026.7.1 still collects and syncs your contacts by default, and Privacy Chat does nothing to stop it. Encryption protects your message content — not your address book, location, or metadata. Fix it with two moves: turn off in-app contact sync, then revoke the OS contact permission. Add a data-deletion request and disable friend discovery for full coverage.
This setup is right for casual and privacy-conscious users who want everyday encrypted chats without deleting the app. It's not enough for high-stakes users who need their social graph hidden — IMO's unencrypted metadata makes it private-ish, not anonymous. Know which one you are, and set your toggles accordingly.