Privacy notice

Effective October 2, 2026 · Version 2026-10-02

Who operates this service

J&J Technology Partners LLC, 5135 Willard Norris Road, Milton, FL 32570. Contact info@jjtechnologypartners.com for privacy and support requests.

Information we use

We use your verified email and sign-in identifier to manage your workspace. We store authorized company-page identifiers and permissions, encrypted LinkedIn access tokens, agent credential hashes, drafts, image identifiers and metadata, image hashes and alt text, approval decisions, publishing receipts, scheduled times, exact revision references, permission snapshots and operation history. We do not receive the email sign-in code you enter into Cloudflare.

Images supplied by your agent pass through this service to LinkedIn for your company Page. We do not retain raw image files in connector storage. Uploading an image does not publish it. Removing workspace records does not delete images or posts held by LinkedIn.

How we use and share information

We use this information to connect the pages you authorize, restrict agent access, process requests from client-authorized agents, maintain security, and resolve failures. Cloudflare hosts the service and handles email-code authentication. LinkedIn receives OAuth requests and the page API requests needed for your chosen actions. Published posts are visible according to LinkedIn's rules. We do not sell this service's customer data.

Access and security

Your account can manage the client workspaces to which you have been explicitly invited. Agents use separate credentials with client-delegated Page capabilities. Stored LinkedIn tokens are encrypted. J&J administrative API access is limited to enrollment and service activation or suspension; it cannot perform LinkedIn activity. J&J operates the underlying infrastructure and handles data/support requests.

Retention and deletion

Workspace records are retained to provide the service, preserve approval history, and investigate unresolved publishing outcomes. You can disconnect an account to remove its usable token, or contact J&J to request workspace deletion. A deletion request immediately stops workspace access and removes usable tokens. J&J then completes removal of retained records; unresolved publishing attempts may require review. Historical backups can retain records until they are removed or expire. Restoration procedures must apply deletion records before restoring service. Minimal hashed deletion records are retained to prevent deleted data from returning through a backup restore.

Deleting this workspace does not delete posts already published on LinkedIn. Contact us to request access to, correction of, or deletion of your information, or for the status of a deletion request.

Page history observations

We store public company-post captions, publication dates, post identifiers and retrieval/import provenance to support authorized Page history reads. Provider captions expire after 48 hours and are hidden when expired, then removed during hourly maintenance or a scoped history write. Independent owner-supplied history remains until workspace removal unless superseded by a provider observation. Referenced member posts, profiles and signed media URLs are not retained in history. Observations grant no authority to publish or edit LinkedIn content.

Optional read-only access

Clients can delegate stored read access without permission to create drafts, upload images or perform content changes. New setup defaults to read-only. Existing grants remain as delegated until the owner changes them. The client and agent choose how to use the tool; permissions and reliable execution are enforced by the connector.

Delegated Page history

Owners may explicitly authorize an agent to read stored published Page history from other agents, LinkedIn retrieval or owner imports. Explicit history loading makes provider read requests; ordinary stored search does not. Imported and retrieved observations grant no editing or publishing rights. Private drafts and internal request, revision, upload and operation metadata are withheld. This permission does not authorize cross-agent changes and defaults off.

Scheduled requests

Scheduling needs a separate delegated grant and an enabled workspace rollout. The connector stores the exact revision, timing and authority needed to act while the agent is offline. Dispatch is best effort within a deadline. Key replacement, changed grants, reconnection and service suspension can block queued work. Changing a draft cancels its old schedule. Cancellation cannot recall a request already dispatched to LinkedIn. Scheduling and operation records follow the workspace deletion process described in the privacy notice.