Privacy policy for Post Publisher

Effective date: 2026-06-04. This policy explains what Post Publisher processes, how it is used, and what is intentionally not done with that data.

What Post Publisher does

Post Publisher is a command-line application that authenticates a user with LinkedIn and, after an explicit action from that user, publishes posts on that user’s behalf.

Data processed

OAuth credentials and access tokens returned by LinkedIn
Basic profile identity data returned by LinkedIn, such as member identifier and display name
Email address if LinkedIn includes it in the authorized response
Post content explicitly provided by the user, including text, image files, and PDF files

How data is used

To authenticate the user with LinkedIn
To identify the member account used for posting
To create the LinkedIn post explicitly requested by the user
To store local CLI configuration needed for future runs

What is not done

No sale of personal data
No background posting without an explicit user command
No sharing of LinkedIn account data with unrelated third parties

Local storage

The CLI stores configuration and session data on the user’s local machine. That may include access tokens, resolved member identity, selected API version, and local project defaults. The storage exists to make the command-line workflow usable between runs.

User control

The user controls when authentication happens, when content is submitted, and when local session state is removed. The CLI includes logout and local configuration commands for that purpose.

Contact

For questions about this policy or the application, use the public contact page at /contact/.