Privacy policy

Last updated 14 August 2026. This covers the Nexus application and the nexusmessenger.app website. It is deliberately short, because there is not much to declare.

What the application stores, and where

Every service you add gets its own storage partition: its cookies, its local storage, its local databases. That is exactly what lets two accounts of one service stay signed in side by side without signing each other out.

What Nexus does not see

Your credentials are typed into each service’s official pages, not into any Nexus interface. The application does not modify those pages, injects no script, and does not sit between you and the service. No message and no password passes through us: there is no server-side “us”.

The only connection Nexus makes on its own

The application asks GitHub, where releases are published, whether an update exists. Like any request on the internet, that one exposes your IP address to the server contacted, here GitHub, whose privacy policy then applies.

Beyond that: no telemetry, no crash reporting, no usage statistics, no installation identifier.

The services you add

WhatsApp, Teams, Telegram, Gmail and the rest are loaded from their own servers, in their own official interface. They collect what they normally collect, and their policies apply in full, exactly as if you had opened them in a browser.

The nexusmessenger.app website

Your rights

We hold no data about you, so there is nothing on our side to access, correct, export or delete. For the data held by the services you use, contact them: they are the controllers. To erase what sits on your machine, remove the service inside Nexus, or uninstall the application.

Check rather than trust

Nexus is published under the MIT licence and its source is public. Everything above can be read in the repository, including the update request and the absence of any other outbound connection. A privacy policy is worth exactly as much as your ability to verify it.

Changes and contact

If this document changes, the date at the top changes with it, and the edit history stays visible in the site’s repository. For any question, open an issue on the GitHub repository.

Sources