Privacy Policy for contactkit

Last updated: 21 August 2026

What contactkit is

contactkit is a personal address book kept as plain text files in a git repository. It is run from the command line by one person — its operator — on their own computer. It is not a service, it has no users other than its operator, and there is no server anywhere that runs it on anyone’s behalf.

This policy exists because Google requires a published privacy policy before an application may use the People API outside of testing mode. It describes a program with a single operator, and that is the honest scope of it.

What data it touches

With the operator’s authorisation, contactkit reads and writes the operator’s own Google Contacts, using the contacts scope of the Google People API. It does not request access to mail, calendar, files, or any other Google service.

It touches no one else’s Google account. It cannot: the OAuth token it holds authorises access to exactly one account, the one that granted it.

Where the data goes

Nowhere. Contact data stays on the operator’s own computer, in a git repository under their control, and on whatever contact servers the operator has configured for their own use.

contactkit has no analytics, no telemetry, no crash reporting, and no third-party services of any kind. It makes network connections to exactly two sorts of destination: Google’s own API endpoints, and contact servers the operator has named in their own configuration file. It does not sell, share, transfer, or disclose data to anyone, because there is no one to disclose it to.

Credentials

The OAuth refresh token is stored as a file on the operator’s computer, readable only by the operator’s own account. It is never committed to the repository.

Contact information about people other than the operator

An address book contains information about other people by its nature — names, addresses, phone numbers, birthdays. That information is held locally by the operator, in the same way a paper address book or a phone’s contact list holds it. It is not aggregated, sold, published, or transmitted to third parties.

Retention and deletion

The operator may delete their data at any time by deleting the repository and revoking the application’s access at myaccount.google.com/permissions. Revoking access invalidates the stored token immediately.

Changes

Any change to this policy will be recorded here with a new date.

Contact

Questions about this policy may be directed to the operator of this site at flintrock@tinymux.org.