Security · Reviewed October 10, 2026
Understand access before you connect customer data.
Review the controls and deployment requirements that matter to your team. Ask for current documentation when evaluating a regulated or larger rollout.
Individual account access
Team members work through authenticated accounts. Use roles and permissions appropriate to each person’s responsibilities.
Workspace and API scope
Workspace and permission checks control access to customer data and actions. Treat API credentials as privileged access, and rotate or revoke credentials when appropriate.
Controlled AI and integrations
MCP tools follow the permissions of the API key used. Review any connected AI service, permitted actions, and data destinations before enabling a workflow.
HTTPS connections
Public Greenbubble web and API endpoints use HTTPS. Information handled by an application or connected provider is not automatically end-to-end encrypted across the full workflow.
Before procurement
Request the applicable data-processing agreement, hosting regions, subprocessors, retention and deletion procedures, backup/recovery arrangements, support terms, and any current certification evidence. Confirm the documented scope for your setup.
