Privacy

What this tool stores

When you sign in, you provide your Garage admin URL and admin token. These are encrypted (AES-256-GCM via iron-session) into an HTTP-only cookie named garage_ui_session and sent to your browser. The server briefly handles the plaintext values when validating sign-in and proxying API requests, but it never persists them to disk or to any database — there is no database.

When you click Use for browser on a key, the server fetches that key's secret from your Garage cluster and stores it inside the same encrypted cookie alongside your admin token. The browser never receives the secret in plaintext.

What it does not store

• No accounts, no email addresses, no passwords.
• No analytics tied to your credentials.
• No file contents — uploads and downloads go directly between your browser and your Garage cluster via presigned URLs. The server is never on the data path.
• No request bodies or response bodies in server logs. Tokens are explicitly redacted by the logger.

Cookie lifetime

The session cookie expires after 24 hours of inactivity. Clicking Sign out destroys it immediately. Closing your browser also clears it (the cookie is session-scoped in practice).

Server logs

The server logs request method, path, and status code so the operator can diagnose issues. Admin tokens, S3 secret keys, and the contents of API request/response bodies are not logged.

Third parties

This tool does not load third-party scripts, ads, trackers, or analytics in your browser today. If that ever changes, this page will be updated.

Risks you should be aware of

The server temporarily handles the plaintext value of your admin token while proxying requests. If the server is compromised, every active session is at risk. You can reduce blast radius by issuing a scoped admin token from your Garage cluster instead of using the root token.

Contact

Questions, concerns, or to delete a session immediately: just sign out, or rotate your Garage admin token (which invalidates any active session).