Legal

End-user licence agreement

What you may do with the Booost desktop application, how credentials are handled, and how updates work. Effective 1 September 2026.

Last updated · July 26, 2026
The Italian version is the only authoritative text. This page is an English summary provided as a courtesy. The binding document is the Licenza d'uso del software, in Italian, in force from 1 September 2026. Where the two differ, the Italian text prevails.

What you get

A personal, non-exclusive, non-transferable and revocable licence to install and run the Booost desktop software for as long as your subscription is paid, for the commercial outreach purposes the software is built for. Booost is explicitly licensed for business use — it is not restricted to personal non-commercial use.

You may install it on any device of your own, provided the use stays yours: the licence does not allow different people to share one subscription. You may connect the accounts you pay for — Personal covers your own connected account, Business covers as many connected accounts as you are billed for.

What you may not do

Copy the software beyond lawful backups, modify it or create derivative works, resell or sublicense it, remove proprietary notices, or use it to build a competing product.

Decompilation is prohibited except where it is indispensable to achieve interoperability with independent programs, under Article 6 of Directive 2009/24/EC and Article 64-quater of Italian Law 633/1941. That exception cannot be contracted away and any clause to the contrary is void — it is written into the licence for that reason.

Your API key (Basic edition)

Your key is stored only on your device, protected by the operating system's secure storage — DPAPI on Windows, Keychain on macOS, the secret service on Linux. It is never transmitted to Alfercom's servers, in any form.

One limit you should know: on Linux systems with no secure store configured, that service is unavailable and the value is written in clear text in the local database. We cannot guarantee encryption at rest on such a configuration. Check that a system keyring is running.

Configuring a key sends other people's data to the provider you chose — for incoming-message classification, the full text of the message you received. For that data you are the controller: you picked the provider and you carry the consequences, including any transfers outside the EU and that provider's training policies. If you would rather not send anything anywhere, leave the key unset — the AI features simply stay off — or run a local model, which the software supports, in which case nothing leaves the machine.

Booost AI (Pro edition)

No key to configure: model access is part of the service. Content travels from the software to Alfercom's servers and on to the inference provider. The writing instructions, the banned-register lists and the text quality rules do not live in the software and are not licensed to you: they sit on Alfercom's servers and remain our confidential know-how. The installed software carries only generic instructions, for the features that run on your own key.

Credentials and session

The primary credentials of your connected account — username and password — are never transmitted to or stored by Alfercom. Neither are the session credentials: cookies and session tokens stay in the rendering engine's cookie store on your device, in a separate partition per account, and never cross the network towards us.

Do not stretch that promise further than it goes. What stays on your device are the credentials and the session. Contact data does travel to our servers, the connection graph included, as the privacy notice describes.

Diagnostics and updates

The software does not collect or transmit diagnostic telemetry: there is no crash reporter and no application logs are sent. The in-app diagnostics panel works locally, on a temporary in-memory log. A deep-capture function exists, off by default, and writes to local files that stay on your device.

Automatic updates are on by default and may install without interaction where security requires it. Breaking changes are notified at least 30 days in advance; mandatory updates must be installed within 30 days; support for releases older than 12 months may end with 30 days' notice.

When the licence ends

On expiry or termination the software deletes locally stored session credentials, campaign and message caches, automation configuration and your API key, by secure overwrite. You have 7 days to uninstall. Export your data first, from Settings → Data → Export Data (JSON or ZIP). Data already on Alfercom's servers stays governed by the privacy notice and the DPA.

Read the binding text

The complete licence is the Italian one: Licenza d'uso del software.