This English version is a translation; in case of any discrepancy, the Czech version prevails.
1. Introductory provisions
This technical information is published by UNALYZE s.r.o., Company ID No. 29853575, with its registered office at Nové sady 988/2, 602 00 Brno, email info@un-alyze.com (“we” or the “Provider”), under Section 12 of the UNALYZE Terms of Service (the “Terms”). It describes the categories of exported data and digital assets, the formats, known limitations, the available interface, the procedure for requesting and handing over the export, the time limits, the price, the jurisdictions of the infrastructure, and the measures against unlawful international access to non-personal data.
The terms Website, service, user account, trading account, plan, subscription, and Price List have the meanings given to them in the Terms.
Export and switching to another provider are governed by Section 12 of the Terms and by the directly applicable rules of Regulation (EU) 2023/2854, where they apply to the service. This information supplements them with technical details and does not change your rights under the Terms. Your rights under the GDPR, in particular the right of access to personal data and the right to data portability, remain unaffected; they are described in the Privacy Policy.
2. Categories of data and digital assets
The export includes the data that we retain about you and your trading accounts and that you are entitled to obtain (Section 12.2 of the Terms). This also includes data from a previous plan for as long as we retain it, for example trading accounts locked after you move to a lower plan or trades hidden because of the plan’s history limit.
The export includes the following categories of data:
- a)
identification and profile data: email address, display name, bio, the billing address entered with the payment gateway, referral code, and the link to your Discord account;
- b)
settings and preferences: language, report time zone, display currency, breakeven tolerance, selected trading account, report and synchronization settings, your choice regarding commercial communications, and browser notification subscriptions;
- c)
records of contractual acts: acceptance of the Terms and the Privacy Policy, offers and orders with the versions of the accepted documents and texts and the time of acceptance, and withdrawals from the contract;
- d)
identification of trading accounts: name, platform, broker server, masked account number, currency, account type, method of obtaining data, and connection status, and, for a direct connection, also the paired devices;
- e)
stored trading history: closed trades, individual transactions including deposits and withdrawals of funds, and the history of the balance and equity, including data from a direct connection and from imported statements;
- f)
reports and stored resulting metrics: weekly, monthly, and yearly reports and reports on individual trades with their stored content and chart data, poster serial numbers, and records of their sharing;
- g)
gamification elements: experience points (XP), streaks, and the history of their crediting;
- h)
subscription and payments: plan entitlements, payment transactions, and tax documents (invoices and credit notes), including the PDF document itself;
- i)
related metadata needed to use the data: the history and results of synchronizations, error categories and rejected data that explain why some data is missing, the progress of loading older history, logged-in devices (IP address, approximate location, and browser), notifications in the user account, audit records, and service usage counters.
Of the digital assets that you upload to the service, the export includes your profile photo and profile background in WebP format, in the form in which the service stored them after upload.
The current version of the service does not allow you to save your own notes on trades; the export therefore contains no notes.
The export does not include (Section 12.3 of the Terms):
- a)
our source code and internal algorithms;
- b)
security secrets and passwords, in particular the investor password in any form, encryption keys, device access tokens, and technical fingerprints of login credentials;
- c)
data of other users;
- d)
raw data in the form in which it was provided by the broker, the external integrator (Section 4.3 of the Terms), the local assistant, or an uploaded statement; the export does include the data processed from it, that is, trades, transactions, and balances;
- e)
internal diagnostic messages; instead, the export states the error category;
- f)
data that we do not retain, for example payment card details, which are processed only by the operator of the payment gateway.
3. Formats
We provide the trading history in CSV format, the complete export in JSON format, and reports in their output format under paragraph 3.6. The CSV and JSON files are encoded in UTF-8.
The CSV file contains the closed trades of all your trading accounts, one trade per row, sorted by trading account and closing time. The first row contains the column names. Values are separated by commas, the decimal separator is a period, and there is no thousands separator. A value containing a comma, quotation marks, or a line break is enclosed in quotation marks. An empty field means that the value is not available.
The CSV file contains the following columns in the order listed:
| Column | Meaning | Unit and format |
|---|---|---|
| account_id | Identifier of the trading account in the service, identical to the id field of the trading account in the JSON file | UUID |
| account_name | Name of the trading account in the service | text |
| platform | Trading platform of the account | MT4 or MT5 |
| broker_server | The broker’s trading server | text, as stated by the broker |
| login_masked | Number of the trading account with the broker, in masked form | text, e.g., 12***89 |
| account_currency | Currency in which the amounts of the account’s trades are stated; for a cent account, the main currency | ISO 4217 currency code, e.g., USD |
| external_trade_id | Position number under which the broker records the trade | text |
| symbol | Traded instrument | text, as stated by the broker |
| direction | Direction of the trade: long is a buy, short is a sell | long or short |
| volume | Trade volume: the sum of the volumes of all entries into the position; for a trade with an unknown opening, the sum of the volumes of the exits | lots, as stated by the broker; at most 4 decimal places |
| opened_at | Time of the first entry into the position; for a trade with an unknown opening, the start of the stored history | ISO 8601 in UTC, e.g., 2026-10-14T18:46:29.123Z |
| closed_at | Time of the last exit from the position | ISO 8601 in UTC |
| open_price | Volume-weighted average entry price; empty for a trade with an unknown opening | instrument price as quoted by the broker; at most 8 decimal places |
| close_price | Volume-weighted average exit price | instrument price as quoted by the broker; at most 8 decimal places |
| profit | Gross result of the trade before costs | in the currency given in account_currency; at most 4 decimal places |
| commission | Commission for the trade; a negative value is a cost | in the currency given in account_currency; at most 4 decimal places |
| swap | Swap for holding the position overnight; a negative value is a cost | in the currency given in account_currency; at most 4 decimal places |
| net_profit | Net result of the trade: the sum of profit, commission, swap, and any other broker fees for the trade | in the currency given in account_currency; at most 4 decimal places |
| entry_truncated | Indicates whether the stored history lacks the opening of the trade (paragraph 4.3) | true or false |
The JSON file contains all categories under Section 2 in the following parts:
- a)
exportMetadata: the version of the export structure (schemaVersion) and the time the export was created (generatedAt);
- b)
subject: data about you, settings, records of the acceptance of documents, logged-in devices, gamification elements, and notifications;
- c)
memberships and organizations: data linked to your user account, in particular trading accounts, trades, transactions, balance history, synchronizations, reports, subscriptions, payments, and documents.
In the JSON file, points in time are stated in ISO 8601 format in UTC. Calendar days without a time refer to the time zone stated in the relevant record or part, for example the report’s time zone; for service usage counters, they are days according to UTC. Trade amounts are in the currency of the trading account, and subscription and document amounts are in the currency stated in the record; fields whose names end in Minor state the amount in the smallest units of the currency, for example in cents. The profile photo, profile background, and PDF documents are embedded as base64-encoded text. When the structure of the export changes, the version in the schemaVersion field changes as well.
The content of each stored report, that is, its figures, texts, and chart data in the form in which the report was created, is part of the JSON file. The Website displays weekly, monthly, and yearly reports as a page in the user account; we do not create a separate file for them. While you have access to reports, you can download the poster of a report on an individual trade on the report page with the “Download image” button, as an image in WebP, PNG, or JPG format. We do not store the poster as a file; we render it from the stored content of the report each time it is downloaded.
4. Known limitations
The export contains only data that the service has received and retains. The completeness of the trading history also depends on the broker, the trading program, and the chosen transfer method (Section 4.7 of the Terms). The export cannot contain data that has already been deleted, for example after a trading account is removed, after the user account is closed, or after the retrieval period under Section 12.8 of the Terms has expired. The export includes trades hidden because of the plan’s history limit until we delete them in accordance with the Price List.
The CSV file contains the closed trades that the service has compiled from the transactions of the trading account. Open positions and transactions from which we do not compile trades, for example for an account in a mode that the service does not support, are not in it; they are contained in the JSON file.
If the stored history does not contain the opening of a trade, the trade has the value true in the entry_truncated column, the start of the stored history as its opening time, and an empty opening price.
For cent accounts, for example in USC, we state amounts in the main currency (100 USC = 1 USD). We state volume in lots as stated by the broker.
We state times in UTC. For data from the local assistant and from an imported statement, we convert the trading server’s time to UTC according to the rule that governs that server’s clock. For a trade executed within one hour of a change between daylight saving time and standard time, the time may therefore differ by one hour.
We calculate the metrics and the UN Score on the dashboard from the trading history. We store their intermediate results only as a technical cache for faster display, and the export does not contain them; it contains the trading history on which the metrics are based and the metrics stored in reports.
In the JSON file, trades, transactions, and balance history records are not assigned to a specific trading account. The assignment of trades to trading accounts is contained in the CSV file.
The export passes through a security filter that replaces values in the form of access credentials with text beginning with “[redacted-”. Should the filter replace any of your data in this way, we will add it back, or we will inform you and provide the data to you on request.
5. Export request and available interface
You may request an export, that is, a copy of your data, or switching to another provider or to your own environment at any time using the contact details under Section 1.3 of the Terms: by email to info@un-alyze.com, through the contact form on the Website, or in writing at the address of our registered office. A switching request is not tied to the end of a monthly or annual billing period (Section 12.1 of the Terms).
In the request, state the email address of your user account and tell us whether you are requesting a copy of your data, switching, or termination and deletion without switching under Section 12.6 of the Terms.
The export is created and handed over by our support team. A self-service export in the user account is not available. The service has no API or other programmatic interface for exporting or transferring data; we hand over the data as files under Section 3.
The export captures the state of the data at the moment it is created, which is stated in the generatedAt field of the JSON file.
6. Secure handover
Our support team uploads the export files to private storage in the EU. We will send the signed download link exclusively to the email address of your user account, even if you submitted the request another way.
The link is valid for 7 days. When it expires, we delete the files from the storage. If you do not download them within this time, you can request a new export.
Do not forward the link to anyone: anyone who has it can use it to download the files.
When switching, you download the files and hand them over to the new provider or to your own environment yourself. During switching, we will provide you with reasonable assistance and maintain the security and continuity of the service (Section 12.4 of the Terms).
7. Time limits
We will confirm receipt of your request and agree with you on the destination and the schedule of switching; the secure method of handover is described in Section 6 (Section 12.4 of the Terms).
We will hand over the export and begin switching without undue delay, and no later than 30 calendar days after the request, unless you specify a later date. As standard, we will complete switching within 30 calendar days of its start (Section 12.4 of the Terms).
You may extend the switching period once; tell us of your request before it expires. If switching within the standard period is objectively technically unfeasible, we will notify you no later than 14 working days after the request, substantiate the reasons, and propose an alternative period of no more than 7 months (Section 12.5 of the Terms).
After switching is completed or the paid service otherwise ends, we will keep the exportable data available for you to retrieve for at least 30 calendar days and will tell you the last day for retrieval in advance (Section 12.8 of the Terms). During this time, you can request an export under Section 5.
8. Price
Standard export and switching are free of charge. We do not charge any special fee for a standard export, switching, or early termination under this regime (Section 12.7 of the Terms).
If you request a non-standard format or an individual adjustment of the output beyond our statutory and contractual obligations, we will tell you the price in advance and carry out the adjustment only after you have expressly ordered it. At the same time, the standard export remains available to you free of charge.
9. Jurisdictions of the infrastructure
We process and store the service’s data in the infrastructure listed in this table, by its role and the jurisdiction in which it is located:
| Role of the infrastructure | Jurisdiction and location |
|---|---|
| Database, login, and file storage, including export files | EU—Germany (Frankfurt am Main) |
| Website server functions | EU—Germany (Frankfurt am Main) |
| Encryption key management | EU—Germany (Frankfurt am Main) |
| Background jobs, for example synchronization; local assistant updates; market prices for report charts | EU—Germany |
| Copies of tax documents | EU—Germany (Nuremberg) |
| Error tracking | EU |
| Retrieval of trading account data through the external integrator (Section 4.3 of the Terms) | United Kingdom (London), outside the EU |
| Payments and invoicing | the payment gateway operator, established in Ireland (EU); processing in the EU, in the USA, and by the operator’s other suppliers |
| Email delivery | sending from Ireland (EU); logs, metadata, and message content are retained by the email delivery provider in the USA |
| Assistant for finding your way around the Website (Section 14.2 of the Terms) | Canada and the USA |
| Product analytics, only with your consent | EU |
| Website traffic measurement, only with your consent | USA |
Transfers of personal data outside the European Economic Area and the related safeguards are described in the Privacy Policy.
10. Measures against unlawful international access to non-personal data
We protect the service’s data against unauthorized access, including access by public authorities outside the EU that would be contrary to the law of the EU or of the Czech Republic. In particular, we use the following technical and organizational measures:
- a)
the database, login, file storage including export files, Website server functions, background jobs, and encryption key management are located in the EU; the exceptions are listed in Section 9;
- b)
the data of each user account is separated in the database: every table with customer data has row-level security rules under which the database makes available to a logged-in user only the records of their own account, except for records that the user shares (Section 8.3 of the Terms);
- c)
communication with the Website is encrypted over HTTPS, and the Website instructs browsers to establish only secure connections;
- d)
we store investor passwords encrypted with the AES-256-GCM algorithm with a separate key for each user account, and these keys are protected by a key management service in the EU; the encrypted passwords cannot be read from the browser, and the server decrypts them only in precisely defined cases, in particular to connect a trading account and retrieve its data, and always only after an audit record has been written;
- e)
only authorized support staff can create an export; the Website creates the JSON file only for persons on the list of authorized persons who are logged in with two-factor authentication, and it records each creation of the file in an audit record;
- f)
access keys with full database permissions are used only by the server; they are never part of the code loaded into the browser;
- g)
operational logs and error reports do not contain passwords, access tokens, or raw data from the broker, and the error tracking service receives user and account identifiers only in pseudonymized form;
- h)
we hand over the export from private storage in the EU via a signed link valid for 7 days, only to the email address of the user account, and we delete the files when the link expires (Section 6).
11. Final provisions
We update this information when the structure of the export, the formats, or the infrastructure of the service changes, and we publish the current version on the Website. A change to this information does not in itself change your rights under the Terms.
This technical information is version 1.0 and applies from the date of its publication on the Website.