Data Handling
- Last updated:
- August 28, 2026
This operational guide describes the product as it works today. It complements Agentzia's formal Privacy Policy with a concise view of the current service.
Account, run, and billing records.
- Account
- Email address, plan and credit balance, subscription status, account creation time, and hashed MCP-token metadata when a manual token is used.
- Run input
- The submitted public URL or content, optional competitor names, source, status, and timestamps.
- Run output
- Participant decisions, citations, reported research traces, observer synthesis, usage, and error details.
- Billing
- Credit events and checkout identifiers. Stripe processes card details; Agentzia does not store card numbers.
Models and research services receive what they need to run the study.
- OpenRouter
- Routes the current participant and observer model requests and reports model usage and cost telemetry.
- OpenAI
- GPT-5.6 Luna processes up to four matched ChatGPT participant situations. GPT-5.6 Terra produces one observer synthesis after the participant decisions.
- Gemini 3.7 Flash processes the same set of up to four participant situations for the Gemini client proxy.
- Anthropic
- Claude Sonnet 5 processes the same set of up to four participant situations for the Claude client proxy.
- xAI
- Grok 4.6 processes the same set of up to four participant situations for the Grok client proxy. During the current transition, OpenRouter supplies web research rather than reproducing the complete consumer Grok harness and X search policy.
- Research tools
- Provider-native routes and OpenRouter provide model-directed research using provider defaults. Agentzia does not impose search-result, page-count, or fetched-page token limits.
- Firecrawl
- The submitted public URL is used for the separate visibility and page-inventory track.
- Infrastructure
- Vercel runs the web application and Supabase stores account and report records.
Private by account. Retained until deletion.
- Access
- Signed-in reports are restricted to their owning account. Guest reports use an unguessable claim token until they are attached to an account.
- Database
- Row-level security blocks users from reading another account's records. Server credentials are kept outside browser code.
- Retention
- There is currently no automatic expiry. Run inputs, traces, and reports remain stored until you delete the report.
- Report deletion
- A signed-in user can permanently delete a completed or failed report from its report page. This removes the submitted input, research artifacts, traces, citations, and generated report from Agentzia's primary database.
- Account deletion
- Self-serve account deletion is not available yet. Email support to request deletion of the account and remaining account records.
Use public pages and non-sensitive content.
- Public URL
- URL analysis is designed for pages that the model and research tools can reach without credentials.
- Direct content
- MCP can analyze supplied content, but that content becomes part of the stored run.
- Avoid
- Do not submit secrets, personal data, confidential drafts, authenticated pages, or regulated information.
- OAuth
- MCP authorization requests the email scope. Manual MCP tokens are stored only as hashes and can be rotated.
Accountability
Agentzia is operated by Morphologic AI Inc. Read the complete policy before submitting content.