Privacy & Security Policy

Introduction & Scope

This Privacy and Security Policy governs data processed by Feed The Troll (the “App”), a Jira Cloud application developed by drinkits DEV and distributed via the Atlassian Marketplace.

This policy applies to all end-users, project members, and Jira System Administrators who interact with the App within their organisation’s Atlassian Jira Cloud instance.

What the App Does

Feed The Troll gamifies your team’s existing Jira workflow. When team members log time, transition issue statuses, leave comments, complete sprints, or send a teammate a Toast, the App awards XP to a personal “troll” character. Trolls level up, evolve through five stages, and collectively shape a shared team village. No new workflow is imposed - the App observes activity that already occurs inside Jira.

Data Storage (Forge Infrastructure)

All App data is stored exclusively in Atlassian Forge SQL - a TiDB-compatible managed database that runs entirely within Atlassian’s infrastructure. There are no external servers, no cloud buckets, and no off-platform databases of any kind.

What Is Stored and Why

On Uninstall

When the App is uninstalled from a Jira instance, the Forge platform automatically deletes all associated Forge SQL data, after Atlassian's 28-day retention window. No data remains on any infrastructure we control.

What Data We Process

The App processes the minimum data necessary to deliver the gamification experience. The following describes precisely what is read from Jira and what is derived and stored.

Data Read from Jira (Not Stored)

To detect XP-awarding events, the App receives event notifications from Jira and uses these parts of them, plus a few narrow reads for specific rules:

• Jira Account ID - the Atlassian-assigned opaque identifier for the user who performed the action (e.g. 5f7a3b...). This is not a name or email address.
• Project ID - to associate the event with the correct village.
• Event type and timestamp - what happened (e.g. a worklog was created) and when.
• Issue key - the Jira issue identifier (e.g. PROJ-42) stored alongside the XP event for the activity log.
• Status category - whether an issue's new status is in Jira's To Do, In Progress or Done category, so a status counts whatever it is called.
• A sprint's projects and state - the projects of a sprint's issues (a JQL search that returns the project and nothing else), the board's project when a sprint has no issues, and whether a sprint is over, so its raid and team quests reach the right village.
• Counts of work in progress - per project, how many issues are in progress and how many of those have not moved for a week. These are JQL counts with no issue content, used for the village's defence.
• Comment count - how many comments a flagged issue has, the number only, for the blocker bonus.
• Estimate and time spent - of an issue that was just finished, for the Estimation Sage quest.

Jira API Scopes Requested

The App declares the following Forge permission scopes in its manifest. No other scopes are requested.

The App does not request write access to Jira issues, attachments, users, or any other Jira content. All write operations are limited to the App’s own Forge SQL storage.

User-Controlled Visibility

Each user controls what teammates can see via five privacy toggles in the Gear tab of the My Troll issue panel. A save applies to every troll that person owns, not only the project in view. These settings do not affect data storage - they only govern what is displayed to other users within the App.

Admin-Controlled Visibility

A Jira System Administrator can also set Who sees trolls to Only your team. Then the troll is shown only to people who hold Jira’s View Development Tools permission, hiding it from anyone without that permission (such as external or portal customers) across the issue panel and the Team Village. This is a display control only - it does not change what data is stored. It is off by default.

Troll Sprint

Troll Sprint is a short running game in the Team Village. By default no time or result of a run leaves the browser or is kept in browser storage; the game only adds to two counts (the game opened, a run finished), described under Atlassian-Hosted Activation Metrics, and the day’s best time lasts only until the page is reloaded. The My Troll panel remembers in the browser only the date on which it last opened the game, so it invites a player once a day.

A player can turn on racing teammates in the game. It is off until that player turns it on, it is not offered under Harmony Mode or Ethics Mode, and the game shows exactly what is shared before it is turned on. For that player, the best time on each day’s track and its ghost are stored (see the table above). Teammates who can see the player’s troll in a village can race that ghost and see the troll name and the difference in time, never an account ID. Meeting the day’s Sprint Goal earns 10 XP once a UTC day, recorded like any other XP, so teammates see it only if the player shares their XP. A player who shares also sees on the Troll Sprint sign how many teammates ran today’s track, a number and never who. Turning racing off deletes the player’s runs at once. A Jira System Administrator can turn Troll Sprint off for the whole site.

