Privacy & Telemetry

Telemetry

Atlassian for VS Code collects and sends analytics to help us better understand errors and common usage trends.

Personal Data

The extension collects and transmits the following personal data through its analytics system:

Data Collected

1. Machine Identifier: A unique identifier (env.machineId) for your VS Code installation
2. Atlassian Account ID (AAID): Your unique Atlassian account identifier when authenticated with Jira or Bitbucket services
3. User Domain Classification: Determines if you are an Atlassian employee (checks if email ends with @atlassian.com) and sends this as userDomain: 'atlassian' or userDomain: 'not-atlassian'
4. Site Information:
   • Hostnames and instance types (cloud vs server) of connected Jira/Bitbucket instances
   • Site IDs for cloud instances
5. Usage Analytics:
   • Actions performed (creating issues, pull requests, etc.)
   • Features used and configuration changes
   • Error information with sanitized stack traces
   • Performance metrics

Data Protection Measures

• Stack traces are sanitized to remove personal file paths (replaces /Users/<username>/ with /Users/<user>/)
• Error messages are sanitized to remove IP addresses
• File paths in error logs are anonymized

Event Types

We categorize events into the following types:

1. track_event
2. operational_event
3. screen_event
4. ui_event

Destination

We send all production analytic events to the following domain:

https://as.atlassian.com

Experimentation

The extension uses feature flags and experimentation to gradually roll out new features and test user experiences. This system collects additional data for feature targeting and experiment analysis.

Data Collected for Experimentation

1. Machine ID: Uses the same VS Code machine identifier (env.machineId) as the primary anonymous identifier for feature flag targeting
2. Tenant Association: When authenticated with Jira, the extension sends your primary Jira site/tenant ID to determine which features and experiments you should receive
3. Feature Flag Analytics:
   • Which feature flags are enabled/disabled for your session
   • Experiment group assignments and parameter values
   • Feature usage patterns for A/B testing analysis

Experimentation Infrastructure

• Uses Statsig's Feature Gate service for feature flag management

Data Protection

• Uses the same machine ID as main analytics (no additional personal identifiers)
• Tenant ID is only collected when you're authenticated with Jira and have it enabled

Opt-Out

Atlassian for VS Code respects VS Code's telemetry.telemetryLevel setting. To disable all analytics and experimentation, set telemetry.telemetryLevel to off.

Rovo Dev

Atlassian for VS Code provides a user interface for Rovo Dev's serve mode. Learn more about Rovo Dev and how Rovo handles your data here: https://support.atlassian.com/rovo/resources/