Personal tool · Privacy notice

LinkedIn editorial scout

Last updated: 30 September 2026

This notice covers a personal, read-only editorial tool operated by Zacaria Chtatar. The tool is intended for Zacaria’s own LinkedIn account, not for other members to sign in. It is not yet connected to LinkedIn; the processing described below begins only if Zacaria authorizes the connection.

Who is responsible?

Zacaria Chtatar operates the tool. For privacy questions or a deletion request, email havesomecode@gmail.com.

What data and why?

With the account owner’s authorization, the tool will request only the LinkedIn Member Data Portability data needed to identify subjects already published: original posts and articles, their text, publication dates, and links or identifiers. It will use them to avoid repeated topics and suggest new draft subjects for the owner to review. It will not read private messages, contacts, or the feed for this purpose, and it will not post, react, connect, or message on LinkedIn.

The processing is based on the account owner’s explicit authorization for this purpose. This page itself does not connect to LinkedIn or request account access.

Where does it go?

The tool runs in Zacaria’s controlled Hermes environment. Short excerpts or topic summaries may be sent to the configured AI model provider to draft suggestions. Selected draft ideas may be stored in a private Notion editorial bank and summarized in a private Discord notification. These services process information under their own applicable terms; the tool does not sell LinkedIn data or share it with advertisers. Service providers may process data outside the European Economic Area.

How long is it kept?

Access credentials are kept only while the connection is authorized and are removed when it is disconnected. Raw LinkedIn activity cached for the scout is deleted within 30 days. A minimal index of published topic labels and links, and editorial ideas in Notion, remain until Zacaria deletes them or requests deletion so the tool can avoid repeating past subjects. Server access is restricted to the operator and the tools needed for this workflow.

Your choices

The account owner can revoke the app’s LinkedIn access and ask to inspect, correct, export, or delete locally retained data by contacting the address above. Revoking access stops new reads; a deletion request also covers the local cache and editorial records derived from it. Questions about LinkedIn’s own processing should be directed to LinkedIn.