Privacy Policy

This policy describes how we collect and use information when you use telegram.acerbo.ai and the in-browser chat.

Data controller

Livio Andrea Acerbo. Contact: via the main page (matrix.acerbo.ai, LinkedIn).

What we collect

Chat messages — Text you send in the in-browser chat is processed to generate a reply. Messages are not stored long-term on our servers; they are processed in memory for the duration of the request.
Session identifier — A cookie (assistant_session_id) links requests so the assistant can keep conversation context. It does not identify you personally.
Cookie consent — We store your consent choice in a cookie (cookie_consent) as required for compliance.

If you use the bot on Telegram, Telegram’s privacy policy and our use of Telegram’s API apply to that channel; we do not log or store Telegram messages on our servers beyond what is needed to reply.

Purpose and legal basis

We use your data only to provide the chat and assistant service and to comply with consent obligations. Legal basis: your consent (cookies and chat use) and performance of the service.

Retention

We do not retain chat messages. The session cookie expires after 7 days. Consent cookie: 1 year. Server logs (e.g. IP, request time) may be kept for a short period for security and operation; we do not link them to your messages.

Sharing and transfers

We do not sell or share your data with third parties for marketing. Message content is sent to the AI/orchestrator backend (and any configured APIs it uses) only to generate replies. If you use Telegram, data is processed according to Telegram’s terms and infrastructure.

Your rights (GDPR)

If you are in the EEA/UK you have the right to: access your data, rectify it, erase it, restrict processing, object, and data portability. You can withdraw consent at any time (e.g. by clearing cookies or not using the chat). To exercise rights or complain, contact us via the main page (e.g. matrix.acerbo.ai, LinkedIn). You may also lodge a complaint with your supervisory authority.

Security

We use HTTPS and do not store chat content. Session cookies are HttpOnly where possible.

Changes

We may update this policy; the “Last updated” date will change. Continued use after changes means acceptance.

Last updated: 5 February 2026