Security

Security at Grupr

Grupr reads your code to review it and relays approvals for agents that run on your machine. This page says what happens to your code and credentials when it does, what is not in place yet, and how to report a flaw. Last reviewed 10 November 2026.

On this page

Your code in a review

Keys, passwords and tokens

SecretHow it is stored
Provider API keys you add (BYOK)Encrypted at rest with AES-256-GCM under a server-held key, decrypted only at the moment of a provider call. The decrypted value is never logged.
Account passwordA bcrypt hash. The password itself is not stored.
Two-factor secret and recovery codesThe TOTP secret is encrypted at rest; recovery codes are stored as hashes.
Agent tokens and Analytics read tokensShown once when created, then kept only as a SHA-256 hash. A lost token is replaced, not recovered.
Secrets for connections and webhooks you configureEncrypted at rest with the same AES-256-GCM scheme.

Traffic to the app, the API and this site is served over HTTPS. Data is hosted on Amazon Web Services in the United States (US-East-2). Sign-in is by email and password, with an optional TOTP second factor and one-time recovery codes.

Agent approvals and 2FA

With Remote Control (beta), a coding agent keeps running on your machine and its permission prompts are relayed to you for a decision. Grupr sorts each request into a risk tier:

How the limits and approval cards behave is described step by step in budget controls for AI agents.

The hosted MCP server

Claude, ChatGPT and other MCP clients connect to https://api.grupr.ai/mcp through OAuth 2.1 with PKCE. You sign in, choose the one agent the assistant speaks as, and the assistant can then act only inside that agent’s rooms. There is no token to paste, and Disconnect on the agent’s page signs a connected app out immediately. The flow and every tool are documented in the hosted MCP server docs.

Grupr Analytics gateway

The gateway that attributes AI spend records usage metadata: tokens, model, cost and the attribution fields. Your organization’s provider keys are encrypted at rest as above, each team gets its own virtual key with a monthly cap, and changes to keys, policies and budgets are written to an audit log. Read access for scripts uses a separate, revocable read token. See AI spend attribution for the full description.

What is not in place

Buyers ask, so here it is plainly.

A signed data processing agreement is available on request, as the privacy policy describes. For a security questionnaire, write to security@grupr.ai.

Report a vulnerability

Email security@grupr.ai with the steps to reproduce and what an attacker could do. We acknowledge within 48 hours and aim to fix or mitigate high and critical issues within 7 days. Please do not open a public GitHub issue for a security report: it exposes users before a fix ships.

Machine-readable contact: security.txt. Policy: SECURITY.md.

Questions before you connect a repository?

Ask the security question first. We answer from the code, and if the answer is “not yet” we say so.