1. Who provides this connector
Nabu Facebook is a NabuxAI-operated integration for Facebook. The integration is separate from the platform provider and is not an official product of that provider. Contact info@nabuxai.com with privacy questions.
2. Data relevant to Nabu Facebook
Depending on which account and features you choose to authorize, the connector may process:
- Authorized Page metadata and roles
- Selected posts, comments and message events
- Access-grant and webhook metadata
Page-level scopes and roles granted through the official Meta connection.
3. Why this data is used
To authenticate the connection, provide the features you request, maintain account-specific permissions, troubleshoot failures, and protect service security. Access is limited by available provider permissions and the NabuxAI account that initiates the request.
4. Authorization and third parties
When you connect Facebook, the relevant provider's own terms and privacy notices also apply. The integration may communicate with authorized provider APIs, your connected NabuxAI service and the MCP client you choose to use. Content retrieved by a tool may be included in a response to that client. Avoid requesting data you do not have permission to disclose.
5. Storage and retention
Account-linking details, session or OAuth authorization information, and operational data may be held by the connected service for as long as required to provide the authorized features, maintain security records, resolve support requests, or comply with applicable obligations. A universal deletion period is not claimed for every connector; contact support for the applicable deployment's retention schedule.
6. Your choices and requests
You may stop using the connector, revoke the platform authorization where supported, and ask to access or delete information held by NabuxAI in relation to your account. Include the connector name and sufficient non-secret account details so we can locate the relevant connection. Never email your password, verification code, access token, or private session cookie.
7. Security, changes and questions
No plugin package needs to contain a user's platform credentials. Access to data through the hosted service still depends on its actual deployment, provider access controls and your granted scopes. We may revise this notice when implementation or legal requirements change; the updated date will change with it.