Effective 2026-11-15
This page explains how to take your data out of Kubi and move to another provider or to your own servers. It puts section 12 of our Terms of Service into plain words and gives the information the EU Data Act asks cloud providers to publish. If this page and the Terms ever differ, the Terms win.
1. Who this covers
1.1 These rules apply to every Kubi customer, wherever you are. They follow Chapter VI of the EU Data Act (Regulation (EU) 2023/2854), which covers cloud services offered in the EU, and we run the same process for everyone.
1.2 Free trials and credit-only Accounts get the same export tools and the same help.
1.3 This page explains section 12 of our Terms of Service, which are the binding text.
2. What you can take with you
2.1 You can take all of the following, and this list is complete (Terms 12.3):
| Data | What it covers | How to get it |
|---|---|---|
| Screen disks | Everything stored on each Screen's disk, as one disk image | Dashboard: a download link that works for 7 days, also sent by email |
| Files you uploaded | Files you sent to Kubi for your Screens | Dashboard, API or SDK |
| Screen settings | The settings you chose for each Screen | Dashboard, API or SDK |
| History and saved screenshots | Each call on a Screen and the screenshot it returned, for the 30 days we keep them | Dashboard or API |
| Account and Team Member data | Names, emails and roles in your Account | Dashboard, as one JSON file |
| API keys | Each key's name and details | Dashboard, in the same JSON file |
| Usage and billing records | Your usage records, invoices and receipts | Dashboard; invoices and receipts come from Stripe |
2.2 We store API key secrets only as hashes, so an export lists your keys but can't show the secret itself. Create new keys at your new provider.
2.3 A disk export contains the operating system and all software on the disk. Open-source and third-party software keeps its own license (Terms 13.1), and the list of components and how to get their source code is at open source notices URL (Terms 13.1). You remain responsible for the licenses of software you installed (Terms 4.5).
2.4 We don't hand over our security detection rules, signals about abuse involving other customers, our source code or the configuration of our infrastructure (Terms 12.3). They are our trade secrets, and none of them is needed to run your data somewhere else, so leaving them out never slows your move.
2.5 We can't export what we don't keep. We never store the live view, history and its saved screenshots are kept for 30 days (Terms 8.4), and our recovery copies of Screens are not a backup service (Terms 8.5).
2.6 Your rights over your personal data under our Privacy Policy, such as getting a copy in a machine-readable format, apply on top of this page.
3. Formats and standards
3.1 This table is our register of export formats. We keep it up to date.
| Data | Format | Standard or specification |
|---|---|---|
| Screen disks | one qcow2 image behind a download link that works for 7 days | QEMU's qcow2, which qemu-img converts to raw or VMDK |
| Files you uploaded | Original files, unchanged | Same format you uploaded |
| Screen settings | JSON | Described in the Documentation |
| History | JSON | Described in the Documentation |
| Saved screenshots | The images as returned | PNG, WebP or JPEG |
| Account and Team Member data | JSON | Described in the Documentation |
| API keys | JSON | Described in the Documentation |
| Usage and billing records | CSV, PDF invoices | Described in the Documentation |
3.2 Our API, SDK and MCP server are described in the Documentation at API reference URL. Anyone can read it free of charge, including a provider you move to, so they can build tools that read your exports.
3.3 What moves as is, and what needs work:
- Moves as is: the files, apps and data on your Screens' disks, which are standard Linux file systems.
- Needs adapting: your Screen settings, and code or Agent setups written for Kubi's API, SDK or MCP server, which you'll point at your new provider's tools.
- Rebuilt elsewhere: features of the Kubi service itself, such as the dashboard and the live view. They aren't data, so there is nothing to export.
3.4 To help you set up an equivalent machine elsewhere, each Screen's settings export includes its machine description: CPU count, memory, disk size, operating system image and version, and location. A provider that offers Linux virtual machines can run the same operating system and files. If you need help matching it, email support@trykubi.com.
4. How to export
4.1 You can export at any time through the dashboard, the API or the SDK (Terms 12.1). You don't need to tell us or ask permission.
4.2 Known limits: known export limits.
4.3 Exports are free, including the data transfer they use (Terms 12.5).
4.4 Exporting regularly is a good habit even if you're not leaving, because our recovery copies of Screens are not a backup service for you (Terms 8.5).
4.5 Moving to Kubi. To bring data from another provider or your own servers, upload files to a Screen through the dashboard, API or SDK, or copy them over the network from inside the Screen with standard tools such as rsync or scp. Importing whole disk images is not supported at launch. Section 4.2 lists the known limits.
4.6 Planning ahead. You can ask support@trykubi.com at any time, not only when you're leaving, for what you need to plan an exit, such as the size of your Screens' disks and the formats and limits for your Account (Terms 12.2).
5. How to switch or leave
5.1 To move to another provider or to your own infrastructure, or to have your data erased, email support@trykubi.com from the Account owner's email address (Terms 12.2). Tell us:
- whether you want to switch to another provider, move to your own infrastructure, or have your data erased;
- if you're switching, which provider you're moving to, so we can help;
- which Screens are involved, or whether it's the whole Account; and
- whether someone else, such as your new provider or a contractor, will do part of the work, with their contact details.
5.2 Terms 12.2 and 12.4 set out what happens next. At a glance:
| Step | When | What happens |
|---|---|---|
| You ask | Any day | We start at once and confirm the dates by email |
| Transition period | Up to 30 days | The Service runs; we help you and anyone you authorize |
| Your extension | Once, for as long as you need | Ask before the transition period ends |
| Longer if needed | Up to 7 months | We tell you why within 14 working days |
| End of the Terms | When the move is done, or on our erasure date | We confirm by email |
| Retrieval Period | 30 days | Download what's left, or waive it |
| Erasure | When the Retrieval Period ends | We erase your data, except what the law makes us keep |
| Disk copies | 7 days | Old copies expire |
| Database backups | 14 days | Old copies expire |
5.3 The same Retrieval Period applies however your Account ends: when you cancel (Terms 10.7), when we end the Terms (Terms 11.3), and when a payment stays unpaid, in which case the 30-day pause is the Retrieval Period (Terms 10.6). Terms 12.4 covers Accounts we close for illegal content, a security threat or a legal order.
5.4 You can move only some of your Screens and keep using Kubi for the rest. Name them in your request (5.1 item 3), and the same help and transition period apply. When you tell us their move is complete, those Screens stop and no longer renew, and you have the 30-day Retrieval Period for anything left on them, unless you delete them sooner yourself. The Terms continue for your other Screens.
5.5 You can also close your Account yourself in the dashboard (Privacy 11.2). This works like an erasure request: the Terms end, the 30-day Retrieval Period starts unless you waive it, and then we erase your data and email the Account owner to confirm it. Business customers can also ask for a written deletion certificate (DPA 2.5).
6. Fees
6.1 We don't charge for exports or switching, and there are no early termination fees (Terms 12.5). Plans run month to month, and you can cancel at any time in the dashboard (Terms 10.7).
6.2 Normal Fees continue for Screens you keep running during the move (Terms 12.2). They are your usual service fees, not a charge for switching. Prices are on the Pricing Page.
6.3 The Data Act lets providers charge reduced switching fees, limited to their direct costs, until 12 January 2027, and bans switching charges from that date. We don't charge them at all, before or after.
6.4 We know of no part of Kubi where switching is especially complex or costly. Large disks take longer to copy; section 4.2 lists the known limits.
6.5 You can also run Kubi alongside another provider and move data between them while you use both (Data Act Art. 34). Exports through the dashboard, API or SDK stay free and never count toward your Screens' limits (Terms 12.5). Other traffic between a Screen and that provider counts toward the data transfer included with each Screen (Terms 4.2). If we ever charge for traffic beyond it, a charge for traffic to a provider you use alongside Kubi never exceeds our own cost.
7. Where our infrastructure is and which laws apply
7.1 Screens, our main database and our backups run in the EU by default, in France and Germany: Screens in data centers run by Ikoula, the main database at Hetzner, and backups, saved screenshots and disk exports at Scaleway. Each Screen runs in the location shown when you create it, and we don't move Your Content to another country without telling you first, unless an emergency or the law requires it (Terms 4.1).
7.2 That infrastructure is subject to EU law and the law of the country where each data center is. Kubi is provided by Arthur Katcher, doing business as Kubi, who runs Kubi's systems remotely from Serbia and bills through a Canadian payment account, so the laws of Serbia and Canada can also reach us. Once Kubi is run by a US company, US law will apply too, and we will update this section first. Stripe processes payment data in the US (Privacy Policy 8.2).
7.3 How we protect data held in the EU against government access that would conflict with EU law or the law of an EU country:
- Technical: Screens and their data stay in the EU location you chose; Screen disks, recovery copies, database backups, saved screenshots and disk exports are encrypted at rest; each Screen runs in its own virtual machine; administrative access is limited, and every time a person opens a Screen is logged (Terms 8.3).
- Organizational: we disclose data only when the law requires it and after a reasonable check that the request is valid, and we tell you unless the law forbids it, it would put someone at risk, or, for as long as needed, it would defeat a criminal investigation (Terms 7.5). When a request from outside the EU would conflict with EU law or the law of an EU country, we get legal advice before acting, challenge it where we have reasonable grounds, and never disclose more than a valid order requires.
- Contractual: our subprocessors are bound by contract, and we remain responsible for their work (DPA 2.3); for personal data, our DPA sets the rules.
7.4 This section is the information that Terms 12.5 refers to, and the Trust Center links here.
8. Business use
8.1 Kubi is for business use only, so everything on this page applies to every customer.
9. Changes and questions
9.1 We keep this page up to date. Every version stays online with its date.
9.2 Questions about exports or switching: support@trykubi.com. Legal notices: legal@trykubi.com.
9.3 You can download the Terms, the DPA and this page as PDF files at trykubi.com/legal, before you sign up and at any time after, so you can store and print them. Each version keeps its date (Terms 16.2).
Arthur Katcher, doing business as Kubi, postal address
