Find likely matches
Identify repeated people and properties without relying on a single name or phone-number comparison.
Find likely duplicates across your address books, compare their sources and properties, and approve the result before anything is merged or written back.
For anyone seeing the same person two, five, or hundreds of times after years of syncing, importing, or changing phones.

One record may contain the current phone number while another holds a work email, postal address, birthday, or note. Cloud Contacts groups likely matches and keeps the source visible so cleanup begins with review instead of deletion.
Identify repeated people and properties without relying on a single name or phone-number comparison.
See whether each record belongs to Apple Contacts, Google Contacts, Outlook, CardDAV, JMAP, or another connected account.
Review names, phones, email addresses, notes, dates, and other fields before approving a repair or merge.
Choose the address books you want to inspect and let the app prepare manageable groups of likely duplicates.
Compare ownership and field-level differences. Remove only the redundant information you no longer need.
Fix locally or write back when the provider and your plan support it. Long operations continue in the background.
Cleanup should not be a black box. Cloud Contacts emphasizes source ownership, preview, visible progress, and recoverability.
The proposed result is available for review before destructive changes are applied.
Available write operations depend on the connected provider, protocol, and account permissions.
Candidates are processed in bounded batches rather than holding every possible comparison in memory.
The app can identify and prepare likely duplicate groups, but the safer workflow is to review the proposed result and approve the change you want.
Yes. The same person may exist in Apple Contacts, Google Contacts, Outlook, CardDAV, JMAP, or several accounts at once. Source ownership remains visible during review.
The merge review is designed to retain useful non-redundant properties. Exact writable fields depend on the destination provider.