Credentials, access, ownership, and retention
Use scoped accounts and project permissions, and understand where generated repositories and project records live.
What you need
Only the access required for your workflow and an ownership plan for GitHub and store accounts.
What LaunchLayer does
Creates generated repositories in the connected GitHub account, uses protected credential flows, stores GitHub build values as encrypted repository secrets where configured, and applies project/team access controls.
What you still need to do
Rotate revoked credentials, manage team access, retain required artifacts and audit records, and review account ownership before staff changes.
Common problems
Connecting the wrong account, over-broad permissions, deleting a repository that owns build history, or assuming project deletion also removes data held by Apple, Google, or GitHub.