Who Owns an App Built With AppCub?
The code, the data, the signing key and the Google Play listing: what belongs to you when you build an app with AppCub, and what we keep.
Imran Choudhary · · 4 min read
Business owners who have worked with an app agency often ask us the same question first: if I build my app with AppCub, is it really mine? Can I take it somewhere else? Who sees my customers' data?
The short answer is that the app, its code and its data are yours. This post explains each part, with links to the terms and the privacy policy where the details are written down.
The code
Your ideas, your messages, and the code and files AppCub generates for your projects belong to you, as far as the law allows. Every file is visible in the Code tab while you build. You can download your code and build files and use them without AppCub, for example with a developer you hire later.
You can also connect your own GitHub account, and AppCub keeps a copy of your app's code there.
The apps are written in Flutter, a widely used open-source framework from Google. Any Flutter developer can open the project, read it and continue working on it.
Your customers' data
By default an app built with AppCub keeps its data on the phone it is installed on. The data stays on that phone.
When an app needs shared data, for example two staff phones seeing the same bookings, or customers signing in, you connect your own Supabase project from the chat. Supabase is an online database with a free plan. Your app's tables and sign-in are set up in your Supabase account, so your customers' data is stored there, under your control, and not on AppCub's servers.
Payments work the same way. If your app takes payments, you enter the two keys of your own Razorpay account. AppCub stores them encrypted and sets them up in your own Supabase project. The money goes to your Razorpay account.
The signing key
Every Android app is signed with a key, and Google Play only accepts updates signed with the same key. Lose it and you cannot update your app.
AppCub creates a signing key for each of your apps and keeps it securely, so every update you build carries the same key. On request we give you a copy of your app's key. If you publish on Google Play, we recommend turning on Google Play App Signing as well, so Google also holds a copy.
The Google Play and App Store listings
Your app is published from your own Google Play developer account, in your name. You pay Google's one-time US$25 registration fee directly to Google and complete its identity check yourself.
If you ask our team to do the Google Play steps, you invite us to your account from Play Console. You never share your Google password with us, and we do not publish apps under our own account, even when asked. The same applies to the iPhone launch: the Apple developer account is yours, and you invite us to it.
That way the app's reviews, downloads and earnings stay with you, whether or not you keep using AppCub.
What AppCub keeps, and for how long
To build your app we store your account, your projects and your build files. They are stored on Amazon Web Services in Mumbai, India. To plan and write your app, AppCub sends your project to Google's Gemini models through Google Cloud Vertex AI. Under Google Cloud's terms this data is not used to train Google's models, and we do not use your projects to train models either.
We do not sell your data, do not show ads and do not track you across other apps or websites.
You can delete your account at any time from Settings, then Delete account. Your account and projects are deleted within 30 days, server backups are overwritten within 7 days, and older backups of signing keys within 90 days. Download your code and ask for your signing key before you delete your account.
What stays your responsibility
Owning the app also means being its publisher. AI-generated code can contain mistakes, so review and test your app before you share it. You are responsible for what the app does, for following Google Play's policies, and for your own app's privacy policy, which AppCub drafts for you to check.
In one table
| What | Who it belongs to | Where it lives |
|---|---|---|
| App code | You | AppCub, and your GitHub if you connect it |
| Customers' data | You | The phone, or your own Supabase project |
| Payments | You | Your own Razorpay account |
| Signing key | You, with a copy on request | Kept securely by AppCub |
| Google Play and App Store listings | You | Your own developer accounts |
If anything here is unclear, write to support@lagnevertech.com. To see how AppCub builds the app itself, read how AppCub turns a chat into a working Android app.