Terms of service

1. Who we are

Unbase44 is operated by Codama Advanced Engineering, Inc. (“Codama”, “we”, “us”), a Delaware corporation with its registered office at 8 The Green, Ste A, Dover, DE 19901, USA. You can reach us at hello@unbase44.com.

These terms cover the website at unbase44.com, the Unbase44 app where migrations are set up and run, and the migration service itself (together, the “Service”). Our privacy policy explains how we handle personal data and forms part of these terms.

2. What the Service does

Unbase44 moves an app built on the Base44 platform onto accounts you control. With your permission it reads the Base44 app you choose, analyses it, shows you a price, and then, if you go ahead, copies the app’s code, data, users, files and configuration into a GitHub repository, hosting, database and other services in accounts you own, and deploys it there.

Unbase44 is independent. It is not affiliated with, endorsed by or sponsored by Base44 or Wix.com Ltd. The Service relies on Base44’s interfaces, which Base44 can change at any time; if a change affects a migration, we will tell you what it means for your app.

3. Your account

You must be at least 18 and able to enter a binding contract, and if you use the Service for an organisation, you confirm you are authorised to accept these terms on its behalf. You sign in to Unbase44 through Base44’s own sign-in, and you are responsible for activity under your account.

4. Your right to move the app

By starting a migration you confirm that:

• you own the Base44 app, or are authorised by its owner to copy and move it;
• you have the right to copy its code, data, user records and files to the destination accounts you choose;
• moving the app is consistent with the agreements that apply to it, including Base44’s terms and any promises you have made to your own users.

You are responsible for your app and its data, including the personal data of your app’s users. When we process that data during a migration, we do so on your behalf and on your instructions, as described in our privacy policy.

5. How we access your Base44 app

You grant access through Base44’s own device sign-in: Unbase44 shows you a code, and you approve it on Base44, where it appears as a sign-in for Base44’s command-line tool. We never see your Base44 password. We use that access only for the apps you select: to analyse and migrate them, and for the follow-up tasks you ask for, such as copying new data after the move.

The access Base44 grants could change your app, but we use it only to read, with one exception that we disclose before it happens: to copy the values of your app’s secrets, which Base44 does not otherwise reveal, we may add a small temporary helper function to your Base44 app, use it to read the values, and remove it straight away. If that isn’t possible on your plan, or you prefer it not to happen, you can type the values in yourself and nothing is added. Apart from this we do not change your Base44 app’s code, data or settings.

You can end our access with “Revoke access” on your app’s live page once it has moved, or by writing to us at any time. You can also revoke it from your Base44 account wherever Base44 provides that option.

6. Your provider accounts and credentials

A migration deploys your app to services you choose, such as GitHub, a hosting provider, a database provider, file storage, an email provider and an AI provider. You open or connect those accounts, and you give us credentials so we can create and configure what your app needs.

• You authorise us to use those credentials to set up and deploy your migration, and to carry out follow-up actions you request, such as connecting a custom domain.
• We store credentials encrypted and use them only for those purposes. “Revoke access” on your app’s live page deletes all of them, together with the other keys we hold for your app; before your app is live, write to us and we will delete them. You can also revoke them with the provider at any time; your running app does not need us to hold them.
• When your app runs on Railway, we also create a deploy token in your Railway project and add it to your GitHub repository, so that pushing a change deploys it. We keep our copy encrypted and delete it when you revoke access; the token itself stays in your accounts, where you can remove it.
• Those services are provided by third parties under their own terms, and they bill you directly. You are responsible for their charges and for keeping those accounts in good standing.

7. Price, payment and our guarantee

One-time price per app. We show you the price for a migration after analysing your app and before you pay or connect any accounts. The price is for that app as analysed; if the app changes significantly before the migration runs, we may ask to analyse it again. Optional extras, where offered, are priced in the same quote.

More than one app. A second app gets 25% off its quoted price, and each app after that 50% off, as shown in your quote.

Beta. While the Service is in beta, migrations are free. A migration you start during the beta stays free, including the follow-up actions on its live page. We will give notice on the website before paid migrations begin.

If the migration fails, you don’t pay. Once paid migrations begin, if we cannot deliver a working migration of the app described in your quote, you will not be charged, or, if you have already paid, we will refund you in full. Before we start charging, we will add to these terms how to ask for a refund.

Once paid migrations begin, payments will be handled by a payment processor that we will name in our privacy policy first. Prices are in US dollars and may exclude taxes, which are added where the law requires.

8. What you receive, and who owns it

Your app’s code, data and content remain yours. We claim no ownership of them, and we don’t use them to train AI models.

The repository we deliver also contains the Unbase44 runtime, the backend that lets your app run outside Base44 (in the server folder), together with deployment files and documentation. We license all of these to you under the MIT License, included in the repository as server/LICENSE: you can use, modify, copy and deploy them however you like, without time limit.

9. Your users’ passwords

Base44 does not release password hashes. So that your users can keep their passwords, the migrated app checks each user’s first sign-in against your Base44 app once and then stores its own secure hash. This check runs from your own server; we never receive your users’ passwords. It only works while your Base44 app remains published, so keep it available until your active users have signed in to the new app.

10. Acceptable use

You agree not to:

• migrate an app you don’t have the right to copy, or use the Service to access anyone else’s data;
• use the Service for anything unlawful, or to build or move an app that is unlawful;
• interfere with the Service, probe it for vulnerabilities without our written permission, or overload it;
• resell the Service without an agreement with us.

11. Changes to the Service

We are improving the Service continuously, and features may change. Features we describe as “coming soon” are plans, not commitments, and are not part of what you pay for until they are available.

12. Our commitments, and their limits

We will provide the Service with reasonable care and skill. Beyond that, and to the extent the law allows, the Service is provided “as is”. We do not promise that a migrated app will be free of defects, that it will behave identically in every case, or that third-party services will stay available. Test the migrated app before you move your users to it, and keep your own backups.

13. Limitation of liability

To the extent the law allows, we are not liable for indirect or consequential losses, such as lost profits, revenue or data, and our total liability for any claim relating to the Service is limited to the amount you paid us for the migration concerned in the twelve months before the claim, or US$100 if you paid nothing. Nothing in these terms limits liability that cannot be limited by law.

14. Indemnity

You will compensate us for third-party claims arising from your app, its data, or your breach of these terms, including a claim that you did not have the right to migrate an app.

15. Ending the agreement

You can stop using the Service at any time and ask us to delete your account by writing to us; we delete it within 30 days. We may suspend or end your access if you breach these terms or if we have to for legal reasons, and we will tell you why unless the law prevents us. When your account ends we delete stored credentials and account data as described in the privacy policy. Apps already migrated keep running: they live in your accounts, not ours.

16. Changes to these terms

We may update these terms. We will change the date at the top, and for material changes we will give notice by email or in the app before they take effect. A migration you have already paid for continues under the terms that applied when you paid.

17. Governing law

These terms are governed by the laws of the State of Delaware, USA, without regard to its conflict-of-law rules, and the state and federal courts located in Delaware have jurisdiction over any dispute. If you are a consumer, you also keep the protection of the mandatory laws of the place where you live.

18. Contact

Codama Advanced Engineering, Inc., 8 The Green, Ste A, Dover, DE 19901, USA. Email: hello@unbase44.com.