Argus Account Deletion Guide

Before you request deletion

Account deletion is different from logging out or revoking GitHub access. Logging out removes the Argus CLI credential from that device. Revoking GitHub stops future GitHub sign-in. Deleting the Argus account removes the account and associated identity records from active systems, subject to the limited retention described below.

1. Remove credentials from every CLI device

Run the following command on each computer where you signed in:

• argus auth logout
• Then run argus auth status and confirm the state is logged_out.
• Also remove any ARGUS_ACCESS_TOKEN, API key or other Argus credential that you manually stored in environment variables, CI systems or secret managers.

2. Revoke GitHub access if you used GitHub

Open GitHub Settings → Applications → Authorized OAuth Apps, locate the GitHub OAuth application used by Argus authentication, and revoke its access. Revocation at GitHub does not delete your Argus account; complete the next step as well.

3. Send the deletion request

Email [email protected] from the email address associated with the account. Use the subject “Argus account deletion request”. Include only your Argus username and account email, plus whether you used GitHub sign-in. Do not send your password, OAuth token, API key, recovery code or a copy of identity documents unless we specifically request a proportionate verification method.

If you cannot access the account email, explain that in the request. We will use a proportionate alternative verification process. We will acknowledge and complete valid requests within the time required by applicable law.

4. What we delete or disconnect

Deletion does not delete your GitHub account, data held independently by GitHub, public source data queried through Argus, or credentials you stored outside our systems.

• The active Casdoor account used for Argus and its email, username, profile and linked GitHub identity.
• Active Argus sessions and refresh credentials under our control, where technically available.
• The Argus OAuth subject mapping and active account-to-caller association.
• Support content that is no longer needed, unless retention is required for a claim, security investigation or legal obligation.

5. Limited information that may remain

We will explain any material exception that applies to your request unless prohibited by law.

• Security and tool audit records may remain for up to the current 365-day audit period where needed to protect the Service, demonstrate authorised use, comply with law or resolve disputes. We will minimise or de-identify the account linkage where reasonably possible.
• A suppression record may be retained to honour the deletion, prevent accidental reactivation or document compliance.
• Encrypted backups may contain residual copies until overwritten in the normal backup cycle. They are isolated from ordinary use and deleted again if restored.

6. Consequences

Deletion is intended to be irreversible. Your saved settings, provider links and access history may not be recoverable. A later registration may create a new account and will not automatically restore prior access. Organisations should arrange transfer of any organisation-controlled access before requesting deletion.

7. Contact

Questions, appeals and deletion requests: [email protected]. You may also complain to the data-protection authority that applies where you live or work.