Apple Developer Account After Death: A Continuity Plan

Apple Developer Account After Death: A Continuity Plan

For an independent app developer, an Apple Developer membership can sit at the center of an entire business. It connects app ownership, releases, certificates, agreements, sales reports, tax information, banking, user roles, and access to App Store Connect. Yet the person who writes the code may also be the only Account Holder, the only person with trusted devices, and the only one who understands how the rest of the product stack fits together.

If that person dies or becomes incapacitated, a password is not a continuity plan. The family may possess a laptop without having authority to operate the business. A collaborator may know the codebase without being able to accept agreements or renew the membership. An executor may have legal authority but no map of the developer account, repositories, servers, or customer obligations.

The answer is to prepare both sides of the handoff: Apple's official account processes and the real-world records that let an authorized person use them responsibly.

First identify the membership type

Start by recording whether the developer enrolled as an individual or as an organization. This distinction changes what other users can do and how succession works.

For an organization membership, the Account Holder can transfer that role to another employee on the team who has legal authority to bind the organization. Apple describes a formal acceptance process and allows only one Account Holder at a time. A prepared studio should therefore have an eligible successor already on the team, with their own Apple Account and appropriate operational knowledge.

An individual member can add users to App Store Connect, but Apple says those users are not part of the Apple Developer Program team and do not receive access to the other membership resources. Giving a contractor an App Manager or Developer role is useful, but it does not make that person a complete successor.

Apple specifically states that an Account Holder transfer for an individual member may be granted when the Account Holder is deceased and that help from Apple Developer Support is required. That is the correct escalation path. Do not assume that sharing the deceased person's password or taking control of a trusted device produces a valid ownership transfer.

Record the membership type, Team ID, Account Holder name, legal entity name if applicable, renewal date, enrollment method, and link to Apple Developer Support in the continuity file.

Understand the jobs only the Account Holder can finish

The Account Holder is not merely the most powerful technical user. Apple assigns that person responsibility for agreements and membership renewal. The role also matters for banking changes and other business actions in App Store Connect.

This creates several possible failure points:

• an updated agreement waits for acceptance
• the annual membership reaches its renewal date
• banking or tax details need attention
• a new app or version cannot complete its release workflow
• certificates, identifiers, or profiles need management
• a specific app needs to move to another developer account

Apple says that when a standard Apple Developer Program membership expires, apps are no longer available for new download. The developer also loses the ability to submit new apps or updates and access Certificates, Identifiers & Profiles. People who already installed an app can continue using it, but that is limited comfort if its backend, authentication, domain, or paid infrastructure also depends on the missing developer.

List the renewal date and payment arrangement, but do not rely on auto-renewal as the whole plan. A payment card can close, an agreement can change, or a trusted device can become inaccessible.

Build a team before there is an emergency

Organization accounts should avoid concentrating every task in the Account Holder. Add team members using separate Apple Accounts and grant only the roles their work requires. At minimum, decide who can handle app management, releases, development, finance, customer support, and administration.

Separate identities are safer than a shared login. They preserve an audit trail, allow one person's access to be removed, and keep each person's two-factor authentication independent. They also let the team see which tasks still depend on the Account Holder.

An organization should identify a potential successor who satisfies Apple's rule: the person must be an employee on the team and have authority to bind the organization to legal agreements. Do not wait until the founder is already unavailable to discover that the intended successor is an outside contractor or has never been added to the team.

For an individual developer, App Store Connect collaborators still improve day-to-day resilience. Give a trusted maintainer enough access to monitor releases and understand the portfolio, while documenting clearly that a death-related Account Holder transfer must go through Apple Developer Support.

Keep the continuity inventory separate from secrets

The continuity document should tell an authorized person what exists and where the protected access method lives. It should not become a plain-text collection of passwords, private keys, or recovery codes.

Inventory at least:

• the Apple Developer Team ID and membership details
• App Store Connect users, roles, and contact information
• every app, bundle ID, platform, status, and business owner
• source-code repositories and the organization that owns them
• build, continuous-integration, and deployment services
• certificates, provisioning profiles, API keys, and signing procedures
• App Store Connect API integrations and webhook consumers
• domains, DNS, email, support desk, status page, and privacy contacts
• backend hosting, databases, storage, analytics, and crash reporting
• paid applications agreements, banking, tax, bookkeeping, and revenue records
• third-party SDK, licensing, advertising, and subscription dependencies
• the attorney, executor, company officer, technical maintainer, and accountant to contact

For each item, state who owns it, who is permitted to act, its renewal or expiration risk, and where its recovery instructions are stored. A password manager, controlled company vault, sealed estate record, or professionally managed escrow arrangement may hold sensitive details. The inventory merely points to that protected location.

Do not confuse an app transfer with account succession

