How GitHub Connections Are Protected
Godot Launcher opens GitHub sign-in in your normal web browser. Your GitHub password is entered only on GitHub and is never entered into Godot Launcher.
Sign-in protection
When you start connecting, the launcher creates a temporary sign-in session for that copy of the launcher on your computer. After you approve the request on GitHub, the approval can complete only that originating session. The sign-in result expires quickly and cannot be reused after the connection completes.
Do not approve a GitHub App request that you did not start from Godot Launcher. Close the browser page and start a new connection from Settings > Connections when you are ready.
What Godot Launcher stores
Godot Launcher stores the credentials needed for a connection using secure credential storage provided by the operating system. If secure storage is not available, the launcher does not save the connection.
Credentials are not placed in project files, Git remote URLs, or normal application logs. Non-sensitive details, such as the connected GitHub account name, installation name, and connection health, are stored locally so the launcher can show and manage the connection.
The project-operated sign-in service handles the GitHub sign-in exchange. It does not retain GitHub tokens, repository lists, repository contents, or Godot Launcher project data. Repository information is requested from GitHub when the launcher needs it for a workflow you started.
Repository permissions
Repository import uses read access to list and clone repositories. Publishing a new project also requires Contents write access to push its initial commit and Administration write access to create the private repository. The launcher requests these permissions through the GitHub App and uses them only for a publishing action you start.
When installing the GitHub App, you choose which repositories it can access. Use Manage repository access in Settings > Connections to review or change that selection through GitHub.
If an existing installation has not approved the publishing permissions, the launcher keeps supported import access available but disables publishing for that connection. GitHub must show and receive approval for the updated permissions before the launcher can create or write to a repository.
Disconnecting and revoking access
By default, Disconnect removes the local connection. It does not uninstall the GitHub App or change its repository selection on GitHub. When disconnecting the last connection for a GitHub account, you can also choose Revoke and disconnect to revoke that GitHub authorisation on all Godot Launcher devices. Those devices will need to reconnect.
Use Manage repository access to change the repository selection, revoke authorization, or uninstall the GitHub App through GitHub.
Limits
No sign-in design can protect credentials from malicious software that already controls your operating-system account or computer. GitHub sign-in and token refresh also require GitHub and the project-operated sign-in service to be available.
Keep your operating system and Godot Launcher updated. Report suspected security problems through the project's published Security Policy.
See Connections to connect or manage GitHub, Create Your First Project to publish a new project, and Import a Git Repository to import a repository.