Log work as another user for Jira Cloud - Privacy policy

    This policy describes how the app processes data when it is installed on a Jira Cloud site. Host this page on a public HTTPS URL (for example on branchcreation.com) and paste that URL in the Atlassian developer console and Marketplace listing.

    Who is responsible

    BranchCreation S.L.U. provides the app. Your organization (the Jira site admin) is the customer. Atlassian hosts the app on the Forge platform (“Runs on Atlassian”): the app does not send data to BranchCreation servers.

    What the app accesses

    With the site admin’s consent at install time, the app uses these Jira scopes:

    • read:jira-work and write:jira-work (with impersonation): read time tracking, create a native worklog as the selected user, and read issue/project context.
    • read:jira-user: resolve display names and avatars for people allowed by the permission matrix.
    • storage:app: store the permission matrix and a short history of worklogs created through the app.

    The app does not use remote egress. It does not send worklogs, comments, or account IDs to BranchCreation.

    Personal data stored in Forge storage

    Per project, the app may store:

    • Actor and target identifiers (Atlassian account ID or group ID) and display names, as configured by an admin.
    • For the acting user: issue key, target account ID and name, time spent, worklog id, and a timestamp (last 50 entries).

    Worklog comments that a user types are stored in Jira as part of the native worklog, not in the app’s storage.

    How data is used

    • Enforce who may log time on behalf of whom.
    • Create the worklog in Jira as the target user.
    • Show the actor a short history of actions they performed.

    Data is not sold, used for advertising, or shared with third parties outside Atlassian’s Forge hosting.

    Retention and deletion

    • Permission rules remain until an admin deletes them or the app is uninstalled (Forge then deletes app storage).
    • History is capped at 50 entries per actor.
    • Uninstalling the app removes Forge storage. Native Jira worklogs stay in Jira; they are the customer’s data.

    To correct or delete personal data stored by the app, a site admin can edit/delete rules, or uninstall the app.

    Contact

    BranchCreation S.L.U. https://branchcreation.com - Email: support@branchcreation.com

    International transfers

    Processing happens on Atlassian Forge infrastructure in the regions Atlassian uses for the customer’s site. The app does not add its own cross-border transfers.

    Changes

    We may update this policy when the app or the law changes. The date at the top will change. Material changes should also be reflected on the Marketplace listing.