legal record · v2026-11-14
Argus Privacy Notice
What the personal Service collects, why it processes it, and how access, retention, cross-border processing and deletion work.
- Effective date
- Notice version
- 2026-11-14
1. Controller and scope
ArgusFA, LLC, a Delaware limited liability company, operates the Argus personal Service. This Notice covers the static website, independent account application, CLI, API, MCP, Casdoor authentication and support. GitHub, your agent host and financial sources have their own independent practices. No enterprise-customer processing service is offered.
2. Account, security and service data
- Casdoor handles account credentials, provider links and verification status. GitHub sign-in can return an identifier, login, display name, avatar and email under read:user and user:email; it does not grant repository-content access. Argus does not copy your password into personal business records or invent a verified contact.
- Argus records issuer/subject and account lifecycle, client and session metadata, explicit domain grants, document-version acceptance and security decisions. A device label is user-supplied; registered activity is not proof that a physical device is online.
- At your request we store preferences, watchlists, saved-query definitions, evidence references, private research notes, event subscriptions, retained inbox notifications and user-entered holdings and income. CSV previews and export jobs contain only the selected authorized material.
- Usage records distinguish admitted attempts, successful calls, policy denials, business failures and incomplete statistics. Security audits contain bounded categorical metadata and evidence references, never private bodies, credentials or complete third-party agent conversations. Responses delivered to you or your agent are not archived.
- Support receives what you choose to send. Do not send passwords, access or refresh tokens, API keys, deletion progress credentials or unnecessary identity documents.
3. Purposes and permissions
We process requested private records to save, calculate, retrieve, notify, export and delete them; account/security data supports authentication, abuse protection, permissions and reliable operation. We also process necessary records for applicable obligations and claims. We do not use private notes or asset records for advertising, recommendations, model training or cross-user analysis.
A fact-reading grant gives no private-data rights. Private reads and writes require signed domain scopes plus current owner consent. Background subscription authority is explicit and separate from a short-lived agent login. Export has its own scope and is intersected with readable domains. High-impact revocation, deletion and identity changes require the trusted owner flow and recent verification.
4. Cookies, credentials and the static website
The static documentation website does not receive tokens or private records and does not set advertising or third-party behavioural analytics cookies. Published usage information is privacy-thresholded aggregation, never private documents or subject identifiers.
The personal application uses host-only Secure, HttpOnly, SameSite cookies, CSRF protection and private no-store responses. It stores upstream credentials in a dedicated encrypted, expiring session store; browser script cannot read its opaque session cookie. The CLI uses the operating-system credential store. No private record or deletion progress credential belongs in a public URL, search index, screenshot, issue report or chat.
5. Sharing and your agent
Infrastructure, security and email providers process necessary data under applicable arrangements; advisers, authorities or a successor may receive data where necessary and lawful. GitHub participates only when you choose that sign-in method. We do not sell private data or share it for cross-context behavioural advertising.
An authorized agent may retrieve only the domains you granted. Its host may process those results under its own terms and in other countries. A saved evidence reference grants no right to send restricted source text to an external model. Current source rights are checked separately for display, storage, notifications, export and model processing; withdrawn rights can withhold source content while preserving a lawful minimal reference.
6. Cross-border processing
ArgusFA operates from the United States; infrastructure, identity, email, source providers and the agent host you choose may operate elsewhere. Data can therefore be processed outside your country. The deployment-specific provider, location and transfer arrangements must be recorded before that deployment opens. This Notice does not assert a verified provider location, worldwide legal clearance or a transfer safeguard that has not been established. Contact us about the arrangements applicable to your account.
7. Retention and erasure
- Private records remain while active and requested, subject to published capacities and owner deletion. Inbox notifications are retained for 90 days; import previews expire after 30 minutes, with cleanup targeted within 24 hours; export artifacts for 24 hours. Reaching a retention limit is reported as a gap rather than a complete history.
- Personal usage history is retained for 35 days. Recovery requests expire after 30 days and completed recovery clears its encrypted contact claim. Unconfirmed deletion preparations expire after 5 minutes.
- Deletion progress credentials and final status expire 180 days from preparation. Access is refused at expiry even before maintenance purges the record. An unfinished dependency may retain minimal job state for verified support; it is not falsely marked completed.
- Security audit records are kept for up to 365 days and then pruned, without private bodies or usable secrets. Minimal consent history and revoked-credential metadata follow the same 365 days security period. Account deletion pseudonymizes your audit records: your account identifiers are replaced with a random per-deletion token, the record linking that token to your account is deleted once the rewrite finishes, and request details are removed, so each record keeps only that token, event type, outcome and timestamps. Later attempts to use the deleted account are recorded as refused security events.
- Responses delivered to you or your agent are not archived. Response archives of internal service accounts are pruned after 30 days, and account deletion removes any archive linked to your account.
- Backups are encrypted and rotate within 35 days, including any off-host copy, and are isolated from ordinary access.
- Minimal subject/lifecycle denial state prevents old access tokens, refresh chains or automatic registration from restoring a deleted account. It has a mandatory review after 90 days; it never expires into permission. Removal requires verified upstream retirement, backup drain and continuing refusal protection. A necessary retention exception has a dated reason and next review.
- A restored backup stays closed until deletion and revocation protections have been replayed. Deletions recorded after that backup, including audit pseudonymization and archive removal, are applied again before access reopens.
8. Export, deletion and account rights
Use the trusted personal account application to request selected or full personal export after recent verification, or to request deletion without exporting first. Exports provide CSV and Markdown with snapshot time, versions, timezones, currencies, source references and missing categories. Every new download rechecks identity, access, expiry and applicable source rights. Already delivered bytes cannot be recalled.
Deletion disables Argus access, stops subscription work and revokes applicable sessions and credentials before cleanup. Cleanup covers private records, response archives, audit linkage and the identity mapping, which is reduced to a minimal tombstone that keeps the deleted account refused. Shared identity accounts lose Argus authorizations only; dedicated identity deletion requires verified scope. Public financial source data and accounts independently held by GitHub are outside Argus account erasure. See the Account Deletion Guide for progress, failures and support.
9. Questions, rights and changes
Contact [email protected] to request access, correction, erasure, a processing explanation or verified recovery. Applicable statutory rights and complaint routes remain available. We publish a real document version and require renewed owner acceptance of an updated version; an identity-provider footer alone does not create acceptance. This is a description of the implemented service, not an independent legal conclusion about every jurisdiction.
This Notice is written in English, and the English text is authoritative. A translation is provided for convenience only; if a translation and the English text differ, the English text prevails.