This page explains what data the mParticle Agent reads, what it shows you, how it handles personal data, how that data is secured, and where it is processed. Use this information to determine whether the agent fits your privacy and governance requirements.
\nThe agent runs under your authenticated mParticle session and is scoped to the workspaces and permissions your account can access.
\nBy default:
\nMost requests use catalog metadata, such as event and attribute names, and aggregate analytics, such as counts, volumes, and coverage. When your permissions and workspace configuration allow it, the agent may also inspect user attributes or event values to complete a supported task. For example, it may confirm whether a subscription status field stores values like “active,” “true,” or “premium” so it can propose a rule that matches your data.
\nThis user and event data may include personal information if your organization stores personal information in those fields. The agent is designed to have access to only the minimum amount of data needed to perform the task, including personal information. If value inspection is restricted, the agent won’t access those stored values and may ask you to provide the exact value needed.
\nWhen the agent uses event and user data, that data is processed under the same customer agreements that govern the rest of the mParticle platform, including processing by the model provider described in Where data is processed.
\nThe mParticle Agent is designed not to expose personally identifiable information (PII) in your conversation. It won’t list stored email addresses or phone numbers, it won’t list audience members, and it won’t allow you to extract PII. It can use those fields structurally, for example targeting users who have an email address on file, without revealing anyone’s actual address.
\nThe mParticle Agent can show you non-PII business labels. It can show you fields such as a subscription status field storing “active” and “churned,” when seeing the choices helps you pick the right rule.
\nIndividual user data stays permission-gated: the agent reads a specific user’s profile or event history only when your own permissions allow it and you provide that user’s mParticle ID.
\nIf a naming convention in your workspace embeds personal information in a name or label, the agent can read it the same way other platform features can. As a best practice, don’t include personal information, such as a person’s name or email address, in event names, attribute names, or other labels.
\nThe agent doesn’t modify existing resources or workspace configuration. For supported creation workflows, it prepares a proposal and requires your explicit confirmation before saving it.
\nThe agent cannot:
\nCreating a prediction or audience and activating an audience are deliberately separate steps. After you save an audience definition, you connect and activate it yourself through the normal flow. See Connect an Audience.
\nThe agent may use permission-gated event and user data when available and needed, subject to your own user permissions. Most tasks use metadata, aggregate analytics, and saved definitions. Additional safeguards govern how the agent handles your data:
\nThe agent is not a path for exporting personal data or bypassing your workspace’s privacy controls.
\nThe agent uses the same authentication and permission controls as the rest of the mParticle platform, and those controls are enforced by the platform itself, not by instructions given to the agent.
\nData the agent works with is protected the same way as data anywhere else in mParticle: encrypted in transit and encrypted at rest. Requests sent to OpenAI are encrypted in transit and processed under mParticle’s agreement with OpenAI.
\nAgent activity is logged under the same security model as other mParticle platform logs, and log access is restricted to a limited set of authorized personnel.
\nThe mParticle Agent is optional. If your organization doesn’t want the agent available in its account, contact your mParticle account representative to disable it.
\nThe mParticle Agent uses a large language model from OpenAI to interpret your requests and generate its responses. When you chat with the agent, your messages and the workspace context needed to answer them, such as catalog metadata and attribute values, are encrypted and sent to OpenAI for processing under mParticle’s agreement with OpenAI. Only the prompt and workspace context needed to respond to your request are sent for processing.
\nThe agent processes data primarily in the United States through mParticle’s OpenAI account. Your prompts and data are not used to train or improve OpenAI’s models.
\nmParticle may review agent conversations for limited internal purposes, such as troubleshooting, quality assurance, safety review, and improving the mParticle Agent experience. Those improvements may benefit all customers, but mParticle does not use one customer’s agent conversations, workspace data, business context, or audience definitions to generate recommendations or build audiences for another customer.
\nIf your organization is based outside the United States or is subject to regional data-processing requirements, confirm that US-based processing meets your requirements before using the agent. mParticle plans to support region-specific processing, beginning with the European Union.
\nThe mParticle Agent doesn’t change how data subject requests are handled. It doesn’t create a separate store of consumer data, so requests such as access or erasure continue through mParticle’s existing data subject request process. For more information, see Data Subject Requests.
","frontmatter":{"title":"Data and Privacy","order":5,"seoTitle":null,"seoDescription":null},"parent":{"__typename":"File","modifiedTime":"September 25, 2026"}}},"pageContext":{"slug":"/guides/mparticle-agent/data-and-privacy/"}},"staticQueryHashes":["2950460867"]}