Privacy policy (beta)

Effective 2026-10-23. These are the terms of Argustry's private, invitation-only beta. They will be replaced before Argustry opens to the public.

Who we are

Argustry is run by OOP Consulting LLC ("we"). Contact: support@argustry.com; security reports: security@argustry.com.

Who the beta is for

Only people we invite. We are the controller of your personal data.

What we collect and why

Your account. You sign in with Google through Google Cloud Identity Platform. We keep the user id Identity Platform gives us, your email address when Google confirms it is verified (to contact you; it is never used to find or link your data), a session record that keeps you signed in for up to 48 hours, and the times your account, tokens and sign-ins were created, changed or closed. Identity Platform keeps its own record of your Google sign-in (email, name, photo, provider ids) on our behalf.

Your Claude account email. You type it once so we accept data only from your own Claude subscription. We never store it: we store a keyed code computed from it.

Token names. The names you give your tokens, so you can tell them apart. They are free text, so don't put anything in them you don't want us to keep.

Claude Code telemetry. With the setup block we give you, Claude Code sends its OpenTelemetry events and metrics to us. We keep usage data: event names and times, session ids, models, token counts, cost, durations, the names of tools, MCP servers, skills, plugins, agents, slash commands and hooks, permission decisions, error names and codes, sizes (never contents) of prompts and tool results, the Claude Code version, and your operating system type, processor architecture and terminal type. Names are kept as sent, so a name you chose (for example an MCP server named after a project) is kept as it is.

What we drop. Before anything is queued, stored or logged we remove your email address, account, organization and installation ids and host name, and we drop prompts, model responses, tool arguments and commands, file paths, URLs, full error messages, git branch names and commit ids. Your user and installation are stored under keyed codes instead. That is pseudonymisation, not anonymisation: we hold the keys.

Logs. Our services log event names, counts, our own account and token numbers and error types. They never log tokens, email addresses, prompts or other content. Our load balancer also logs a sample of about one request in ten: the time, your IP address, the browser or client name, the address requested (never what comes after #, so never an invitation code) and the result; for telemetry it includes the first characters of the token, never the part that makes it valid. We use these logs to keep the service running and to stop attacks.

Someone who signs in without an invitation. If you open Google sign-in without a valid invitation, we refuse you, but Identity Platform has already created its record of your Google sign-in. Ask us and we delete it.

How we use it

Only to run Argustry for you: to sign you in, accept and store your telemetry, show it to you, keep the service secure and contact you about your account. We do not sell your data, use it for advertising, or share it with anyone except the service provider below.

Legal bases (EU/EEA, UK and Switzerland)

We process your account data, Claude account email code, token names and telemetry because we need them to provide Argustry to you under our terms (performance of a contract). We process the load balancer's request logs for our legitimate interest in keeping the service secure and running. Without the account data and telemetry we cannot provide Argustry. We make no decisions about you by automated means alone.

Google sign-in data

We request only the basic Google scopes openid, email and profile. We use what they return only to sign you in and to contact you, as described above, and never transfer it to anyone else.

Where it is kept, and who processes it

Everything runs on Google Cloud in the United States, which hosts our services, database, queue, logs and sign-in. Google is our only service provider for your data and processes it under Google's Cloud Data Processing Addendum. If you are in the EU/EEA, the UK or Switzerland, your data is transferred to the United States under the Standard Contractual Clauses that addendum includes (with the UK Addendum for UK data).

How long we keep it

While your account is active. Retention periods are not set yet in the beta: we delete your data when you ask us. Copies in database backups and in our message queue age out within about a week; operational logs, which hold no email or content, within about 30 days. If you close your account, your tokens stop working about 48 hours later.

Your rights

You can revoke any token and close your account yourself. Write to support@argustry.com to access your data or get a copy of it, correct it, have it deleted, restrict or object to its processing, or take it elsewhere. We answer within one month; in the beta we handle requests by hand. If you are in the EU/EEA, the UK or Switzerland, you may also complain to your data protection authority.

Cookies

The Argustry app sets one cookie, which keeps you signed in. We use no analytics, advertising or tracking cookies. Google's sign-in popup runs Google's own pages while you sign in; afterwards the sign-in library keeps nothing in your browser.

Do Not Track. We do not track you across other websites, and we let no one else do so through Argustry, so a browser's Do Not Track signal changes nothing here.

Security

All traffic uses HTTPS. The web app you sign in to never holds the keys that sign tokens or compute the keyed codes. Tokens are shown to you once and never stored by us.

Changes

We will tell beta users by email before a change that affects them takes effect. The effective date above shows the current version.