Privacy Policy

Last updated: September 26, 2026

Overview

ContactLogo ("we", "our", or "us") matches business contacts to public brand marks so your address book shows a logo instead of grey initials. This policy covers the web app at contactlogo.com, the iOS app, the macOS app, and the Android app.

Imported vCards and CSVs are reviewed in the browser. Google Contacts import reads contacts from Google when you choose it; selected-photo sync sends approved updates back to Google. Logo requests use business domains and can reach external image services.

On-device processing

Matching happens locally. Company names, emails, websites, and phone numbers are scored on the device or in this browser tab.
No address-book uploads to ContactLogo. We do not operate a server that stores contacts, phone numbers, notes, or photos.
Nothing is written without you. A logo reaches a contact only after you review and approve it.

What we do not collect

ContactLogo does not create accounts. We do not store your address book, and we do not sell contact data. Closing the web tab leaves the imported book behind in that session only.

Logo lookups

To find a mark, the app may request a public image using only a sanitized business domain (for example fedex.com), never a person's name, email, or phone. Depending on the surface and your settings, those lookups can reach:

Simple Icons (cdn.simpleicons.org)
The ticker-logos GitHub pack (raw.githubusercontent.com)
Brandfetch and Logo.dev, only when you (or a build) supply a key
Clearbit Logo (logo.clearbit.com)
Google Favicon (t1.gstatic.com)
DuckDuckGo icons (icons.duckduckgo.com)
Wikimedia Commons, on native Apple apps
Official company domains, when you paste an image URL

The first-party logo cache and external image services can receive the business domain and standard request metadata (such as IP address and user agent). ContactLogo does not send the imported address-book file as a logo request.

Google Contacts

If you tap Import Google Contacts or Apply to Google Contacts, the browser talks to Google using OAuth. Scopes cover reading your Google Contacts and, when you choose write-back, updating contact photos you approved. Google is the processor for that data. ContactLogo never sees the OAuth refresh token on a ContactLogo server, because there is no ContactLogo account server.

Optional crash and performance telemetry

When public keys are configured for a build:

The web app may send Datadog RUM and browser logs (page views, resource timing, and errors). Interaction tracking that would derive names from image alt text is off. Session Replay is off.
The web app may send exception envelopes to Sentry if a Sentry DSN is configured at build time.
The iOS app may send crash reports and app-hang traces to Sentry. Screenshots, view hierarchy, and default PII are off.

If those keys are absent, telemetry stays dark. Telemetry payloads are not supposed to include contact display names, emails, phone numbers, or photos. Logo CDN URLs keyed by domain may appear in resource timing.

Android, iOS, and macOS

The native apps read the on-device Contacts database with system permission. Applied logos are written back as contact photos. Undo, where implemented, keeps prior photo bytes in app-private storage on the device, not in iCloud or Google Drive. Android backup of that private store is disabled.

Cookies and local storage

The web app may keep an optional Google client id in this browser's storage so you do not re-paste it. Native apps may keep Brandfetch keys in the system keychain. There is no advertising cookie and no cross-site tracker.

Your choices

Web: close the tab when you finish reviewing. This does not delete downloaded files or undo changes already synced to Google Contacts.
iOS / macOS: Settings → Privacy & Security → Contacts.
Android: app permission for Contacts.
Google: revoke ContactLogo in your Google Account security settings.

Contact

Questions: support@contactlogo.com. You can also open an issue on the public GitHub repository. See also the Terms of Use.