Keys and passwords
Secure CredentialsAuthentication data kept safely using one-way methods
ARESS gathers financial data from trusted sources, keeps the raw data, and runs control and validation processes, turning what the capital market needs into data you can rely on.
The quality of financial information depends on more than its source: how the data is received, kept, checked and processed all shape it too. ARESS takes data from trusted sources and, after storing, validating and processing it, turns it into information that financial products and services can use.
Choosing the source is the first step of data quality control. We use official, trusted websites connected to the capital market and economic institutions, and we treat their data as reliable on the strength of the source itself.
We review the list of sources and the standing of each one regularly, and we assess every new source for how official it is and how steadily it publishes before letting it into the process.
Data enters the processing pipeline through defined channels, and access to those channels is part of the financial data processing infrastructure.
We build the receiving and storage flow in modules, so each part can be reviewed and tested on its own, by hand and automatically. We check that ingestion, storage and processing are correct with unit tests and integration tests in the code itself.
API keys we receive from various sources and institutions are kept encrypted whenever they are stored in a database or a file. Access passwords are stored using one-way algorithms.
Data we take from trusted sources is stored raw in the database, and every piece of processing runs on that stored copy.
We change nothing before the raw copy is stored. As long as that copy stays untouched, any final figure can be traced back to its original source and checked. Without it, a processing error can no longer be traced.
No more than three months pass between two validation tests. The point is to see whether the data we received and stored still matches the original sources: in each test we take at least 10 percent of the stored data at random and compare it against the original source.
These tests run automatically, and they are deliberately written in a different language or library from the tools in the storage path, so that a fault in the storage process is not repeated inside the test that is meant to catch it. We report each period's result to the board by email or messenger.
We process raw data according to defined methods, formulas and logic. In the mathematics we aim to keep our methods consistent with financial standards and with the teaching of bodies such as the CFA Institute and GARP, and with recognised academic sources.
Wherever we take a formula, a methodology or a particular encoding from an outside source, we check that source's standing and record the reference both in the product documentation and in the code itself. The formulas and mathematical relationships are documented as an appendix to the procedure.
The processed data is the information layer beneath the ARESS financial products, services and systems.
Whoever builds a part of this path documents it themselves once it is implemented: comments in the code, a flowchart, and a written explanation in the product documentation. That documentation is what makes the output reviewable.
Following this procedure is mandatory for all financial data ingestion and processing activities and for the company's specialists and managers. It can only be changed on the managing director's proposal and with the board's approval.
Access to the data sources and to the stored data is part of the financial data processing infrastructure. Access keys and sensitive information are kept with appropriate security measures.
Authentication data kept safely using one-way methods
Encrypted storage of keys and sensitive information
Controlled access to the data sources
A financial figure earns its standing from several independent layers: choosing the source, keeping the raw data, periodic checks, access security and documentation. Wherever processing follows a particular formula, methodology or encoding, we check that source and record the reference in the process documentation and in the code. In the mathematics we aim to keep our methods consistent with financial standards and with the teaching of sources such as the CFA Institute and GARP.
A reference to the original source of a formula or methodology
A flowchart of the collection and processing stages
Notes on the implementation, in the code
In the capital market, financial decisions take shape on top of information. ARESS covers that distance by combining collection, storage, control, processing and delivery: an infrastructure for products and services that need structured financial data they can rely on.
Who uses this dataAccess to accurate, structured data for better analysis and decisions
Support for professional analysis and asset management built on data you can rely on
Current, consistent data for trading and analytical services
Stronger transparency, reporting and compliance with supervisory standards
Access to reliable information for deep analysis and informed decisions