Switching provider and data porting¶
Version 1.0 · effective from 15 August 2026 · AITY CLOUD SRL
The information and procedure are provided by AITY CLOUD SRL, a Romanian limited liability company with its registered office at SACEL no. 1003, Săcel Village, Săcel Commune, Maramureș County, postal code 437290, Romania, tax ID 39458128 (VAT RO39458128), Trade Register J2018000824245, EUID ROONRC.J2018000824245, subscribed and paid-up share capital RON 5,000, correspondence address Str. Heliade Între Vii no. 35, postal code 023382, Sector 2, Bucharest, Romania, telephone +40735850896 (Monday-Friday, 09:00-18:00 Romanian time), e-mail office@aity.ro. The Romanian and English versions are both official; in case of divergence, the Romanian version prevails.
This page describes the Exportable Data, formats, interfaces, limitations, and procedure applicable to the aity Platform and aity Cloud data processing services. It supplements article 5^1 of the Terms and the DPA.
1. Submit a request¶
We confirm receipt and the registration number by e-mail. If the form is unavailable, send the same data to office@aity.ro.
2. Data and formats¶
| Service/category | Exportable Data and Digital Assets | Interface or format |
|---|---|---|
| aity Platform - e-mail | Messages, attachments, folders, and standard metadata | IMAP/TLS; MIME/RFC 5322 messages through the selected client |
| aity Platform - contacts | Available contacts and standard fields | CardDAV and vCard |
| aity Platform - calendars | Available calendars and events | CalDAV and iCalendar |
| aity Platform - files | Files, folders, and versions made available to the Customer | Download in native format, WebDAV, and the available open interface |
| aity Platform - account structure | End Users, roles, quotas, and metadata administered by the Customer | CSV and JSON |
| aity Cloud - object storage | Objects and metadata accessible to the Customer | S3-compatible API and native object formats |
| aity Cloud - Kubernetes | Customer manifests, configurations, and access information | Kubernetes API, YAML/JSON, and kubeconfig; Provider secrets are not exported |
| aity Cloud - compute and block storage | Instance configuration, volumes, and images created by the Customer | JSON/CSV inventory; QCOW2 or RAW images where image export is technically available |
| aity Cloud - network and DNS | Managed networks, addresses, rules, load balancers, and DNS zones | JSON/CSV; BIND zone file for DNS |
| aity Cloud - consumption and billing | Available detailed consumption, aggregates, invoices, and credits | CSV, JSON, and PDF for tax documents |
If no standard applies, we supply the data in a structured, commonly used, and machine-readable format. Passwords, private keys, and internal secrets are not exported; the Customer creates new credentials at the destination. Images or components licensed by third parties are ported only within the limits of the applicable licence.
3. Excluded internal data¶
Only internal data necessary to operate and protect aity is excluded, such as internal security telemetry, anti-fraud and anti-abuse rules, analytics derived exclusively for capacity, aity code and tools, trade secrets, and other customers' data. Exclusion will not prevent or delay switching and does not include data created directly or indirectly through use of the Service that the Customer needs for continuity.
4. Procedure, periods, and assistance¶
We verify the requester's authority and agree the scope, destination, and date. The notice period does not exceed two months. The Technical Transitional Period is no more than 30 days, subject to the justified and notified extension specified in the Terms where porting is technically unfeasible. Completion is followed by a Retrieval Period of at least 30 days, then deletion and backup rotation under the Terms and DPA. We communicate known risks, maintain security, and provide confirmation of completion and, upon request, deletion.
AITY CLOUD SRL charges no separate switching or porting fee. Fees remain due for Services and ordinary network traffic actually supplied, as well as any early termination cost disclosed before contracting and permitted by law.
5. Interoperability and equivalence¶
For aity Cloud, we take the reasonable measures within our power to achieve functional equivalence with a service of the same type. For aity Platform, we provide the open interfaces above and necessary technical information to the Customer and destination provider on equal terms and free of charge. The Customer and destination provider are responsible for compatibility of the destination system, transformations outside aity's control, and validation of data after import.
6. Jurisdiction and international governmental access¶
Customer Content stored at rest is kept on infrastructure in the EEA, subject to Union law and the law of the applicable Member State. AITY CLOUD SRL uses access control, privilege minimization, logging, cryptographic measures appropriate to the flow, and legal review of binding requests. We challenge manifestly unlawful or disproportionate requests where permitted by law, disclose only necessary data, and inform the Customer before disclosure unless prohibited from doing so. Every infrastructure partner is subject to equivalent obligations and identified in accordance with the DPA.
Version history¶
| Version | Date | Changes |
|---|---|---|
| 1.0 | 15 August 2026 | First published version. |