Privacy Policy

Jira for Looker Studio Connector

Last updated: April 8, 2026

1. Introduction

This Privacy Policy describes how the Jira for Looker Studio connector ("the Connector"), developed by Flip on Tech, handles your data when you use it to connect your Jira Cloud instance to Google Looker Studio.

2. Data We Access

The Connector accesses the following data from your Jira Cloud instance:

• Issue data: summaries, descriptions, statuses, priorities, assignees, reporters, labels, components, fix versions, sprint information, story points, and other standard and custom fields
• Project metadata: project names and keys
• User information: display names and account IDs of issue assignees and reporters

3. How We Use Your Data

Your Jira data is used exclusively to:

• Fetch issue data from your Jira Cloud instance via the Atlassian Forge platform
• Transform and pass data to Google Looker Studio for visualization and reporting

4. Data Storage

The Connector does not permanently store any of your Jira data. Data is fetched in real-time from Jira when Looker Studio requests it and is passed directly to Looker Studio for rendering. No data is written to external databases, files, or third-party services.

5. Data Sharing

We do not sell, share, or transfer your data to any third parties. Your Jira data flows exclusively between:

• Your Jira Cloud instance (via the Atlassian Forge platform)
• The Connector (Google Apps Script)
• Google Looker Studio

6. Authentication

The Connector uses OAuth 2.0 authentication through the Atlassian Forge platform. Your Jira credentials are never directly handled or stored by the Connector. Authentication tokens are managed securely by Google Apps Script's built-in services.

7. Third-Party Services

The Connector interacts with the following third-party services:

• Atlassian Forge: Used as the backend platform to securely access your Jira Cloud data
• Google Looker Studio: The reporting platform where your data is visualized
• Google Apps Script: The runtime environment for the Connector

8. Data Security

All data transmission occurs over HTTPS encrypted connections. The Connector follows security best practices including:

• No permanent data storage
• OAuth 2.0 authentication
• Read-only access to Jira data
• Minimal data scope (only data needed for reporting)

9. Your Rights

You can revoke the Connector's access to your Jira data at any time by:

• Removing the Connector from Looker Studio
• Revoking the Forge app's access in your Atlassian account settings

10. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated date. Continued use of the Connector after changes constitutes acceptance of the updated policy.

11. Contact

If you have questions about this Privacy Policy, please contact us at: