PIM Sync Privacy Policy
Last Updated: June 20, 2026
This Privacy Policy explains how the PIM Sync application accesses, uses, stores, and protects information obtained from Google APIs.
Roles used in this policy
To avoid any ambiguity, this policy uses two defined terms:
- Operator — Privacy Playbook LLC, the party that provides the PIM Sync application (the software). The Operator does not host, receive, transmit, store, or have any access to an Owner's Google data.
- Owner — the individual who runs their own instance of PIM Sync, connects their own Google account to it, and whose contacts, calendar, and tasks are synchronized to their own self-hosted personal-information system. The Owner controls and hosts their own data.
PIM Sync is a self-hosted tool: data is synchronized only between the Owner's Google account and servers the Owner controls. The Operator supplies the software and never sees Owner data. Where this policy says "your" data, it means the Owner's data.
1. What the application accesses
When an Owner connects a Google account, PIM Sync requests access only to the data it synchronizes, plus a read-only identity check:
- Google Contacts (
https://www.googleapis.com/auth/contacts) — read and write. - Google Calendar (
https://www.googleapis.com/auth/calendar) — read and write. - Google Tasks (
https://www.googleapis.com/auth/tasks) — read and write. - The Owner's email address and basic profile (
https://www.googleapis.com/auth/userinfo.email,https://www.googleapis.com/auth/userinfo.profile) — read only. - Sign-in (
openid) — the standard OpenID Connect sign-in scope, requested automatically alongside the profile scope. The application does not use the resulting ID token for anything beyond completing the sign-in.
The application requests no other Google scopes and accesses no other Google services.
2. How the information is used
PIM Sync uses the data for one purpose only: to synchronize the Owner's own contacts, calendar events, and tasks between Google and the Owner's self-hosted personal-information system (an LDAP/CardDAV contact directory and a Radicale CalDAV server). The email and profile scopes are used solely to verify, at the start of each sync, that the connected account matches the Owner — a safety check to prevent syncing the wrong account. That identity information is not stored or shared.
3. Where the information is stored
Synchronized data is stored on servers the Owner controls. OAuth refresh tokens are stored on those servers with restrictive file permissions and are never transmitted to any third party. The Operator runs no servers in this flow and holds no copy of the data: it moves only between the Owner's Google account and the Owner's own servers.
4. Information sharing
PIM Sync does not sell, rent, or share an Owner's Google data with any third party. The data is never used for advertising, never used to train machine-learning or AI models, and is never read by any human other than the Owner. The Operator has no access to it.
5. Google API Services Limited Use disclosure
PIM Sync's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, data obtained through Google APIs is used only to provide the synchronization features described above; it is not transferred to others except as necessary to provide those features, to comply with applicable law, or as part of a merger or acquisition; it is not used for advertising; and it is not read by humans except the Owner, and otherwise only where necessary for security or to comply with applicable law.
6. Data retention and deletion
Synchronized data is retained on the Owner's servers for as long as the Owner runs PIM Sync. The Owner can revoke the application's access at any time from Google Account → Security → Third-party access; doing so immediately invalidates the application's tokens. The Owner may delete the locally stored copies and tokens at any time.
7. Security
All Google API traffic uses TLS. OAuth tokens are stored with Owner-only file permissions on the Owner's own servers. The system is self-hosted and is not exposed as a shared cloud service.
8. Children
PIM Sync is a personal tool run by its Owner and is not directed to children.
9. Changes to this policy
If this policy changes, the updated version will be posted on this page with a new "Last Updated" date.
10. Contact
Questions about this policy or PIM Sync's data handling can be directed to the Operator at pim-sync@privacyplaybook.com.