This page describes how you can port your data out of Lediv: the available procedures, the data structures and formats of all exportable data, the relevant standards, and known limitations. It carries the switching information required by Article 26(a) of Regulation (EU) 2023/2854 (the Data Act) and hosts the online register required by Article 26(b). It is referenced from Section 4 of our Terms of Service and forms an integral part of that agreement. We keep it up to date. Because this page forms part of your agreement with us, we give at least 30 days' notice of a material change to it, under Section 21 of our Terms of Service.
Switching and porting procedures
Export is self-service, per project, available at any time and on every plan (including the Free plan), and free of charge. There are no switching charges of any kind. From the app, "Download project" downloads the project as a ZIP archive containing all project files with their original paths. The ZIP is assembled in your browser from your local copy of the project.
To erase your data after porting it, delete the project in the app and empty the trash, or delete your account (see the Privacy Policy). Account deletion permanently purges the projects, content and assets you own, with one narrow exception explained there: where a domain of your own was provisioned for your published site at our infrastructure provider, we keep that domain name, an internal account reference and the date the connection was removed, so that only someone who can prove the domain is theirs may connect it afterwards. We keep that record for as long as the domain's DNS may still point at our infrastructure, which is not something we can see from our side. Once it no longer points at us, write to support@lediv.com: we check the DNS and delete the record.
Data structures and formats (register of exportable data)
All exportable data and digital assets, meaning every project you own and its files, documents,
assets and reusable components, are available in one structured, commonly used and
machine-readable format: a standard ZIP archive (ISO/IEC 21320-1) containing every file in the
project. Text files (HTML, CSS, JavaScript, JSON, Markdown and similar) are plain text
conforming to the relevant open standards (WHATWG HTML, W3C CSS, ECMAScript, RFC 8259 JSON).
HTML and CSS files are reformatted with a standard code formatter as they are written into the
archive; every other file is byte-identical to the copy you stored. All other files (images,
video, fonts, audio and any other assets) are included as their original binary files. A
package.json and vite.config.js are added when not already present, so
the export builds and runs locally with open-source tooling:
Vite and Lediv's
open-source build plugin (@lediv/vite-plugin), which compiles pages that use Lediv
components and expressions into plain static HTML.
An open interface is available too. The archive above is the route that carries
a project in full, assets included. Beyond it, every project you own can also be read
programmatically over the Model Context Protocol at https://lediv.app/mcp, using a
credential you issue from your account: the file tree, the text of every file, and the name,
type and size of every asset, with image bytes returned inline where the model can use them. The
protocol is an open specification and the interface is documented at
Connect Your AI Agent. It is available to every customer,
on every plan, free of charge, and to a destination provider you authorise with a credential of
your own, so that software can be written against it for the purposes of interoperability.
No harmonised standards or common specifications for interoperability of design-tool services are currently listed in the Union standards repository. If applicable ones are published, we will make the Service compatible with them within the required timeframe.
Known restrictions and limitations
- Project version snapshots are not included in the export, which reflects the current state of the project. They are left out of the ZIP because it is assembled in your browser from your local copy, which holds the current state only. They are your data, not ours, so whatever we still hold is available on request at support@lediv.com. Saving and restoring versions needs a paid plan; when a paid plan ends, the snapshots you already have are kept read-only and you can still delete them.
- The deploy history of a published site is not exportable data. It records which version of your site was live on our infrastructure and when, and it has no meaning on another provider, which publishes in its own way. Each site keeps the number of published versions your plan retains and the older ones are pruned, so once a version has been pruned it is gone and we cannot recover it. A change of plan triggers the same pruning: when a paid plan ends, the deploy history of every published site is pruned within a day to the version that is live and anything published after it, and that cannot be undone. None of this touches your project files, and the export carries the current state of the project either way.
- Published-site settings are not included in the export. If you publish a
project on Lediv, the export contains the project itself, not the way it is published: the
address the site answers on, whether it is kept out of search engines, and the domains you
have connected with their status and which one is the main address. This data is held in our
systems and is available on request at
support@lediv.com. Its purpose is to serve the site on
our infrastructure, and it has no meaning on another provider, which uses its own addressing
and its own domain configuration. The
_redirectsfile is a different matter: it is a file of your project, so it is in the export, and hosts that read the same file honor the same rules. - Data specific to the internal functioning of the Service (server logs, security and rate-limiting data) is not exportable.
- No size cap applies to the export itself. The ZIP is assembled in your browser from your local copy of the project, so open the project and let it finish syncing before you export: what the browser has not yet loaded cannot go into the archive. Very large projects are bounded in practice by the memory your browser can spare.
- Exporting a project shared with you follows its owner's plan. Every project you own is exportable on any plan. Where you are a collaborator rather than the owner, you can export a project shared with you while its owner holds the plan that gives you access to it; once that plan ends, only the owner can export it, so ask the owner for a copy.
Questions and assistance
For assistance with switching, exit strategies or bulk export, contact support@lediv.com. Information about the jurisdiction of our ICT infrastructure and the measures we take regarding governmental access to non-personal data is published in our Privacy Policy.