PRIVACY
PROTOCOL.
AgentFramer is built on the principle that trust is infrastructure. This document defines how we handle the data that flows through our MCP-native generation platform: what we collect, why we collect it, and the controls you hold as a data subject.
System Overview
AgentFramer operates as an MCP-native proxy layer between AI agents and generation providers. Data trust is foundational to this architecture. When your agent dispatches a tool call, we act as a stateful intermediary. We handle authentication, route the job, and return the asset URL. We do not train models on your generations or prompts.
Data We Collect
Collected at registration and used for authentication, billing, and communication.
Telemetry from every agent interaction, used for service reliability and credit accounting.
How We Use Data
Data Sharing
To fulfil generation requests, we transmit prompt data and configuration to third-party model providers. We work with trusted service providers bound by data processing agreements. Legal disclosures may occur when required by valid legal process.
Security Standards
All data in transit is encrypted using TLS 1.3. MCP connections use mutual TLS where supported.
Stored assets and credentials are encrypted at rest using AES-256. Access is audited and role-gated.
Subject Rights + Contact
You hold data sovereignty over your account. You may access, correct, export, or delete your data at any time. Requests are fulfilled within 30 days.
- check_circleAccess and download your data
- check_circleCorrect inaccurate information
- check_circleDelete your account and data
- check_circleOpt out of marketing communications
- check_circleExport generated assets and history
- check_circleRequest data processing information
Privacy questions, data requests, or regulatory inquiries can be directed to our legal team.
legal@agentframer.com