Privacy policy — Matthew Contacts Sync
Effective 1 October 2026
Purpose and access
Matthew Contacts Sync is a personal desktop application operated by Matthew Hitchcock for his own Google account. It uses Google OAuth to confirm the account identity and the Google People API to read contacts, add missing business contacts, and apply reviewed enrichment from a local customer archive. Google’s contacts permission allows broader operations. The application does not merge or delete contacts.
Data used and changes made
The application reads names, telephone numbers, organisations, email addresses, postal addresses, contact metadata, memberships, notes and custom fields to identify existing contacts, prevent duplicates and verify its work. New contacts contain relevant business names, telephone numbers, usable business postal addresses and source identifiers.
For confidently matched contacts, the authorised rules can fill blank Organisation and explicitly recorded person-name fields, append an eligible Work email, append the Khaos source identifier to Notes, add the NL Customers label, and classify sync-added phone numbers as Work or Mobile where clear. Existing values, notes and labels are preserved. Shared-number company-only names are retained. Generic, shared or company-branded mailbox emails are held for named-person contacts and are eligible only for existing confidently matched company-only contacts; no extra company contacts are created just for email addresses. Unclear email ownership and other conflicts remain held for review.
A Work postal address can be added only when a contact has no existing address of any label. The source must be a unique active invoice address. Ambiguous, placeholder or unusable source addresses are omitted. Closed and identity-held records are excluded from automatic additions and enrichment. Reviewed rules may run nightly after a verified successful archive update, with safety limits, audit journals and fresh-read verification.
Storage and sharing
OAuth credentials are stored in Windows Credential Manager on the owner’s PC. Local archive exports, review reports, audit journals and contact backups remain in files under the owner’s control. Authorised contact additions and changes are sent to Google Contacts and may sync to the owner’s connected devices. Contact data is not published on this website, sold, used for advertising, or used to train AI models. No additional contact-data recipients are part of the sync workflow.
Retention and control
Local records and backups remain until the owner removes them. Google contacts remain until the owner changes or removes them through Google Contacts. Google access can be revoked in Google Account third-party connections settings; revocation stops future access but does not undo changes already made or delete local files. The owner can disable the scheduled task locally.
Website and enquiries
This informational website is hosted by Google Sites and does not provide a contact upload or public sign-up service. Google may process website visits under its own privacy policy. Privacy enquiries can be directed to the app operator through the support email displayed on the Google consent screen.
Google API data use
Use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.