Privacy policy

What we collect

Account details. Your email address, an optional display name, and your password. Passwords are hashed with PBKDF2-SHA-256 (100,000 iterations, a random salt per user); we never store or log the plain password. Project names and membership records link your account to the projects you belong to.

Provider credentials. The API keys or tokens you connect for OpenAI, Anthropic, OpenRouter and other providers. See How we store credentials.

Data we read from your providers. Using your credentials, Argus makes read-only requests to each provider for balances, credits, spend, usage and plan details, and stores the results so it can chart them and send alerts.

Usage telemetry you send. If you use the SDK or post to /ingest, each event can include: provider and hostname, request path (not the query string), HTTP method and status, latency, model, token and other unit counts, cost, credits spent or remaining, rate-limit headers, the provider’s request id, a timestamp, and up to 2 KB of metadata tags you choose. The SDK reads provider responses only to extract a fixed list of those fields. It never sends request bodies, prompts, completions or other message content, and the ingest endpoint has no field for them. Don’t put personal data in metadata tags.

Billing details. Stripe collects your card and billing details directly; we never see or store your full card number. We store your Stripe customer and subscription ids, plan, subscription status and renewal date.

Connector builder conversations. On paid plans you can ask an AI agent to build a connector for a provider we don’t support yet. We keep the conversation, any docs you paste, the requests the agent made to the provider (method, host, path, status) and the resulting connector code.

Request and security data. Your IP address is used to rate-limit sign-in, sign-up and waitlist requests, and is recorded in our audit log alongside security-relevant actions such as creating keys or deleting connections. Our servers also record operational telemetry (route, timing, outcome, errors and your user and project ids) to run and debug the service.

Waitlist. If you join the waitlist we store your email address and where you signed up from.

How we store credentials

• Provider credentials and ingest signing secrets are encrypted with AES-256-GCM before they're written to our database. The encryption key is held as a separate server secret, not in the database.
• Credentials are decrypted only in memory, at the moment Argus calls the provider. They're never returned by our API, shown in the dashboard after you save them, or written to logs.
• Argus API and MCP keys are shown once at creation; we store only a SHA-256 hash.
• When the connector builder calls your provider, a gateway attaches your credential to the request and redacts it from the response. The AI model never receives it.
• Deleting a connection deletes its stored credential. A credential entered in the connector builder is kept, encrypted the same way, with that build session.

How we use data

• To run the service: sync provider data, price and chart your usage, forecast runway and send the alerts you configure.
• To secure the service: authenticate you, rate-limit abuse and keep an audit trail.
• To bill you for a paid plan.
• To email you about your account and the alerts you set up. We don't send marketing email without asking.
• To diagnose problems and improve the service, using operational telemetry.

We don’t sell personal data, share it for advertising, or use your provider data or telemetry to train AI models.

Cookies and browser storage

We set one cookie, argus_session, when you sign in. It’s HttpOnly, Secure and SameSite=Lax, and expires after 30 days or when you sign out. The dashboard also keeps a few interface preferences in your browser’s local storage. We don’t use advertising cookies or third-party web analytics on argus.town.

Subprocessors

These companies process data on our behalf to provide the service:

Argus also calls the providers you connect, using your credentials, to read your account data. Those providers are your vendors, governed by your agreements with them.

Who else sees your data

Members of a project can see that project’s connections, spend and alerts, and every member receives the project’s alert emails. We disclose data to others only when the law requires it, to protect the service or its users, or as part of a merger or sale of the business, in which case this policy continues to apply.

Retention

Raw usage events are deleted automatically after a window set by your plan. Events that carry a cost or an error are kept for twice that window. Daily totals derived from them are kept while your account exists.

When you close your account we delete its data from our live systems within 30 days. Stripe keeps billing records under its own retention rules and our legal obligations.

Your choices and rights

You can delete connections, ingest sources, API keys and alerts yourself in the dashboard, read your data through the API and MCP server, and cancel a subscription from the billing portal. To get a copy of your data, correct it, or close your account and delete it, email hello@argus.town from the address on the account. We respond within 30 days.

Depending on where you live, you may have rights to access, correct, delete or port your data, to object to or restrict some processing, and to complain to a data protection authority. We honor these requests for every user, wherever they live. Where the GDPR applies, we process data to perform our contract with you, for our legitimate interests in securing and improving the service, and to meet legal obligations.

Security

Traffic to Argus is encrypted with TLS, credentials are encrypted at rest as described above, and staff access to production data is limited to operating and supporting the service. No system is perfectly secure; if a breach affects your data, we’ll notify you as the law requires.

International transfers

We’re based in the United States, and our subprocessors may process data in the United States and other countries. By using the service you understand your data will be processed outside your home country.

Children

Argus is a tool for businesses and developers. It isn’t directed at children under 16, and we don’t knowingly collect their data.

Changes to this policy

We’ll update the date above when this policy changes, and email account owners before any material change takes effect.

Contact

Thybris Labs, Texas, USA. Email hello@argus.town. See also our terms of service.