Privacy Policy

Who is responsible

Popdoc is made by Guillaume Cyr. Contact: [email protected].

Popdoc runs no servers: there is no one in the loop but you and Google.

What Popdoc touches

The drive.file scope only — the narrowest possible: Popdoc can only see and touch the files it creates itself. It cannot read the rest of your Drive.

The content of the files you ask it to open goes directly from your Mac to the Google Drive API, with no intermediary server.

Authentication tokens (OAuth tokens) prove to Google that you authorized Popdoc.

What Popdoc keeps — and where

Your access tokens live in the macOS Keychain — your Mac's built-in, encrypted password vault, protected by your login session. They stay only on your machine and never leave it except to talk to Google.

A local dedup index avoids creating a duplicate when you re-open an already-imported file. It stays on your Mac.

What Popdoc does not do

No personal data is collected, required or stored by us.

No tracking, no ads, no analytics, no cookies.

No data is sold, shared or transferred to any third party — there is no server and no database on our side.

Popdoc does not read the rest of your Google Drive.

Google compliance (Limited Use)

Popdoc's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Popdoc uses drive.file access strictly to import and convert the files you hand it, and for nothing else.

Deleting your data

Revoke access: from your Google Account → Security → Third-party apps.

Erase local tokens: open the Keychain Access app, search for Popdoc and delete the entry. Also delete the ~/Library/Application Support/Popdoc/ folder to clear the dedup index.

Already-converted files live in your Drive: manage them like any other Google document.

Changes & contact

If this policy changes, the date at the top will be updated. A question about your data? Write to [email protected].