Trello

Atlassian says Trello customer data is never used to train, fine-tune, or improve AI models or services.

Atlassian says third-party AI providers do not retain request data or use it for model training.

Workspace admins can deactivate Atlassian Intelligence when teams do not want AI processing at all.

AI request data is processed only to generate a response and then returned to Atlassian.

Rovo and Atlassian Intelligence can still process board and workspace data with AI providers when features are enabled.

Atlassian says AI provider requests are processed without retention or training on customer data.

Board visibility, workspace membership, and Trello permissions still let teams restrict who can see board content.

Atlassian documents privacy-rights and information-control paths for account holders.

Users can choose whether to connect third-party services rather than having all integrations forced on them.

Trello data can still flow through subprocessors, organization admins, marketplace apps, and legal disclosure paths.

Account-level Atlassian services can expose more metadata than a stand-alone single-purpose board tool.

Atlassian and its partners use cookies and other tracking technologies for analytics and advertising.

Atlassian uses account and service information for marketing and targeted advertising of products that may interest users.

Board and workspace permissions still control access to Trello content rather than turning it into an advertising feed.

Atlassian documents privacy-rights and communication controls for account holders.

Trello is primarily a collaboration workspace rather than a consumer ad-personalization product.

Retention and deletion still depend on Atlassian account state, workspace configuration, and compliance needs.

Marketplace apps and organizational policies can keep data available longer than a user may expect.

Trello users can export board data and request account information.

Workspace and organization admins can actively manage board access and account lifecycle.

Atlassian documents privacy-rights requests including access, deletion, and restriction where applicable.

The reviewed AI flow says provider request data is not retained for training.

Admins can deactivate Atlassian Intelligence to stop AI processing in the workspace.

Board visibility, workspace membership, and permissions give teams practical control over who can see content.

Export and privacy-rights paths give users and organizations ways to retrieve or manage data.

Users can still limit some third-party exposure by choosing whether to connect outside services.

Administered accounts may still require organization help for some privacy requests and final settings.

Important settings are split across Trello, Atlassian account, and organization administration surfaces.