Data Export Formats
Version 1.0 · Effective 1 November 2026
Data export and switching
Algora S.A. · Last updated: [PUBLICATION DATE]
This page describes how our customers can export their data, switch to another provider or have their data erased. It is the online description referred to in Section 9.3 of the Algora Terms and Conditions and is provided in accordance with Regulation (EU) 2023/2854 (the Data Act). It applies to all customers of the Algora platform.
1. What you can export
You can export your Customer Data and their metadata:
- documents you uploaded, in their original files;
- portfolios and their positions;
- watchlists;
- notes;
- stored outputs (reports, analyses and answers saved in your workspace) with their citations and sources;
- the configuration of your custom analysts and workflows;
- account metadata (users, roles, settings and creation dates).
The export does not include Algora's software, models, prompts or internal logs, or third-party content (market data, news, filings) beyond what you may keep under Section 4 of the Terms.
2. Formats and structure
| Data | Format | Structure |
|---|---|---|
| Uploaded documents | Original files (for example PDF, DOCX, XLSX) | Same folder structure as in your workspace |
| Portfolios and positions | CSV and JSON | [CONFIRM: one row per position, with columns such as portfolio, instrument name, identifier (ISIN or ticker), quantity, currency, valuation date] |
| Watchlists | CSV and JSON | [CONFIRM: one row per instrument, with watchlist name and identifier] |
| Notes | JSON | [CONFIRM: title, text, author, creation and update dates] |
| Stored outputs with citations | PDF and JSON | PDF as displayed in the platform; JSON with the text, the list of sources cited, author and date |
| Custom analysts and workflows | JSON | [CONFIRM: name, instructions, steps, data sources, schedule] |
| Account metadata | JSON | [CONFIRM: users, roles, settings, creation dates] |
3. Standards and interfaces
- Text files are encoded in UTF-8. CSV files follow RFC 4180, JSON files follow RFC 8259, and dates and times use ISO 8601.
- The export is delivered as a ZIP archive, made available through a secure download link sent to your designated contact. [CONFIRM: delivery method, and whether an export through the API is also available.]
- A description of each file and field is included in the archive.
4. How to request an export, a switch or an erasure
- Send a written request to info@algora.lu, stating whether you want to switch to another provider, transfer your data to your own infrastructure, or have your data erased.
- Notice period. The process starts two (2) months after your request, or earlier if you choose a shorter period.
- Transitional period. For up to thirty (30) days, the service continues, we assist you and the third parties you designate, and we provide the export. If this period is technically not feasible, we inform you within fourteen (14) working days and propose an alternative period of up to seven (7) months. You may extend the transitional period once.
- Retrieval. After the transitional period, and at the end of the contract for any other reason, you have at least thirty (30) days to retrieve your data.
- Erasure. We then erase your Customer Data. Copies in backups are deleted in the normal backup cycle set out in our Data Processing Agreement and remain protected until deleted. On request, we confirm the erasure in writing.
5. Costs
We charge no switching or data egress fees. Subscription fees remain payable until the end of the transitional period.