ConnectDivblox MCP privacy notice
Updated 24 September 2026. This notice covers the hosted Divblox MCP service, operated by Divblox. Contact support@divblox.com about access, correction, deletion or security concerns.
What is processed
Your login is sent to Divblox to authenticate you. MCP does not save your password. It stores encrypted connection credentials, OAuth state, project permissions and limited operation results needed to serve your connection and prevent duplicate changes. Requests can include project, requirement, ticket, checklist, task and user-assignment data.
Where data goes
The service runs in Microsoft Azure in South Africa North and calls the Divblox API. Requested results go to the AI client you connect, such as ChatGPT, Claude, Cursor or VS Code. That provider processes conversation and tool data under its own terms. Choose a client approved for your project data.
Retention and control
Saved grants last up to 90 days; renewal tokens expire after 30 days without use. Upstream expiry, permission changes or revocation can end access earlier. Disconnecting revokes MCP access; it does not delete records already created in Divblox or copies held by your AI client. Expired operation-result caches are cleared after their 24-hour lifetime. Unknown-write markers and reconciliation audit records are retained to prevent accidental duplicate writes. Production operational logs are configured for 30 days and database backups for 14 days.
Operational event logs exclude passwords, access tokens, request bodies and raw business content. Encrypted database records and backups still contain necessary connection and operation data. Restrict permissions to what your agent needs. Contact support for data requests that cannot be completed through Divblox or your connected client.