Data export
Last updated: October 6, 2026
This page explains how to download the data of a Linia Directă account and what the exported files contain. It is the online register of data formats and structures provided for in Article 26(b) of Regulation (EU) 2023/2854 (Data Act) and includes the information required by Article 28 of that regulation. The switching and export rights are set out in section 22 of the Terms and Conditions. The page is updated whenever the format changes.
1. How to download your data
- The account owner: in the Account section, the "Export data" button. The file contains all the business data.
- An invited member: in the Account section, the "Export account data" button. The file contains the member's own data.
- The call log: from the Calls page, as a CSV file.
The export is free of charge. The full export can be requested at most 3 times per minute. To switch to another provider or to your own infrastructure, write to contact@liniadirecta.ro.
2. File format
The full export is a JSON file, encoded in UTF-8. Its top-level keys are the following, in the order they appear in the file:
| Key | What it contains |
|---|---|
exported_at | when the file was generated |
export_schema_version | the version of the file format |
ai_provenance | the fields with content generated by artificial intelligence (AI Act, Article 50) |
user | the account that requested the export |
client | the business data: profile, contact, billing, plan and usage |
assistants | the assistants’ configuration, with the team (staff), the services (services) and who provides which service (service_staff) |
call_logs | calls: transcripts, translations, summaries, extracted data, durations, cost |
appointments | appointments and booking requests |
chat_sessions | chat conversations: messages, translations, summaries |
call_audits | the automated checks of calls |
team | team members, their consent and active invitations |
invoices | the tax invoices issued, with the link to the document |
outbound_lists | uploaded call lists |
outbound_contacts | the contacts in the call lists |
outbound_suppressions | the numbers that no longer want to be called |
whatsapp_messages | WhatsApp messages sent to callers |
moderation_decisions | moderation decisions concerning the account, with their reasons |
- Dates and times are in ISO 8601 format, in UTC (for example,
2026-10-06T09:30:00.000Z). - The
ai_provenanceheader shows which fields contain text generated by artificial intelligence, with the legal basis and a link to the AI Transparency page. - The
export_schema_versionfield gives the version of this description (currently2026-10-06). - A category that could not be read when the file was generated appears as
{ "unavailable": true, "note": ... }, not as an empty list. If the assistants' team and services could not be read, theassistants_teamkey appears with the same marker. In that case, run the export again. - Each list is capped at 10,000 rows. If the cap is reached, the
truncatedkey shows which lists were limited, and the full export can be requested from contact@liniadirecta.ro.
The export of an invited member has the keys exported_at, user, membership (role, date of joining the team and consent), invitation (the accepted invitation) and decisions (the decisions taken on booking requests).
3. Call log (CSV)
The columns are: date, time, assistant, phone, duration (in seconds), outcome and summary, with the header in the interface language. The file is encoded in UTF-8 and uses ";" as separator, so that it opens correctly in Excel. Date and time are in Romanian time. The filters of the Calls page (period and assistant) apply, and the file contains at most 10,000 calls, the most recent ones.
4. What is not exported
The configuration you entered (business information, hours, services, team, your own instructions) is exported in full. Only data that belongs to the internal operation of the service or to its security, and what belongs to other accounts, are not exported:
- The service's internal instructions: the system instructions the platform generates from your configuration and references to internal templates. They are how the service works, not business data.
- Access secrets: access to Google Calendar, the secret used to sign automated notifications and the codes used to accept invitations. Exporting them would let someone else access the account or the connected services.
- Internal identifiers at providers: references at the payment processor, the telephone operator, the invoicing software, the messaging provider and Google Calendar, plus technical error codes. They have no meaning outside the service.
- What belongs to other accounts: the user identifiers of members and of those who made a decision, members' personal preferences (which appear in each member's own export) and the reference to a content report, which contains the reporter's data.
- Internal technical markers: when emails and reminders were sent, the call scheduler's counters and state, internal deadlines, retention markers and the account deletion log.
- Duplicates and technical metadata: the business identifier repeated on every row (it appears once, in
client), the position in lists (expressed by the order), the technical copy of the email address and the technical dates of some auxiliary rows. Accepted invitations appear as members, and revoked ones are not exported. - Abuse protection data: request rate limiting and anti-bot checks. They belong to the security of the service.
5. Jurisdiction of the infrastructure
The Provider, Digital Leadership SRL, is a company established in Romania. The database and the assistants’ server are in the EU, in Germany. Some providers are entities established in the US; for them, transfers are covered by the safeguards described in the Data Processing Agreement (DPA). The categories of providers are listed on the Sub-processors page.
6. Access by non-EU authorities
The Provider does not grant access to, or transfer, the Client's data to an authority of a country outside the EU except under the conditions of Article 32 of the Data Act (on the basis of an international agreement or of a decision recognised in the EU). When it receives such a request, the Provider checks its legal basis, provides only the minimum necessary and informs the Client beforehand, where the law allows it. Communications with the service are encrypted in transit, and the database and its backups are encrypted at rest (AES-256).