Quote data exports
Language notice: The German version of this document is the original version. This English version is provided to inform English-speaking users and is intended to accurately reflect the German version. In the event of any discrepancy, the German version shall prevail.
This Export Register supplements Section 13.1 of the Terms of Use available at www.tasia.io/terms. It describes the current data structures, data formats, applicable standards, access methods, available interfaces, open interoperability specifications and known technical limitations for exports and switching providers, insofar as the respective data and functions are available in the customer account.
This Register neither extends nor restricts the scope of export established in the Terms of Use and under mandatory law. In the event of any conflict, the Terms of Use and mandatory law shall prevail.
1. Access Methods
Exports are provided by at least one of the following appropriate and secure methods:
- existing export or download functions within the Service;
- an interface provided by Tasia for the export concerned;
- a documented and versioned public API, insofar as it is enabled for the relevant plan;
- an export provided upon request via support@tasia.io.
For a provider switch pursuant to Section 13.2 of the Terms of Use, Tasia shall, insofar as Article 30(2) of the EU Data Act applies, provide the Customer and the affected destination provider of data processing services, free of charge and to the same extent, with an open switching interface, including sufficient technical information and documentation. This interface does not depend on a plan that includes general API access and may be limited to the specific switching process.
Tasia may implement reasonable authentication, authorization, security and capacity measures, provided that they do not prevent, impede or delay the switch.
A complete export in connection with a provider switch does not depend on the Customer having subscribed to a plan with public API access. Not every data category must be retrievable through a self-service function in the user interface, provided that Tasia makes it available by another appropriate method without undue delay and without avoidable obstacles to switching.
Large exports may be generated asynchronously, divided into multiple archives or made available through time-limited download links. Tasia may require reasonable authentication and authorization checks before making them available.
2. Data Structures and Standard Formats
| Data structure | Content | Standard format |
|---|---|---|
| Account, organization and configuration data | Names, internal identifiers, settings, plan and organizational assignments, insofar as they are stored as the Customer’s product data | generally JSON; for tabular data, additionally or alternatively CSV |
| Users, roles and permissions | Business user details, roles, permissions and assignments, insofar as the Customer is entitled to receive them | JSON or CSV |
| Forms and request configurations | Forms, questions, response options, required fields, sequences, conditions, statuses and associated configurations | structured JSON; text in UTF-8 |
| Price, service and rule configurations | Services, line items, quantities, units, pricing rules, surcharges, discounts, dependencies and other customer-specific quotation logic | structured JSON; for tabular data, additionally or alternatively CSV |
| Requests and information from prospects or end customers | Contact, property, project, requirement, service, quantity, scheduling, response and status data, insofar as available in the customer account | JSON or CSV; free text in UTF-8 |
| Quotations and quotation drafts | Quotation master data, line items, quantities, prices, text, terms, deadlines, statuses, changes and approvals | structured JSON; where offered, additionally document-related or tabular formats |
| Files and attachments | Uploaded or stored images, documents, price lists, plans and other attachments | generally in the stored original format; assignment by path, file name, MIME type or an equivalent technical description |
| Stored AI outputs | Outputs stored by the user or incorporated into Tasia, including their assignment to a request, rule or quotation draft | JSON and, where applicable, text in UTF-8 |
| Approval, delivery, export, version and integration data | Statuses, times, recipient assignments, versions, export operations and integration assignments, insofar as they are stored as the Customer’s product data | JSON or CSV |
| Activity and audit data | Usage, activity, change and audit data, insofar as they are stored as the Customer’s product data and do not serve exclusively Tasia’s internal security or operation | CSV or JSON |
Where required for assignment, Tasia explains the structure of a specific export by means of a schema, mapping or manifest file, or an equivalent technical description.
The specific export contains only data that is available in the respective customer account and that the Customer is entitled to receive. Not every data category is necessarily generated under every plan or product configuration.
3. Formats and Standards
- JSON generally conforms to RFC 8259.
- CSV follows the widely used RFC 4180 scheme, where applicable.
- Text is generally provided in UTF-8.
- Time information is generally provided in accordance with ISO 8601.
- Archives are generally provided in ZIP format.
- Files are identified using customary MIME types.
A proprietary migration protocol is not required. Where an open interoperability specification or harmonized standard is mandatorily applicable to the data structure concerned, Tasia takes it into account in accordance with applicable law.
The API versions, fields, schemas, authentication procedures, quotas and known technical limitations made available in each case are additionally set out in the current API documentation or in the technical description provided with the specific export.
4. Non-Exportable Data
Unless mandatory statutory rights provide otherwise, the following in particular are not exportable:
- passwords, hashes, session data, private keys, API secrets, and payment and authentication tokens;
- data of other customers or third parties that the Customer is not entitled to receive;
- anonymized internal statistics for which no link to an individual or customer can be re-established;
- source code, models, model weights, algorithms, system instructions and internal evaluation logic of Tasia or third parties;
- internal security, infrastructure, legal, abuse-prevention and operational information, insofar as it is not the Customer’s product data;
- legally protected information whose disclosure would jeopardize third-party rights or the security of the Service.
Further details are set out in Section 13.1 of the Terms of Use.
5. Technical Limits and Known Restrictions
An export does not include content from external services, data that has already been deleted or is no longer available, copies in search engines or third-party archives, or third-party content that is merely linked.
Transfer to a destination system may require mapping, conversion, cleansing or adjustment by the Customer. Tasia is not obliged to set up, configure or test the functionality of the destination system and does not owe complete functional equivalence with that system.
Due to their size, quantity or technical nature, exports may be distributed across multiple files or archives, generated asynchronously or provided through time-limited download options. Reasonable security, authentication, authorization and capacity measures remain permissible.
Files and content can be exported only to the extent that they are stored by Tasia and technically available. Tasia cannot ensure deletion, disclosure or transfer from systems that are not controlled by Tasia.
6. Updates and Versioning
Tasia keeps this Export Register permanently available at www.tasia.io/export and updates it when material changes are made to data structures, formats, standards, access methods, interfaces or technical limitations.
Changes are documented with a date and version identifier. They may not impermissibly restrict the scope of export required by contract or law. Historical versions are retained in accordance with Tasia’s internal documentation and evidence procedures.
Questions concerning a specific export or provider switch may be directed to support@tasia.io.
Last updated: 01 August 2026
