Connecting safely to your AI assistant.
How connecting MetriFi to your AI assistant works, and why it is safe: scoped and revocable access, human approval on every change, and no path to your core or member data.
What the connection is, and what it can and cannot reach.
01What does “connecting MetriFi” actually do?
You connect your own AI assistant, such as Claude or ChatGPT, to MetriFi using a standard authorization, the same kind of secure sign-in you already use to connect business software. It links your assistant to MetriFi’s own tools. It gives MetriFi no way into your network, nor access to any sensitive data.
02What can the AI assistant reach once it is connected?
Only the MetriFi Platform (platform.metrifi.com). The connection is limited to MetriFi’s CRO, GEO, and SiteBuilder tools. (The SiteBuilder tools are for AI websites only, not WordPress websites.) An AI agent that’s connected to the MetriFi Platform acts on your behalf to use those tools, but can act only within the limits of your role on the platform. It cannot see or reach anything you have not connected.
You can further control your AI agent’s actions in the MetriFi connector settings. From there, you can grant read-only access or block certain actions altogether. The assistant can do only what you allow it to.
03Does connecting touch our core, online banking, or member data?
No. The connection runs one way, from your AI assistant to MetriFi’s tools, and has no route into your core, your online banking, or any internal system. Your MetriFi website itself holds no member data and has no database. Sensitive member activity, like banking and applications, happens inside your vendors’ own secure systems, never on the website.
You decide who can do what, and you can switch access off at any time.
04Can the AI change our live website on its own?
No. For most institutions it cannot touch your website at all: if your public site runs on WordPress or another platform, the MetriFi connection has no access to it, so there is nothing there for the assistant to change. If your website is built on MetriFi’s AI website platform, changes are still drafted and previewed first, and nothing goes live until a person with permission approves and publishes it, with every version reversible. Either way, the assistant proposes; your team decides.
05Who can make changes, and who can publish them live?
You control this with team roles, so staff can prepare changes while only the people you choose can publish them:
| Role | Draft changes | Publish live | Manage members | Billing & team |
|---|---|---|---|---|
| Owner | Yes | Yes | Yes | Yes |
| Admin | Yes | Yes | Yes | No |
| Editor | Yes | Yes | No | No |
| Contributor | Yes | No | No | No |
This lets a cautious rollout start small: a few people drafting, and a smaller group approving what goes live.
06How do we turn off or revoke access?
You can revoke your AI agent’s access to the MetriFi platform at any time. In MetriFi’s account settings, every AI assistant you’ve connected is listed and has a disconnect button. Disconnecting ends that assistant’s access immediately: its next request is rejected and it cannot renew itself. Individual access tokens are short-lived, one hour each, but an assistant you stay connected to keeps renewing them, so disconnecting is what ends access rather than waiting. A connection that goes entirely unused for 30 days expires on its own.
What data is involved, and how it is connected.
07What data does MetriFi actually work with?
Your website’s content, your rates, and your brand. If you use MetriFi’s conversion tools, it also reads the website analytics you choose to connect. That is the extent of it. It does not pull in member records, account data, or anything from your core.
08How is our analytics data connected?
Through a secure sign-in you control. You connect Google Analytics yourself in your browser, and MetriFi stores only the connection, never your Google password or credentials. You can disconnect it whenever you like.
09Where does our member data live?
In your vendors’ secure systems, not on your website. The site simply links out to online banking, account opening, and loan applications, which run inside those vendors’ platforms. There is no pool of member data on the site for anyone, or any AI, to reach.
The documentation and the next step your team needs to move forward.
10Where is your security and due-diligence documentation?
Start with the due-diligence documents in our Security Center, which has our business and insurance records. Further documentation on security and AI governance is available on request: how the platform is built, how data is handled, access and AI controls, hosting, backups, subprocessors, and compliance. Ask your MetriFi contact, and we will send what your IT team or AI committee needs and help them through their review.
11How do we connect, and can we start with limited access?
Setup takes a few minutes from your AI app, with step-by-step instructions at platform.metrifi.com/connect. One connection covers all of MetriFi’s tools (GEO, CRO, and SiteBuilder) and cannot be limited to a single product, but the MetriFi connector’s settings in your AI app let you block any tool you do not want your assistant to use. Because access is revocable, many teams start with one person and a short list of allowed tools, then expand once their committee is comfortable.
Ready to connect, or need more for your committee?
Ask your MetriFi contact, or schedule a call, and we’ll help your IT team or AI committee through their review.