Additional Product Terms

1. About these terms

These Additional Product Terms apply when you use the features they describe, and are part of the Terms of Service. If they conflict with the Terms on the subject they cover, these win. Prices and limits referred to here are the ones shown in the app when you use the feature.

2. App hosting: Preview

Apps you build get a database, file storage and a Preview website that we arrange with our infrastructure providers. The Preview is rebuilt after each change and is meant for building and testing, not for running your app for the public. It is publicly reachable, but it limits how many different visitors can open it each day, and it may be slow, show a pause page, change without notice, or be unavailable.

Your plan includes a limited number of apps. More app slots cost credits each month while you keep them, and if your balance cannot cover a slot when it renews, the slot ends (your apps keep running, but you cannot add another until you are back within the limit).

3. Live apps and their billing

Going Live. Go Live publishes a separate Live website for your app that changes only when you choose to update it. It requires an active paid plan. The Preview and the Live site share one database, so changes made while testing the Preview can affect your Live app's data.

Billing. A Live app is billed monthly in credits to the app's owner. The first month is charged when you go Live, before anything is published. Each renewal charges the monthly base price plus any usage above the included allowance (database size, file storage and function calls), up to the monthly spending limit set for the app. Only the owner pays; a collaborator's request to go Live waits for the owner to approve and pay.

If a renewal cannot be paid. We give a grace period of about 7 days with reminders. If it still cannot be paid, the Live site shows a paused page until you resume it, which charges the month again. Your Preview, data and code are not removed by a pause.

Taking an app offline. You can take a Live app offline at any time. It goes offline at the end of the month already paid for, and there is no refund for the rest of that month.

Your app, your users. We generate basic privacy and terms pages for Live apps as a starting point only. You are responsible for making them accurate and sufficient for your app, and for everything else Section 7 of the Terms says about your apps' users.

4. When your plan ends

If your paid plan ends or a payment fails, your apps' Preview and Live sites show a paused page. If the plan is not restored, after about 7 days we may save a snapshot of each app's data and files, check it, and then remove the app's database. Snapshots are kept for about 12 months, and an app can be restored from one when you start a plan again. Your code is kept. Restoring is provided on a best-effort basis, and anything added after the snapshot, or not captured by it, may not come back. Downloading an app's code or data needs an active plan, so after a plan ends, start it again first.

5. Custom domains

You can connect a domain you own to a Live app. You are responsible for registering and renewing the domain with your own registrar and for its DNS settings. We attach the domain and request a security certificate for it only once its DNS points correctly, and we may detach it if it stops doing so, if it is used to break our Usage Policy, or when the Live app goes offline. Do not change or remove your domain's email (MX) records when you connect it. We are not responsible for downtime, email problems or certificate failures caused by DNS changes or by your registrar or DNS provider.

6. App store publishing service

The optional "Get it on the app stores" service is hands-on help from our team preparing and submitting your Live app to Apple's App Store, Google Play, or both. It is priced per platform when you buy it (currently $100 for the App Store and $100 for Google Play), plus applicable taxes.

• Your own developer accounts. Apps are published under your own Apple Developer Program membership (charged by Apple, currently US$99 a year) and Google Play developer account (currently a one-time US$25), which you open, pay for and keep. They are separate from what you pay us.
• Non-refundable. The service fee is non-refundable once paid, including if a store rejects or removes the app, delays review, or changes its rules.
• No guarantee. Apple and Google decide whether to accept an app. We do not guarantee approval, a review time or a launch date. Times we give are aims, not promises.
• Your information. You must complete the intake form accurately, and you are responsible for your app's store listing, content, privacy answers and compliance with the stores' rules, and for keeping the app compliant after it is published.

7. Connecting an existing app

When you connect an app you already have on GitHub, Co-Create copies its current code into a new private repository that we host for your project. We only read your original repository; we never write to it, and we do not copy its history or its automated workflows. You confirm you have the right to copy that code and to let us change it. Some kinds of apps can be edited but not previewed or hosted by Co-Create, and the app says which.

If you sign in with GitHub to connect a private repository, we store the access token encrypted and use it only to read the repository you choose to connect. As soon as the import finishes, we revoke the token at GitHub and delete it, so Co-Create keeps no access to your GitHub account; a later import asks you to sign in again. Until then you can disconnect it on the Connect an external app screen, which also revokes it, and deleting your account revokes it too.

8. Outside services and keys for your apps

Some features need an account or API key with another company (for example, a maps, email or AI service). You sign up with that company yourself, under its terms and prices. Keys you give us are stored encrypted and made available only to your app's own server functions, never to its public code. When you save a key we check it with the provider, but only at addresses we trust: a key for a service whose address we have not verified is saved without a check, and the app tells you so. Setup guides are provided to help and may be out of date. You are responsible for charges a provider makes for your key, including those caused by your app's users or by builds you approved, so we recommend a key limited to what the app needs and a spending limit with the provider. Removing a key from Co-Create does not cancel it with the provider; delete it there too.

A value whose name starts with a public prefix (such as EXPO_PUBLIC_, NEXT_PUBLIC_ or VITE_) is built into your app's public code, where anyone can read it. We warn you when such a value looks like a secret key, but it is your choice to keep it public.

Builds may add open-source packages to your app. We check new packages against basic safety rules before they are merged, but we do not guarantee any package is secure, maintained or licensed for your use.

9. App data backups, restore and rollback

Before some changes that could remove data, Co-Create backs up your app's data inside your app's own database and keeps the backup for a limited time. You can restore it from the App panel; a restore first saves a copy of the current data. Rolling back your app's code to an earlier point creates a new version of the code and does not change your app's database. Backups, restore and rollback are provided on a best-effort basis, may not capture everything, and are not a substitute for your own backups (see Section 8 of the Terms).

10. Duplicating projects and apps

Duplicating a project can create a new copy of its app. When the app's owner duplicates it, the copy can include the app's data, files, sign-in accounts and saved keys; anyone else's copy gets the code and sample data only. You are responsible for having the right to copy any personal data in an app, and for how the copy is used. A copy counts toward your app limit and is billed like any other app.

11. Collaborators and shared projects

The owner of a project decides who has access, and can remove collaborators. Collaborators can see and change what the project holds, including its chat, and may start builds that use their own credits. A project's owner is responsible for the app it builds, and for the people they invite.