Linear

Linear's reviewed privacy source does not present customer issue content as default AI training data.

Linear frames processing around providing and improving the service rather than overt customer-content training language.

Workspace and permission controls can still limit who reaches sensitive issue data before new features are used.

Consent and objection rights give some leverage if future processing changes materially.

Linear's policy allows service improvement processing and does not provide a detailed AI-training opt-out section.

The privacy policy is broad enough that users still need to watch for future AI-adjacent feature rollouts.

Workspace data can still flow through integrations, processors, legal requests, and organization admins.

Business transfers such as mergers or acquisitions can transfer collected personal data to another controller.

Linear discloses service-provider sharing and privacy-rights paths rather than hiding them.

Connected apps and third-party services are generally customer-enabled rather than mandatory.

Linear says California residents can request that certain third-party direct-marketing disclosures stop.

Linear can create aggregated, de-identified, or anonymized data that is no longer tied to a particular user.

Website and product analytics are collected to analyze trends, understand the user base, and improve the service.

Third-party analytics providers and cookies are still part of the service stack.

Users can manage some account and communication preferences directly.

Browser settings can reject some cookies rather than requiring every choice to be made inside Linear alone.

Linear distinguishes essential, functional, and performance or analytical cookies.

Retention is described generally rather than with simple data-specific deletion windows.

Linear may retain personal data as long as the account is open or otherwise necessary to provide services.

Users can request access, deletion, correction, and portability where applicable.

Linear ties retention to having an open account or needing data to provide the service.

Users can object to some processing or request restrictions in certain jurisdictions.

Workspace permissions, connected apps, exports, and privacy requests give admins practical controls.

Users can request access to their data and ask for corrections or deletion where applicable.

Browser settings allow users to reject at least some categories of cookies.

Communication and direct-marketing controls are documented for some jurisdictions.

Some privacy outcomes still depend on workspace owner or admin configuration.

Linear notes that some requests may not be fully honored if they are impractical, harm others, or are not required by law.