Skip to content
Load Factor Docs
Open Load Factor

Article

Privacy & request logging

What the Load Factor MCP server records about each request, who can see it, what Load Factor never receives, and what Google sign-in shares.

  • MCP
  • Updated

Overview

The Load Factor MCP server records every request it handles, so your Load Factor admins can see how the connector is used. This page lists what is recorded, who can see it, what Load Factor never receives from your AI client, and what Google shares when you sign in.

What is recorded

For every tool call, resource read and prompt request, the server records:

Recorded Examples
Who Your Load Factor email address and role
Which app The client (for example Claude, ChatGPT or Claude Code), its registration id and version
From where Your IP address and browser or app user agent
What was asked The tool, resource or prompt, and the arguments your assistant sent (anything that looks like a password, token or key is removed)
Scope The ISOs the request covered and the project numbers it touched
Result Rows returned, response size, whether it was trimmed, how long it took
Outcome Succeeded, failed, refused or rate-limited, with the reason

Sign-ins, sign-in renewals, connections and changes to your MCP access are recorded too, including refused ones.

Who can see it

Your Load Factor admins, in Load Factor's admin screens. They can review requests by user, tool, app and day, and see which projects were asked about most.

What Load Factor never receives

The server only sees what your assistant sends it: the name of a tool and the arguments for it, such as a project number or a company name. It never receives the rest of your conversation, your other messages, your files, or the assistant's replies.

Arguments can contain words from your question. If you ask about "NextEra's solar projects in Texas", the assistant may send NextEra, Solar and TX as arguments, and those are recorded.

Where results go

Results go back to your AI client (Claude, ChatGPT or another app) and become part of that conversation. How that provider handles conversations is covered by your agreement with them.

Google sign-in

You sign in with Google, and Load Factor asks Google only for your identity and email address (the openid and email scopes). It never asks for access to your Gmail, Drive, Calendar or any other Google data.

Your AI client never receives your Google password or a Google token. It receives a Load Factor token that works only with the Load Factor MCP server. Load Factor stores the sign-in state it needs, encrypted, so a server update does not sign you out.

Read-only by design

Every tool only reads data. Nothing you or your assistant does through the MCP server can change anything in Load Factor.

Some information is withheld from everyone who uses the MCP server, whatever their plan: landowner names and land-record details, e-mail addresses, phone numbers, street addresses and names of individuals in evidence. See Access & permissions.

Load Factor's privacy policy covers the rest of the Load Factor service.