Apple provides an App Store Connect process for transferring an eligible app to another developer account. This can be useful in a planned sale, reorganization, or succession, but it is different from transferring the Account Holder role.

An app transfer has detailed criteria. Apple requires both accounts to be in an appropriate state and to have accepted relevant agreements. The app must have a released version and cannot be in certain review, release, pre-order, or product states. Particular technologies and services can create extra work. The Account Holder initiates the transfer using the recipient Account Holder's Apple Account and Team ID.

The transferor should save app metadata, pricing, sales, and download records. Apple says the pending transfer expires after 60 days if it is not accepted. A continuity plan should therefore name the intended recipient, confirm that their account is active, and include a checklist for services connected to the app.

Do not promise heirs that every app can be moved immediately. Review the current transfer criteria for subscriptions, in-app purchases, Game Center, Sign in with Apple, CloudKit, keychain sharing, push notifications, and other capabilities before choosing this path.

Connect platform access to legal authority

Apple can decide who controls roles within its systems, but a developer's estate or company still needs a person authorized to make business decisions. The correct representative may be an executor, trustee, company director, surviving owner, or another person named under applicable law and governing documents.

Write down who can make decisions about:

• continuing, selling, or withdrawing an app
• using or licensing source code and other intellectual property
• paying infrastructure and contractors
• accessing business banking and tax information
• communicating with customers and handling privacy requests
• preserving records and responding to litigation or regulatory duties

The technical maintainer and legal decision-maker do not have to be the same person. In fact, a paired handoff is often stronger: one person proves authority and approves decisions, while another explains builds, signing, servers, and releases.

Because inheritance, entity, tax, privacy, and intellectual-property rules vary, obtain legal advice for the relevant jurisdiction. The continuity file should identify counsel rather than trying to replace counsel.

Prepare the source code and infrastructure too

Moving control of App Store Connect will not keep an app healthy if no one can build it or operate its services. Make sure the organization—not only a personal account—controls critical repositories, domains, package registries, cloud projects, databases, email, and monitoring.

Create a concise runbook that explains how to:

1. verify that production services are healthy
2. reach the code and reproduce a build
3. rotate exposed credentials without destroying needed evidence
4. renew domains, hosting, and other time-sensitive services
5. answer customer and security reports
6. pause risky deployments, marketing, or sales if no maintainer is ready
7. find data-retention, privacy, and incident-response procedures

Avoid undocumented signing from one laptop. Document the approved signing workflow and recovery process, limit access, and ensure another authorized maintainer can understand it. Do not casually copy private keys into an estate binder.

What to do after a developer has died

If no plan was made, preserve first and change later. Do not erase the developer's phone or computer, cancel the primary phone number, close business email, delete repository accounts, or dismantle payment arrangements before understanding their dependencies.

Then take these steps:

1. Identify the membership type, Team ID, legal owner, and existing App Store Connect users.
2. Identify the executor, company officer, or other representative with authority.
3. Contact Apple Developer Support and explain that the Account Holder has died.
4. Follow Apple's instructions for the relevant individual or organization account; be prepared to provide the documentation Apple requests.
5. Ask existing team members to inventory app status, pending agreements, releases, certificates, infrastructure, customer issues, and renewal dates without impersonating the deceased.
6. Preserve financial, tax, sales, contract, source-code, and ownership records.
7. Decide whether the goal is continued operation, an Account Holder change, transfer of eligible apps, sale of the business, or orderly closure.

Do not invent a document list and send sensitive records to an unverified address. Start from Apple's official support channel and respond to the case instructions.

Review the plan like a production system

Test the plan at least annually and after changes to ownership, company officers, team roles, Apple Accounts, trusted devices, banking, tax status, authentication, domains, hosting, or major app capabilities.

Run a tabletop exercise: assume the Account Holder and all of that person's devices are unavailable. Can the team identify the membership, contact the right representative, keep production stable, locate the code, see upcoming renewals, and explain the official Apple support path? Can the authorized decision-maker find the contracts and understand the choices without receiving a folder of unexplained secrets?

Every unanswered question is a concrete continuity task.

Conclusion

Planning for an Apple Developer account after death is not about passing down a login. It is about preserving a chain of authority and a chain of operation.

For an organization, add real team members, distribute duties, and prepare an eligible Account Holder successor. For an individual membership, document the account and business thoroughly so an authorized representative can request Apple Developer Support's help. In both cases, protect the code, signing process, infrastructure, finance, domains, and customer obligations that live outside Apple's systems.

Start with one page: membership type, Team ID, Account Holder, renewal date, legal representative, technical maintainer, and official support link. Then build the inventory and test it. That small beginning can keep an app portfolio from becoming another avoidable loss during a family or company crisis.