Privacy policy for Agentas Social

Who is responsible

Agentas AS is the controller: org.nr 831 676 752, Nordvikveien 61, 4085 Hundvåg, Norway.

E-mail: [email protected]

What the tool is

Agentas Social is an internal tool. It is not offered to anyone else, it is not open to the public, and only our founder can sign in.

A post starts as a draft. Our founder reads each draft in its exact wording and approves it, and only then does the tool publish that text on our LinkedIn page, on his LinkedIn profile or in our Discord channels, at the time he chose. For Reddit and Steam the tool only prepares the text, and we post it ourselves.

What it stores from LinkedIn

• The access token from the LinkedIn sign-in. It is stored encrypted and used only to publish our posts and, where LinkedIn allows it, to read the numbers for them.
• For our founder's own profile: his LinkedIn member ID and name, which LinkedIn gives at the sign-in.
• The text and images of the posts we publish, the ID LinkedIn gives each post, and when it went out.
• The numbers for our own posts, such as views, reactions, comments and shares, as totals.

It stores nothing about other LinkedIn members: not who reacted or commented, not what a comment says, and no profiles, connections or messages. The tool does not read the feed, and it never comments, likes, sends messages or sends connection requests.

Discord

In our Discord channels the tool posts through webhooks or our own bot, and stores the ID and link of each message. It stores nothing about the members of the server.

Help from AI

Drafts may be prepared with Claude, an AI assistant from Anthropic. It can read our own drafts and the numbers for our own posts. It has no access to the LinkedIn access token and cannot approve or publish anything. We do not give LinkedIn member data to any AI system, and LinkedIn data is not used to train AI models.

Why, and on what basis

We do this to publish our own company's posts and keep a record of what we published. The legal basis is our legitimate interest in marketing our own business (GDPR article 6(1)(f)). Our founder's name and member ID are processed because he signs in himself to publish on his own profile.

Where it is kept, and for how long

The data is kept on our own server in Norway. Tokens and webhook addresses are encrypted and never written to logs, and signing in takes a passkey.

Posts and the records about them are kept as our publishing history for as long as we use the tool. The access token is deleted when we remove the channel, and a new sign-in replaces it. LinkedIn's tokens stop working after 60 days. Backup copies are made every night and replaced on a rolling basis.