Privacy and terms

Privacy

Information used to connect LinkedIn

When the owner connects LinkedIn, the app requests basic profile and post-sharing permissions. It reads the LinkedIn account ID and name to confirm which account will publish. It does not request LinkedIn email access, connections or private messages. LinkedIn’s post-sharing permission also covers comments and likes; this app uses it only for reviewed posts.

The app stores the LinkedIn app’s client ID, encrypted client secret, encrypted access token and its expiry, and the connected account ID and name in a private Cloudflare D1 database. The client secret and access token are not returned to the browser after saving. Owner sign-in uses an essential session cookie.

Private drafts and publishing history

Saved drafts and publishing history are available only through owner access. Records can include the reviewed text, selected format and cover option, account ID and name, time, outcome and published link. Unsaved draft text is held in the open browser tab, not saved in browser storage.

When information is sent to a platform

LinkedIn handles account sign-in and grants the app access. The app contacts LinkedIn to complete the connection. When the owner chooses Publish LinkedIn post after reviewing a saved draft, the app sends the post text, article link, link-card title and excerpt, and any selected cover image to LinkedIn. Published posts are public under the connected personal profile. A cover upload or an uncertain attempt can reach LinkedIn even if the studio cannot confirm publication.

LinkedIn articles and X drafts are prepared for copying into those platforms’ own editors. Copying text or opening an editor does not publish it. This app has no X publishing connection and sends no email notifications about publishing. LinkedIn and X handle information submitted in their own editors under their own policies.

Disconnecting and deletion

Disconnect LinkedIn removes the app’s stored access token, current account ID and name, and pending connection requests. It keeps app connection settings, saved drafts and publishing history, including account details retained in past history. There is no automatic deletion schedule for these records, and token expiry does not automatically erase the stored token.

Disconnecting here does not revoke the app’s permission at LinkedIn or delete a LinkedIn post. To also withdraw LinkedIn permission, remove this app from the permitted services in your LinkedIn account settings. Manage or delete published posts directly on LinkedIn.

To request deletion of retained LinkedIn account information or publishing records, use the contact form. Removal beyond Disconnect LinkedIn currently requires maintenance by the website owner; there is no self-service delete-all control. Requests about information held by LinkedIn or X must also be handled with that platform.

Use agreement

This app is for the website owner’s own accounts and content. By using it, the owner agrees to connect only an account they are authorized to use and to keep the app’s connection credentials private. LinkedIn sign-in takes place on LinkedIn; this app does not ask for a LinkedIn account password.

The owner is responsible for checking the connected account, the final wording and image, the source article, and their right to share the content before publishing. Do not submit misleading content or content that infringes another person’s rights.

Saving or preparing a draft does not publish it. A LinkedIn post is sent only after the owner reviews the saved draft and chooses Publish LinkedIn post. LinkedIn articles and X content must be published in their own editors. If an attempt is uncertain, check the platform before publishing again; the studio blocks automatic retries of that saved attempt.

LinkedIn access depends on its permissions, token validity and service availability. A successful connection does not publish a post, verify the owner’s identity, or imply endorsement by LinkedIn. Use of LinkedIn remains subject to its terms.