Social Publishing Policy

This page explains how data will be handled when KAIROS enables social-account connection and publishing features.

The availability of each integration will be shown in the service itself. A platform will only be treated as connected once the user completes the relevant authorisation flow and the integration has been enabled for use.

LinkedIn is the first planned integration.

Other platforms such as YouTube/Google, TikTok, Meta/Facebook or Instagram may be added only when the relevant integrations are enabled, approved and verified.

Mentioning a platform here does not mean it is currently connected.

When an integration is active, KAIROS will use the official OAuth flow provided by the relevant platform.

KAIROS does not need and should not request the password for your social account.

Before connecting an account, the user must be able to understand which platform is being connected, the purpose of the connection, the requested permissions or data categories, when the data will be collected, how it will be used, how authorisation can be withdrawn and how deletion can be requested. Connection will occur only after an affirmative user action through the relevant OAuth flow.

Depending on the platform and the permissions actually granted, an integration may process:

• account, profile, organisation or page identifiers;
• access tokens provided by the platform;
• granted permissions/scopes;
• text, media or metadata the user authorises for publication;
• publishing state, errors and references required to prevent duplicates and maintain operational history.

KAIROS does not claim that every category is processed on every platform. It depends on the integration actually enabled.

Integration data is used only to provide the requested functions, such as connecting an account, preparing or executing an authorised publication, recording its status, preventing duplicates, managing errors and providing operational control.

Publishing availability depends on each platform's approval and terms.

When LinkedIn is enabled, KAIROS will use the APIs and permissions approved by LinkedIn and comply with its API Terms, Community Management requirements and applicable storage and deletion conditions.

LinkedIn permits storage of certain application authentication tokens and requires deletion of data collected on a user's behalf, including applicable tokens, when that user requests deletion or closes their account, unless a legal obligation prevents deletion.

A LinkedIn integration will only be presented as available once the relevant connection has been enabled and verified for use.

When the functionality exists, users may request disconnection and deletion of data under KAIROS control by writing to:

[email protected]

KAIROS does not promise a particular encryption method, token lifetime or automatic-deletion mechanism that has not been implemented and verified.

The external platform may retain information under its own terms, logs, backups or legal obligations.

KAIROS may use self-hosted infrastructure or technical providers necessary to operate integrations.

The architecture is designed around KAIROS-owned adapters so that the KAIROS domain is not directly coupled to one external provider.

Security details that could facilitate attacks or compromise secrets will not be published on this page.

This page will be updated when a platform moves from planned to operational or when permissions, processing or disconnection mechanisms materially change.