Wave Agency

Strategy and Leadership

Who Owns Your App? The Accounts to Keep in Your Name

Your domain, code, hosting and app store listings should sit in accounts you control. What to check, what to ask before a build, and how to fix it.

The developer who built your booking app has stopped answering email. The app still works, mostly. Then a customer reports that it will not open on the new iPhone, and you go looking for whoever can fix it. That is when you find out the app is listed in the store under the developer’s account, the code lives in their repository, and the server bill goes to their credit card.

You paid for the software. You may not control any of it.

Usually nobody meant any harm. A developer sets things up in their own accounts because it is faster on day one. Years later, that shortcut decides whether you can change vendors, fix a bug or even renew your own domain. It is easy to check, and usually easy to fix while everyone is still on good terms.

Paying for it is not the same as holding it

A finished piece of software is really a set of accounts working together: a domain, a hosting account, a code repository, a database, the store listings, the services that send email and take payments. Each of those has an owner on file, and that owner is whoever created the account.

If those accounts are in your business’s name, a developer is someone you have given access to. You can add a new one, remove an old one, and keep running. If they are in the developer’s name, you are a customer of your own software, and every change goes through them.

A contract that says you own the code helps. It does not give you the password.

The accounts to keep in your name

Here is the list to walk through for any website, app or custom system you rely on:

  • The domain. The registrar account where the domain is renewed. If the domain lapses or is moved, your website and often your email go with it.
  • Hosting and cloud. The account where the site or app actually runs, and where the bill goes.
  • The code. The repository that holds the source code, with its full history. A zip file is a snapshot; the repository is the working copy.
  • The database and its backups. Your customers, orders and records. Know where it lives and where the backups go, and test that a restore works. We covered how in backups you have actually tested.
  • The app stores. The Apple developer account and the Google Play account that publish the app. These are separate accounts from the code, and the listing, the reviews and the download history live there.
  • Payments. The payment processor account where money from the app lands. This one should never be anyone’s but yours.
  • Email and text sending. The service that sends receipts, reminders and password resets, and the sending domain tied to it.
  • Analytics and search. Your analytics and search console properties, so the history of your traffic does not leave with a vendor.
  • Design files and brand assets. The source files for the logo, the screens and the icons, not just exported images.

You do not need to understand each one to own it. You need the account in the business’s name, a login for someone you trust inside the business, and the developer added as a user rather than set up as the owner.

Questions to ask before a build starts

Ownership is easiest to settle before any account exists. Bring these questions to the first meeting with any developer:

  1. Whose name will each account be created in?
  2. Will you work in accounts we create and invite you to?
  3. Will the code be in a repository we own, with you added as a collaborator?
  4. What third-party services will the software use, and who pays for each?
  5. If we part ways, what exactly do we receive, and how long does the handover take?
  6. Who holds the passwords and two-factor codes for the main accounts?

A good developer will have clear answers and will not mind the questions. If a developer resists every one of these, that tells you something worth knowing before you sign.

These questions sit well alongside a written brief. Our guide to writing an app brief a developer can price covers the rest of what belongs in that first document.

If it is already set up in someone else’s name

Most owners reading this have software that already exists. Here is how to sort it out without a fight:

Make the inventory first. Go through the list above and write down, for each item, who the account belongs to and whether you can log in.

Ask while things are friendly. Moving accounts is far easier with a developer’s cooperation than without it. Frame it as housekeeping, which it is.

Move one thing at a time. Domains can be transferred between registrar accounts. Apps can be transferred between store accounts, though both Apple and Google set conditions on it, so read their current rules before you start. Code can be copied to a repository you own with its history intact. Do the domain and payments first, since those carry the most risk.

Change the keys afterward. Once an account is yours, review who has access, remove anyone who no longer needs it and turn on two-factor sign-in. The same habit from choosing software without regret applies here: count what it would cost to leave, before you need to.

A short self-check

Answer yes or no for the software your business depends on most:

  • We can log in to the domain, hosting and code ourselves today.
  • The app store listings are under our business’s own developer accounts.
  • Payments land in an account in our name.
  • We know where the data is backed up, and a restore has been tested.
  • If our developer disappeared tomorrow, someone new could pick up the work.

Every no is a task, not a crisis. Fix the riskiest first and work down the list.

How we help

We build custom web, mobile and enterprise software with an in-house team, from discovery through build and support after launch, and we manage the app store launch and updates for the iPhone and Android apps we build. We also take over existing projects: we audit what you have, stabilize it and extend it, which usually starts with exactly the inventory above.

Not sure who holds the keys to your software? Book a call and we will walk the list with you.

← Back to The Journal

Work With Wave

Put a good idea to work.

If something here is useful, let's talk about what it would look like for your business. A short call with a senior member of the team.

Book a Call