Docs Security and privacy

Your account · 04

Security and privacy

Tuxedo holds the keys to your other accounts, so it keeps as little as it can and locks up the rest. This page says what it keeps, how it protects it, and what it never keeps at all.

What Tuxedo keeps

Tuxedo keeps what it needs to sign you in, reach your servers and show you what your agents did.

  • Your account. Your name and email address, your profile picture when GitHub or Google gives one, and each way you sign in: a GitHub account's id and username, a Google account's id and email address, or an email address you sign in to with a code.
  • Your Connections. Each server's address, the name, handle and "Use this account for" note you give it, the account it signed in as, the tools the server lists, and its credentials, encrypted.
  • Your Suits. Their names and descriptions, their access modes, the Connections they wear, which tools are on, a hash of each of their tokens, and the apps you approved.
  • Activity. One entry for each tool call through a Suit: when it happened, the Suit, the Connection, the name the client called and the server's name for it, how it ended, how long it took, how the client got in and the name of its token or app.
  • Tool-call counts. How many tool calls your Suits sent on each week, for this week and the 8 weeks before it, for the weekly limit and the usage Tuxedo shows you.
  • Payments. Each payment's period, amount, status and PayMongo references, how you paid (for a card, its brand and last four digits), the address PayMongo emailed the receipt to, and the Pro time it bought. You pay on PayMongo's own checkout page, so your card number never reaches Tuxedo.
  • Sign-in codes. Only a hash of each code, until it's used or expires. Expired codes are removed every day.
  • Your session. While you're signed in, Tuxedo's record of your session holds your IP address and your browser's user agent. Signing out deletes it; otherwise it expires after 120 minutes without use.

In your browser, Tuxedo's cookies keep you signed in and protect its forms, and one remembers which client you last picked in a Suit's setup. The theme you choose stays in that browser too. Tuxedo's pages load no analytics or advertising scripts.

What it never keeps

  • What your agents send and get back. A tool call's arguments and results pass through Tuxedo between your client and the server. Activity records that a call happened, never what was in it.
  • Servers' error messages. Tuxedo never stores the text a server sends when something fails, or writes it to its logs.
  • Your tool searches. What you type in a Tools page's search goes to TypeSafe, with the names, titles and descriptions of the tools being searched, so its Jev model can judge which ones match. Tuxedo keeps the search only in the open page.
  • Passwords. Tuxedo has none. You sign in with another account, such as GitHub, or with a one-time code sent to your email.
  • The tokens GitHub or Google give it when you sign in. Tuxedo uses them only while you sign in, to read your profile, and doesn't keep them.
  • Your Suits' tokens. Only a hash of each, as the next sections explain.

Your Connections' credentials

Connections are the only place Tuxedo keeps your secrets: the token or header value you give it, the OAuth tokens a server issues, your own OAuth app's client secret, and the secret a server gives Tuxedo when Tuxedo registers itself with it.

  • Encrypted with a key of your own. Each secret is encrypted with AES-256-GCM under a data key that belongs to your account alone.
  • Your key is locked by a master key. Tuxedo stores your data key only wrapped by a master key the server keeps apart from the database, so a copy of the database alone can't decrypt your credentials. A wrapped key opens only for its own account.
  • Unlocked only while in use. Your key is unwrapped in memory for the one request or background job that needs it, and never cached.
  • Never shown back. Once saved, a credential never comes back to the page: its field starts empty. To change a token you enter a new one; to keep a header value or a client secret, leave its field blank.
  • A new address starts afresh. On a custom server: "Changing the URL clears every stored credential, so enter the header value or client secret again, and sign in again."
  • Signing in with PKCE. When Tuxedo signs in to a server for you with OAuth, it uses PKCE (S256), and refuses a server whose sign-in isn't on HTTPS or doesn't support PKCE.

Your Suits' credentials

