The short answer
Inspect the current account’s import and device-access state, then decide separately about stored imported contacts. LinkedIn’s older contact definition says legacy syncing ended, while its newer mobile-import help describes a gradual feature that may import periodically. Preserve that difference; do not promise one universal sync switch or deletion of first-degree connections.
What you’ll take away
- Device permission, stored imported contacts and LinkedIn connections are different states.
- Read the actual removal scope before confirming Remove all.
- A lingering suggestion is not a full deletion audit.
Identify the actual source and desired outcome
Is the goal to stop a phone address book being shared, remove previously imported copies or keep a reflection list small? Those are different tasks. Start with the intended account and device, current permission and available import control. Do not upload an address book merely to see whether the feature is enabled.
Keep first-degree relationships, followed members, saved profiles and imported address-book entries separate. The official connections export is a different artifact. Removing imported copies should not be described as disconnecting everyone or recalling a previously downloaded archive, and revoking device access should not be recorded as deletion of stored server data.
Resolve the primary-help mismatch honestly
The older Definition of a contact page says previously synced sources stopped syncing. The newer mobile-import page describes a gradual feature, an initial upload and possible periodic imports, with full or selected-contact access. Both were read directly on 1 November 2026. An old retirement notice cannot establish that every current mobile account lacks import access.
Inspect the actual mobile permission and feature without enabling them unnecessarily. Record unavailable controls as unavailable in that account/version, rather than a global platform fact. Device access and provider-side imported copies require separate review. Do not invent a specific operating-system menu or assume a change on one phone applies to another device.
Review the stored-contact removal separately
The removal help uses Settings & Privacy, Account preferences, Syncing options, Sync contacts and Remove all beside Contacts, followed by its confirmation. Read the confirmation’s scope before any intentional action. Keep the current imported-contact state and relevant source context in a private note if the decision requires it; no extra copy is needed by default.
The source says deletion is immediate but suggestion changes may take up to 72 hours. Preserve the actual removal response and later observation separately. A lingering suggestion can have a different basis and is not proof that a particular imported record remains. Likewise, one empty screen is not an independent audit of every stored copy or backup.
Resolve three contact-state problems
C1 — Constructed device boundary: a member revokes phone contact access but previously imported entries remain in the account view. Decision: keep device permission and stored-copy removal as separate checks. Result: no contradiction and no claim that revocation alone erased the imported records; no real contacts were accessed.
C2 — Constructed help conflict: an old page says syncing ended, but the actual mobile app offers selective contact import. Decision: record the current account/version and newer feature branch without running an upload. Result: availability observed or left unknown, not a global claim that periodic collection is impossible.
C3 — Constructed removal follow-up: an intentional Remove all confirmation is followed by a familiar suggestion. Decision: preserve removal evidence, note the help’s suggestion delay and avoid importing again to test it. Result: suggestion provenance remains unknown; neither failed deletion nor successful removal of every connection is inferred.
Keep the useful relationship work minimal
For a recap, the useful output may be a few verified contributions, not a copy of every address. Find the original relevant feedback and decide separately about public credit. A stored contact, suggested connection or available email does not establish permission for a message or a customer relationship.
If a private archive already exists, review its storage and need separately under your own retention practice. Do not place real contacts in this public worksheet or upload them to an unrelated tool to prove removal. A public exercise can demonstrate scope using fictional states without copying a single address.
Record device, source and stored-copy states
The worksheet records account/device context without credentials, actual feature availability, device permission, stored-import state, intended removal and observed response. Keep suggestions and first-degree connections in separate fields. An unobserved control or timed-out action remains unresolved rather than being silently retried.
No address book, account export, contact permission, imported entry or connection was read or changed for this guide. Sources were checked on 1 November 2026 and all cases are constructed. This is a scoped review method, not a legal compliance certificate, deletion guarantee or outcome study.
Sources & product references
Product details reflect the publication date. External features and interfaces may change.