Third-Party Sharing

We do not share, sell, rent, or otherwise transfer any end-user data to third parties. This section is unambiguous:

• No advertising networks or marketing platforms receive any data.
• No third-party analytics or crash-reporting services (e.g. Datadog, Sentry, Mixpanel) are integrated into the App runtime.
• No external APIs are called at runtime. The App has no outbound network access beyond Atlassian’s own Jira and Forge platform APIs.
• No data is shared between different organisations’ Jira instances. Forge SQL storage is scoped to a single tenancy.

Atlassian-Hosted Activation Metrics

The App emits twelve one-time, installation-level activation counters through Atlassian Forge custom metrics. They indicate whether an installation reached admin onboarding, its first enabled project, its first Team Village, a completed first run, the troll creation screen, a hatched troll, a created Traveling Troll, the choice of “Not now” instead of one, its first positive XP, its first activated quest, its first opened village, and the first teammate seen there.

Three further counters record repeatable plan events: a site moving to the free plan, a site moving off it, and a free-plan limit being reached. Four more count Troll Sprint use: the game opened, the game opened from the My Troll panel, a run finished, and racing teammates turned on. Those are counted in Forge custom metrics only; the App stores no record of them, and a Troll Sprint count carries no person, time, track or result.

The counters do not contain Jira issue content, issue keys, project names, user or account IDs, troll names, comments, worklogs, configuration values, or custom metric dimensions. Atlassian attaches the platform context needed to operate its metrics service, such as the app environment, version, module or function, and installation site. The app developer can view these counters through Atlassian’s Developer Console and App Metrics API.

No third-party analytics service receives this data. Jira administrators can disable custom metrics access for the App through Atlassian Administration. Disabling metrics does not affect product functionality.

Marketplace Storefront Analytics

The public Atlassian Marketplace listing currently has a vendor-configured Google Analytics 4 property for storefront page analytics. It runs on the Marketplace listing, not inside Feed The Troll, and does not receive Forge SQL data or the App’s activation counters.

GDPR & Data Rights

For organisations with users in the European Union or European Economic Area, this section describes the GDPR framework governing the App.

Controller and Processor Roles

Your organisation (the Jira Cloud customer) is the Data Controller: you determine the purpose and means of processing personal data by choosing to install and configure the App within your Jira instance.

drinkits DEV acts as a Data Processor operating through Atlassian’s Forge platform. We process only the data necessary to deliver the App’s stated functionality, in accordance with your instructions as expressed through the App’s configuration.

Individual Data Rights

The following rights are available to data subjects. Because the App stores only Atlassian Account IDs (not names or email addresses), identity verification is handled via Atlassian’s existing authentication.

Data Retention

Data is retained for as long as the App is installed and active in your Jira instance. The one exception is Troll Sprint runs, which are deleted the day after their track’s day, or at once when the player turns racing off; no other record expires on its own during an active installation. Upon uninstall, all Forge SQL data is deleted automatically by the Atlassian platform after its 28-day retention window with no further action required from you.

International Transfers

The App does not transfer data across borders independently. Any geographic placement of data is determined by Atlassian’s infrastructure and your organisation’s Jira Cloud region selection, and is governed by Atlassian’s Data Processing Addendum and Standard Contractual Clauses where applicable.

CCPA (California)

We do not sell personal information as defined under the California Consumer Privacy Act. California residents have the right to know what data is collected (this policy), to request deletion (contact us or uninstall the App), and to opt out of sale (not applicable - no sale occurs).

Contact Us

For any privacy or security question, request, or concern related to Feed The Troll, contact us through one of the following channels:

Policy Updates

We will update this policy when the App’s data practices change. Material changes will be announced via the Atlassian Marketplace changelog. The effective date at the top of this page will reflect the most recent revision.