A Suit's endpoint ends in a random id, and that address opens nothing by itself. A client also needs the credential of the Suit's access mode, and the Suit accepts only its current mode. Access compares the modes.

  • OAuth. A client sends you to Tuxedo to sign in, and you approve it on Tuxedo's consent screen; approve only a client you just added the Suit to yourself. Its access tokens last 1 hour, and each renewal brings a new refresh token good for 30 days, so an app that keeps renewing stays connected until you revoke it. Each token opens only the Suit you approved the app for. Tuxedo keeps a record of each token (its app, its expiry, whether it's revoked), not the token itself. Revoking an app on the Access page stops it at once, and it can't renew its sign-in.
  • Bearer token. A token is txd_ and 40 random letters and digits. Tuxedo stores only its SHA-256 hash and its first few characters, so you can tell your tokens apart, and shows the whole token once: "This is the only time Tuxedo shows this token. If you lose it, create another and revoke this one." A Suit can have up to 10 tokens. The setup has your client read each from an environment variable, so it never sits in the client's config file. Revoking a token deletes it, and clients using it stop at once.
  • Signed URL. The Suit's endpoint with a version number and a signature made with Tuxedo's secret key. "Anyone who has this URL can use the Suit, so treat it like a password." Tuxedo stores only the version number and works the URL out again, so it's always there on the Suit's Access page. Keep it out of shared or committed files. Rotate URL gives the Suit a new one and stops the old one at once.

Switching a Suit's access mode retires the old mode's credentials for good: its approved apps are revoked, its tokens are revoked, or its signed URL stops working.

Every page finds Suits, Connections and payments among your own only, so anyone else's are simply not found.

Activity

Tuxedo keeps Activity for 1 day on Free and 7 days on Pro: once a day, it deletes the entries older than your plan keeps.

Calls Tuxedo refuses are recorded too, but a request with a wrong credential, or one the rate limit stops, isn't.

Activity shows times in your own timezone: the page asks your browser for it and keeps it in your session, not in your account.

Deleting a Suit or a Connection keeps its entries, which then show it as deleted. Deleting your account deletes them all. Activity explains the rest.

Requests to servers

Every request Tuxedo sends to a Connection's server, to that server's sign-in, to PayMongo or to TypeSafe goes through a guard first:

  • HTTPS only. Any other kind of URL is refused, and so is one carrying a username or password.
  • Public addresses only. Every address the server's name resolves to must be public. Private networks, loopback, link-local addresses (cloud metadata among them), carrier-grade NAT and reserved ranges are refused.
  • No switching addresses. The request goes to the addresses Tuxedo checked, so DNS can't change in between, and never through a proxy.
  • No redirects. Tuxedo never follows one, so give it the server's own endpoint.

Tuxedo checks a custom server's URL this way when you save it, as its form says: "The server's MCP endpoint. It must use HTTPS and be on the public internet." Custom servers has more.

Rate limits

Limits keep one runaway client, or anyone else, from using up your accounts.

  • Calls to a Suit. 120 requests a minute for each credential: each token, each signed URL and each approved app. A rotated URL starts afresh. Past the limit, the client gets an HTTP 429 (Too Many Requests) answer.
  • Sign-in codes. One every 60 seconds to the same address, 5 an hour to one address and 20 an hour from one IP address. A code works for 10 minutes and 5 tries. Asking for one says the same whether or not the address has an account.
  • Apps signing in to a Suit. 20 new app registrations an hour from one IP address.

The weekly tool-call limit is part of your plan, not a rate limit: Plans and billing explains it.

Deleting your account

Delete your account from Settings, with Delete account, and type what the box asks for to confirm.

Tuxedo signs you out, revokes every app you approved for your Suits and every token it issued to you, and deletes your account with your sign-in methods, your Suits and their tokens, your Connections and their credentials, your encryption key, your Activity, your tool-call counts and your payment records. "Your Suits stop working in every client right away."

  • Short-lived copies. The records of your sessions in other browsers, and cached copies of your Suits' tool lists, aren't deleted with your account; they expire on their own.
  • Payments. Tuxedo deletes its own payment records but doesn't ask PayMongo to delete anything. Deleting your account ends any Pro time you have left; if you want a refund, read the Refund Policy first.
  • Backups. "Backups are kept for a limited time and then removed." Until then, they still hold your encrypted credentials and your wrapped key.

Revoke your credentials at their services too

Deleting a Connection, or your account, removes its credentials from Tuxedo but doesn't revoke them at the service, so revoke a token or app there if you want it to stop working.

Privacy Policy and Terms

The Privacy Policy and the Terms of Service are the formal word on your information and your account. For anything this page doesn't answer, write to [email protected].