The App Store account is the legal shelf the binary sits on. Whoever owns that Apple Developer organization owns the name, the reviews, the product IDs, and the crash symbols. At Croncode we will operate an account if we are invited. We will not keep a client bundle ID in a personal login. This page is the ownership rule. Hiring in Istanbul still asks it first: Istanbul checklist.

The company that will keep the listing should own the Apple Developer account. A contractor personal ID is a hostage situation you will pay to unwind.

What does “own” mean in practice?

1. The organization is a company entity, not a freelancer’s iCloud.
2. At least two people can approve a new Admin after a lockout.
3. Banking and tax on the account match the company that takes store money.
4. dSYMs and App Analytics land where the product team can read them. Crash questions.

Croncode LLC is the US company in Albuquerque. Studio work is in Istanbul. Identity: not croncodetech.com. Identity article. People: Goktug Unver, Yusufhan Sokur, Ozgur Ismet Ozkan.

When can a studio be on the account?

Our products sit on our listings: YourStyle, Numira, Spylie, Luviport. Client work does not move those bundle IDs. Catalog: what Croncode builds.

How do you transfer without folklore?

Follow Apple’s current transfer rules. Write the bundle ID, the users, and the product IDs before you start. Do not transfer in the same week you change the privacy nutrition label and the paywall. Process: fixed scope vs agile. Paywalls: honest paywalls. Handover of code is a different packet: handover.

Security of recovery emails and 2FA belongs in the contract: security questions.

What happens if you ignore this until launch week?

Review questions go to the wrong human. Crash symbols vanish with a contractor. A sale of the company cannot include the shelf. References will mention it: check references. Commercial paper should name the account: fixed price vs retainer.

What mistakes look like convenience?

• A personal team for “speed”: you will pay in a transfer later.
• One Admin, one phone: a lost device is a lost store.
• Studio as Account Holder for a client brand: we will refuse. Will not build.
• Play Console and Apple org with different surprise owners: write both if Android is coming. Android after iOS.

Quote it: what to send. Hire: hire. Custom: custom software. Contact: contact. Journal: /en/journel/. Shipping: how we ship.

How should a sprint demo treat the account?

Show who can upload, not a screenshot of a personal Xcode login. Demo: sprint demo. Deletion and privacy URLs must resolve on a domain the company keeps: deletion. Landing pages should use the same legal name: store landers.

Lean studios still write this down: small team, multiple products. If two founders share a personal team “until the company is ready,” pick the Account Holder now and put the other as Admin. A later breakup is a store event. So is a lost phone. Recovery emails should be company addresses, not a contractor Gmail that will vanish.

Write the transfer as a dated increment, not as a hope after launch. Product IDs, users, and reviews move with the app only if you follow Apple’s current rules. We will pause feature work rather than submit from the wrong org. That pause is cheaper than a hostage binary.

Frequently asked questions

Can I start in a personal account and move later?

You can. You will spend time and risk reviews. Start in the company org if the company exists.

Does Croncode need Admin?

For client work, App Manager or Admin by invite is enough. You keep Account Holder.

What about enterprise or unlisted apps?

The same rule: the organization that must survive a staff change owns the account. The program type is a separate Apple decision.

Who owns reviews?

The listing owner. We can draft replies if contracted. Habit: read reviews as a team.

Where is this written in a Croncode project?

In the kickoff note next to the bundle ID. If it is missing, we stop before submission.