Approved AI Tools List

Purpose

This document lists the AI tools that are approved for use within Rygen, along with constraints for using them safely with company data.

Scope

These tools can be used by members of the Rygen team within the safe usage constraints for each tool, including any limit on who may use it.

Approved Tools

The following AI tools have been approved for use within their safe usage constraints.

The Information Security Officer records in Permitted data the sensitive company information each tool’s approval permits it to receive (AI-016 Policy Statement 5). A blank cell means none is permitted. Confidential and proprietary data stays governed by each tool’s safe usage constraints.

ToolApproved ByApproved DateSafe Usage ConstraintsPermitted data
ChatGPT (Plus, Pro, or Teams)Chris Broom2025-02-21• Only Plus, Pro, or Teams versions can be used
• Improving the model must be turned off in Data Controls
• Do not submit any conversations for review
Claude (Pro, Max, Teams)Chris Broom2025-02-21• Only Pro, Max or Teams versions can be used
• Do not submit any conversations for review
Github CopilotChris Broom2025-02-21• Must use Rygen’s organizational account
CursorChris Broom2025-02-21• Privacy mode must be enabled
ClineChris Broom2025-02-21• Must use Rygen-provided API key
Circleback.aiChris Broom2025-02-21• Be careful of conversations and documents shared
Google GeminiField Bradley2025-04-01• Only the Pro version or the version built into GCP can be used
LeapsomeField Bradley2025-04-01• Usage following the Leapsome terms and conditions
AiderField Bradley2025-05-12• Opt out of usage data sharing
• Only use approved LLMs
n8nField Bradley2025-08-15• Utilize only with approved LLMs
GreptileField Bradley2025-11-13• Usage following the Greptile terms and conditions
Fathom AI (Notetaker)Field Bradley, Chris Broom2026-07-21• DPA must be signed with Fathom before processing EU/UK client data
• Enable org-level opt-out of de-identified data use for model training
• Obtain client consent/disclosure for recording on customer-facing calls
• Sync only notes/action items to Claude, not full transcripts
• Do not use for client content restricted under AI-016
Otter.aiField Bradley, Chris Broom2026-08-14• Approved for trial evaluation only — three named users
• DPA must be signed with Otter before processing EU/UK client data
• Confirm Rygen’s client-communication practice covers Otter’s account-holder consent model
• Confirm what the Claude MCP integration exposes (transcripts vs. summaries) and scope OAuth accordingly
• Do not use for client content restricted under AI-016

Revision History

VersionDateAuthorSummary of Change
12025-02-21Field BradleyAdded initial approved AI apps (ChatGPT, Claude, Github Copilot, Cursor, Cline, Circleback.ai)
22025-04-01Field BradleyUpdated to allow free version of ChatGPT with policies; added Gemini and Leapsome
32025-05-12Field BradleyAdded Aider for agentic coding
42025-08-15Field BradleyAdded n8n workflow automation tool
52025-12-04Field BradleyAdded MCP connectors section with Atlassian, Office 365, and OpenMetadata
62025-11-13Field BradleyAdded Greptile for AI-powered document search
72026-01-15Field BradleyAdded Gitlab MCP connector
82026-06-10Field BradleyRemoved Approved MCP Connectors section (RFC) — MCP connectors are APIs used within already-approved AI tools; no separate MCP approval required
92026-07-21Field BradleyAdded Fathom AI (Notetaker) to approved tools
102026-08-14Field BradleyAdded Otter.ai (trial evaluation) to approved tools
112026-11-05Field BradleyOwner is the Information Security Officer, who approves new tools under AI-020. The scope allows each tool’s own limit on who may use it. The free versions of ChatGPT and Google Gemini are no longer allowed, Claude allows Pro, Max or Teams, and a Permitted data column records the sensitive company information (AI-016 Policy Statement 5) each tool’s approval permits (AI-2131)