Data security is an ongoing responsibility. Arbicsx handles personal and operational information with care, applying technical and organizational measures designed to protect it over time. This guide explains how in an accessible way.
Categories of processed data
- personal and contact data required for account opening and management;
- administrative data related to subscriptions and transactions;
- operational data shown in the dashboard, derived from accounts linked to brokers;
- technical data produced by software use (system logs, security events).
Guiding principles
Data processing follows three general principles: minimization (we collect what is necessary), relevance (we use data for purposes consistent with the service), and limited retention (data remains for the time necessary for the stated purposes and legal obligations).
Technical measures
- data transmission protected in transit;
- data access controls based on the principle of least privilege;
- monitoring of security events and anomalous access;
- periodic backups and tested recovery plans.
Organizational measures
Personnel accessing data for service reasons operate according to internal procedures, periodic training, and individual accountability criteria. Information is not shared with third parties outside of stated operational needs and legal obligations.
Data security is a shared effort: the platform does its part, but account protection also stems from how you manage it. See Account Protection.
Operational data and brokers
The platform displays data derived from accounts linked to brokers. It does not have access to data unnecessary for monitoring and does not execute market operations on behalf of the user. The distinction of perimeters, along with its positioning as a fintech software house under D.Lgs. 58/1998 (TUF), is central.
Security incidents
In the rare event of a security incident, the approach is to communicate early with verified information, clearly stating what happened and what we recommend doing. This choice of transparency is consistent with what is described in Important Communications.
Reference documents
The complete conditions on data processing are described in the official documents (privacy policy and related documents), which can be consulted as indicated in Terms, conditions and useful documents.
Reporting
If you observe something that seems like a security issue — a suspicious message, anomalous account behavior, content asking for data that should not be requested — reporting it promptly to support is the correct choice. The early hours are the most valuable for intervention.
A continuous commitment
Security measures evolve alongside the evolution of threats. This guide describes the current state of principles; technical details follow industry standards and best practices and are updated regularly.
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