Pango Neuro · Security
Keep advertising data and operating permissions separate by workspace.
Pango Neuro makes account connections, data access, and supported operations available only within the scope you authorize.
- Protected server-side account connections
- Workspace-level data and permission boundaries
- Execution follows your AI client's confirmation and permission settings
Before ad data reaches an AI conversation, three things should be clear: what is connected, who can access it, and which changes can actually run.
Pango Neuro keeps connection credentials on the server and maintains a separate workspace boundary for every brand or client. The AI receives only the data and tool results needed for the request.
01
You do not share ad account passwords
Supported platforms connect through OAuth or the authentication flow provided by that platform. Connection credentials stay on the server instead of being exposed directly in an AI conversation.
- Use platform-provided sign-in and authorization
- Keep connection credentials server-side
- Expose tools only for authorized accounts and permissions
02
Keep each brand or client in its own boundary
Each workspace manages its connected accounts, data, members, and permissions separately. A request cannot use data from a workspace the user is not allowed to access.
- Separate workspaces by brand or client
- Check access against workspace membership and permissions
- Limit requests to the connected account scope
03
Not used to train Pango Neuro AI models
Pango Neuro does not use connected ad data or MCP tool results to train its own AI models. Data handled by an external AI follows that provider's settings and terms.
- No training of Pango Neuro AI models with connected ad data
- The external AI may receive data needed to answer a request
- Review the data controls of the AI service you use