# Review contact imports without confusing them with connections

Original constructed teaching cases, not real accounts, participants or customers.

## Case 1

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.

## Case 2

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.

## Case 3

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.