Forge functions, Custom UI resources, storage, and activation counters run on Atlassian services.
Feed The Troll - Jira Cloud App
Trust Center
A buyer-ready view of where Feed The Troll runs, what it can access, what it stores, how activation is measured, and where to report a security concern.
Verified against production version 2.9.0 on 27 August 2026
Runs on Atlassian
Jira Cloud
Forge SQL
No Write Scopes
At a Glance
The production manifest declares no remote backend, external egress domain, or external customer-data database.
Each teammate controls whether others can see their troll, level, streak, XP, and kudos availability.
The support target is an initial response within 1 business day and critical-security triage within 24 hours.
Architecture
Feed The Troll is a Forge app for Jira Cloud. Jira events invoke Forge functions, the app calculates privacy-safe game progress, and Forge SQL stores the resulting game state. Custom UI modules communicate with the backend through @forge/bridge.
Trust boundary: The app has no remote backend and no external production database. Customer game data stays inside Atlassian-hosted Forge services.
- Node.js 22 Forge runtime
- Forge SQL app storage
- Jira issue, project, global, and dashboard Custom UI modules
- Parameterized SQL queries and additive migrations
- No Jira write scopes
- No personal access tokens requested from customers
Jira & Forge Permissions
The production manifest requests 6 read or storage scopes. Each scope supports a documented game function.
| Scope | Why It Is Required |
|---|---|
read:board-scope:jira-software | Read board context needed for Jira Software progression and sprint features. |
read:issue-details:jira | Read issue metadata needed to recognise supported Jira activity. |
read:jira-work | Read issue, comment, status, and worklog event metadata used to calculate XP. |
read:jira-user | Resolve account identity, display names, and avatars for permitted app surfaces. |
read:sprint:jira-software | Recognise sprint lifecycle events used by team quests and raids. |
storage:app | Store game state, configuration, privacy choices, and deduplication records in Forge SQL. |
The app does not create or edit Jira issues, comments, fields, worklogs, workflows, or project settings.
Data & Retention
The app stores only the identifiers, configuration, and derived game state needed to operate. It does not store issue titles, issue descriptions, comment bodies, worklog text, attachments, or customer files.
| Data Category | Purpose | Retention |
|---|---|---|
| Account & project identifiers | Associate permitted users, projects, trolls, and settings. | Until app data is deleted. |
| Troll profile & privacy settings | Operate progression, appearance, and teammate visibility. | Until app data is deleted. |
| XP, quests, kudos & activity | Calculate rewards, streaks, caps, quests, and activity views. | Operational history; obsolete records may be deleted. |
| Village, raid & guild state | Operate project villages and cross-project Team Villages. | Until deleted by an admin or app data is deleted. |
| Admin configuration | Apply rollout, harmony, privacy, and license-project choices. | Until changed or app data is deleted. |
| Metric deduplication | Ensure each activation counter is emitted at most once per installation. | Until app data is deleted. |
Uninstall deletion and geographic placement follow Atlassian Forge platform behaviour. See the full Privacy & Security Policy for user rights and deletion requests.
Activation Telemetry
The app emits 8 one-time installation-level counters through Atlassian Forge custom metrics. They measure setup, troll creation, first positive XP, quest activation, village discovery, and Team Village creation.
- No Jira issue content or issue keys
- No project names
- No user or Atlassian Account IDs
- No troll names, comments, worklogs, or configuration values
- No custom metric dimensions
- No third-party service receives Forge activation counters
A Jira administrator can disable custom metrics access through Atlassian Administration without affecting product functionality.
Marketplace storefront analytics: The public 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 8 activation counters.
Security Status
| Control | Current Status |
|---|---|
| Marketplace listing | Public & approved |
| Runs on Atlassian | Visible |
| Marketplace Privacy & Security form | Approved |
| External app remotes | None |
| External production database | None |
| Personal access tokens | Not required |
| Bug Bounty badge | Not currently claimed |
| Cloud Fortified badge | Not currently claimed |
Operational logs are sanitised and do not intentionally contain issue content. The app uses parameterized SQL queries, validates resolver input, and filters Team Village reads using Jira permissions and user privacy choices.
Support & Security Reports
Product Support
Use the drinkits support portal for setup, licensing, privacy, or product questions.
Target initial response: within 1 business day.
Security Contact
Email [email protected] or open a ticket marked Security Issue.
Critical report triage target: within 24 hours.
Include enough detail to reproduce the issue, but do not send credentials, access tokens, or customer data.