Some communications carry more weight than ordinary release notes: they announce significant changes, explain incidents being resolved, or clarify important operational aspects. This guide explains what to expect from important communications and how to read them.
What qualifies a communication as "important"
- change to an existing feature with a direct impact on daily operations;
- extensive incident, ongoing or recently resolved, that warrants public clarification;
- update to legal documents or terms of service;
- modification of relevant operational policies, such as broker connection rules;
- information on risks to be aware of related to specific scenarios.
Where to find them
Important communications are published in the Updates category and, when necessary, also displayed in the reserved area with a dedicated highlighter. The most relevant ones remain available over time, so you can re-read them whenever needed.
How they are structured
We try to follow a consistent outline: context in two lines, what is changing, when it changes, what you need to do (if anything), and who to contact in case of doubts. A stable structure helps you read quickly and immediately distinguish fundamental information from details.
How to read them
Important communications deserve a full reading: skipping the "what you need to do" part is the most common way to be unprepared during a transition phase. If you have doubts after reading, the correct channel is usually customer care for administrative topics and technical support for operational ones, as described in the Support and customer care category.
A third-party message asking for sensitive data is never an official communication. The Account protection section explains how to distinguish them.
Transparency on incidents
When an incident occurs that impacts a portion of users, the core choice is to communicate early even if information is partial, and update as the situation becomes clearer. This choice prefers transparency over silence, even at the cost of having to partially rectify later.
Communication commitments
We are committed to always distinguishing between verified facts and information still under analysis, avoiding alarmist tones or unsubstantiated reassurances, and providing realistic update timelines. Some of these rules are also described in Best practices for transparent communication.
Scope
Important communications concern software, service, and operations. They do not modify the legal scope: Arbicsx exclusively provides technology pursuant to D.Lgs. 58/1998 (TUF), does not manage capital on behalf of third parties, and does not promise returns. Every communicated change remains within this framework.
Was this guide helpful?
If this guide wasn't enough, our team is available.
Every request is routed to the correct channel. Contact us and receive a structured reply as quickly as possible.
Go to support