Security Self-Statement: StatusClock (Visual Status Age & Bottleneck Tracker for Jira)
StatusClock: Visual Status Age & Bottleneck Tracker for Jira is built exclusively on Atlassian Forge, a secure, cloud-native platform that provides strong isolation, encrypted storage, and protected execution environments. We take the security of your data seriously and have designed our app to operate with the minimum required access and strong safeguards.
The app respects Jira’s permission model and does not expose any data beyond what the logged-in user is authorized to view. The app stores only minimal configuration data (thresholds and preferences) required for its functionality and does not persist Jira issue content, comments, or user data.
1. General Information
Item | Details |
|---|---|
App Name | StatusClock: Visual Status Age & Bottleneck Tracker for Jira |
App Type | Jira Cloud App (Atlassian Forge) |
Hosting Model | Atlassian Forge (Atlassian-hosted) |
Deployment | Jira Cloud only |
Target Users | Jira Software Users, Project Administrators, Scrum Masters |
Data Sensitivity | Low (configuration settings only) |
2. Authentication & Authorization
Area | Implementation |
|---|---|
User Authentication | Handled by Atlassian (Jira Cloud login) |
Authorization Model | User-as-user (Actions performed on behalf of the current user) |
Permission Enforcement | Fully enforced by Jira (e.g., users can only see issues they have access to) |
Elevated Privileges | Not used |
App Roles | Project Administrator required for configuring thresholds |
3. Permission Scopes Requested
Scope | Purpose | Risk Level |
|---|---|---|
| Read issue details (status, age, summary) to display on board/context | Low |
| Read board configuration to filter issues correctly | Low |
| Read board filter settings | Low |
| Check project details and settings | Low |
| Store project-specific configuration (thresholds) | Low |
| Access project settings for app configuration | Low |
4. Jira APIs Used
API Category | Usage | Permission Context |
|---|---|---|
Search API | Identify "rotting" or critical issues based on age (JQL) | User |
Issue API | Fetch issue details (changelog) to calculate time-in-status | User |
Project API | Load project-specific settings and statuses | User |
Board API | Identify board filters to scope the standup view | User |
Storage API | Read/Write app configuration (thresholds) | App |
5. Data Stored by the App
Data Type | Stored? | Details |
|---|---|---|
Jira Issue Content | No | Never persisted. Fetched on-the-fly and displayed in memory. |
User Information | No | Account IDs used for display/filtering only, not stored. |
Configuration Settings | Yes | Project-level thresholds (Critical/Warning days) and excluded statuses. |
Standup Records | No | Current implementation calculates views dynamically. |
PII | No | No names, emails, or personal data stored. |
6. Data Retention & Deletion
Aspect | Behavior |
|---|---|
Default Retention | Configuration settings retained until modified or app uninstalled. |
Data Deletion on Uninstall | Automatic via Forge (app storage cleared). |
Manual Deletion | Admins can reset/clear settings via the configuration UI. |
Backups | Managed by Atlassian. |
7. Permission Handling Scenarios
Scenario | App Behavior |
|---|---|
Issue Restriction | Issues typically hidden by Jira's API if user lacks permission. App respects this. |
Project Admin Access | Configuration page only accessible to users with project administration rights. |
Board Visibility | Standup modal respects board filter permissions. |
Anonymous Access | Not supported. |
8. UI & Privacy Controls
Area | Design Choice |
|---|---|
User Display | Uses standard Jira UI/Forge components. |
Data Visibility | Users only see data (issues) they already have access to in Jira. |
External Analytics | None (No Google Analytics/Segment). |
9. Data Security
Control | Implementation |
|---|---|
Data at rest | Encrypted by Atlassian (Forge Storage). |
Data in transit | TLS (Atlassian managed). |
External storage | Not used. |
Secrets management | Atlassian managed. |
Tenant isolation | Enforced by Forge. |
10. Operational Security
Area | Approach |
|---|---|
Logging | Forge platform logs only (no PII). |
Monitoring | Atlassian monitoring. |
Rate limiting | Jira API rate-limit aware. |
Caching | Minimal short-term client-side caching. |
11. Compliance Considerations
Regulation / Standard | Status |
|---|---|
GDPR | Compliant (No PII stored, respects "Right to be Forgotten" inherently). |
Enterprise Security Reviews | Supported. |
Atlassian Marketplace | Compliant. |
SOC2 / ISO 27001 | Inherited via Atlassian Forge platform. |
12. Known Limitations & Mitigations
Risk | Mitigation |
|---|---|
API Latency | Standup data loading is asynchronous and shows loading states. |
Large Boards | App limits processing to search results (pagination handled or capped). |
13. Explicit Non-Goals
No Content Analysis: We do not analyze issue descriptions or comments using AI/ML.
No Automated Actions: The app never automatically transitions, assigns, or modifies issues. All actions are user-initiated.
No Performance Scoring: The app does not rank or score users based on issue age or velocity.