Depending on the features you use, SignalFlow may process the following categories of data.
Account data
- name or display name;
- email address;
- registration and email verification dates;
- account status and role.
We do not store passwords in plain text. The database stores only a cryptographic hash created using Argon2id.
Authentication and security data
- IP address;
- User-Agent, which may contain information about the browser and operating system;
- session creation, renewal, and termination dates;
- authentication token hashes;
- information about sign-in attempts and security events.
SignalFlow does not create separate persistent device identifiers.
Service usage data
- history of issued signals;
- selected currency pairs and expiration times;
- signal direction, issue time, and outcome;
- information about the use of SignalFlow features;
- technical interaction timestamps.
Data related to Binodex
- numeric Binodex account ID;
- registration status through the partner link;
- confirmed deposit amount;
- registration, deposit, and access verification dates;
- technical events received from the Binodex partner system.
SignalFlow does not receive or store the user’s Binodex password, bank card data, or payment method details.
Telegram data
If a user voluntarily enables notifications, we may store their Telegram Chat ID and the information required to send those notifications.
Support requests
- name, if provided;
- email address;
- message content;
- date and technical details of the request.
Technical information
We may receive information about application errors, performance, visited pages, and the technical environment.
Goal planner data is stored locally in the user’s browser and is not sent to the SignalFlow database.