# Argus Account Deletion Guide

Prepare independent progress access, confirm deletion after owner verification, and track actual cleanup after ordinary access stops.

## 1. Open the trusted account application

Use the personal application registered for your deployment, then Account → Delete account. The public static website is a guide and never accepts credentials. If the application is unavailable or a credential is lost, contact hello@argusfa.com for verified support. Do not send authentication or deletion progress secrets.

## 2. Review scope and optionally export

You may request an export first, but it is not required for deletion. Review the account lifecycle and impact, then complete recent owner verification. Ordinary agent tools cannot confirm deletion, revoke all authorizations or perform sensitive identity changes.

## 3. Save and test independent progress access

Preparation displays a random progress credential once. Save it privately and test it in the protected progress form before confirmation. It expires 180 days from preparation; an unconfirmed preparation expires after 5 minutes. The server keeps only irreversible verification material. The credential can read status only, not private records, financial facts or a cancellation action. It never belongs in a URL or message.

## 4. Confirm and follow actual state

Confirmation persists the request together with account access disablement. A disablement failure is not reported as acceptance. Repeating the same committed confirmation returns its existing result; if the response was lost, use the progress credential already saved. After sign-out or disablement, the separate progress form remains available.

States distinguish accepted/access disabled, cleaning, waiting for a dependency, exception and completed. They include actual update time and next action. The healthy-dependency cleanup target is 24 hours; an outage is not completion. Contact verified support if progress needs intervention. There is no ordinary undo button and no promise to recover cleaned records.

## 5. What stops and what is removed

Argus blocks tool and private access, ends registered sessions, withdraws domain/background authority, fences in-flight work, and revokes mapped compatibility credentials. It removes private objects, indexes, previews, notifications, private usage, export artifacts, controlled download references and response archives linked to the account. New requests cannot use a still-valid storage URL to bypass revocation.

Security audit records keep only a random per-deletion token, event type, outcome and timestamps: your account identifiers are replaced with that token, the record linking it to your account is deleted once the rewrite finishes, and request details are removed. The identity mapping becomes a minimal tombstone without activity history, so old tokens and automatic re-registration stay refused.

Shared Casdoor accounts retain other applications: only verified Argus grants are removed. A dedicated account is deleted only after its exclusive scope and immutable identity have been verified. GitHub or other external-provider accounts and public financial facts are not deleted. New registration does not inherit the old private lifecycle or permit old credentials into a new one.

## 6. Limited records and backups

Progress access/final status expire after 180 days. Pseudonymized security audits, minimal consent history and revoked-credential metadata are kept for up to 365 days, without private bodies. Encrypted backups rotate within 35 days and cannot restore ordinary access until deletion/revocation replay succeeds; the replay applies completed deletions again.

Minimal subject/lifecycle denial state is reviewed after 90 days and never expires into access. Verified upstream retirement, backup drain and continuing refusal protection are required before removal; dated exceptions explain the next review. Unfinished jobs retain minimal work state for dependency repair after progress expiry. These limited records do not contain private notes or usable tokens.

## 7. Logout and external-provider revocation are separate

Run argus auth logout on each CLI device to remove local credentials; argus auth status shows the resulting state. Logout does not delete the account or stop independently authorized subscriptions. Remove separately stored environment or CI credentials from your own systems.

If you used GitHub, Settings → Applications → Authorized OAuth Apps lets you revoke its login link. That action does not erase Argus data or replace the account deletion process. We cannot recall files already downloaded to your devices.

## 8. Questions and exceptional recovery

Contact ArgusFA, LLC at hello@argusfa.com. Explain the problem without including passwords, tokens, API keys or progress credentials. Support verifies ownership proportionately; an unverified email or display name does not establish identity. Applicable rights and complaint routes remain available.

## Document information

- Language: en

- Argus version: 1.1.48

- Last updated: November 17, 2026

- Effective date: 2026-11-14

- Guide version: 2026-11-14

- Canonical URL: https://www.argusfa.com/en/legal/account-deletion/