Sideways Privacy Policy

Last updated: 20 October 2026

This policy describes how Sideways handles information in connection with its products and this website. It is written for customers, Jira administrators, users of Moving — for Jira, and people who contact Sideways.

Who Sideways is

Sideways is an independent software vendor. Sideways publishes software for Atlassian products. The current product is Moving — for Jira.

Sideways is not Atlassian. Atlassian provides Jira, Atlassian Forge, and the Atlassian Marketplace. Atlassian’s handling of account, billing, and Jira data is described in Atlassian’s own policies and agreements with the customer.

Products covered by this policy

This policy currently covers:

• Moving — for Jira, an Atlassian Forge app.
• This Sideways website, which publishes Sideways legal documents.

If Sideways later offers another product, this policy will be updated to describe that product before it relies on different data practices.

Moving — for Jira

Moving — for Jira is an Atlassian Forge app. It runs on Atlassian infrastructure and uses native Forge and Jira APIs. It helps the person viewing it understand how active issues are moving through workflow.

Jira requests are made on behalf of the user who is viewing the app. Moving can read only Jira work data that user is already allowed to read. The app is currently granted the Jira scope read:jira-work.

What information Moving accesses

Moving reads Jira work data needed to analyze active issues and workflow history. In the current version, that includes:

• Issue identifiers and keys
• Summaries
• Status
• Project
• Created and updated timestamps
• Assignee name and Atlassian account identifier, when an issue has an assignee
• The Jira status catalogue
• Status-change history used to understand workflow movement

To compare current time in status with recent workflow, Moving also reads identifiers, project, creation time, and status history for a limited set of completed issues in the same projects.

Jira issue data may contain personal information. Summaries and other issue fields can include names, assignee information, issue content, and activity information. Sideways does not claim that Moving processes no personal data.

The current scope does not let Moving edit Jira issues. Moving does not request scopes for a Sideways-operated backend, because it does not have one.

How information is used

Moving uses the Jira data it reads to compute and display its analysis while the app is running. That analysis is calculated during app execution and shown in the Forge interface.

Sideways does not use Jira data for advertising. Sideways does not sell customer data. Sideways does not use Jira data to train AI models. Moving does not currently use third-party AI services. Sideways does not send Jira issue data to an external backend.

Data storage

Moving does not have its own database. It does not use Forge persistent storage, including Forge SQL, Forge key-value storage, Forge custom entities, or app-managed entity properties, to store Jira data.

Moving does not intentionally persist Jira issue content outside Atlassian infrastructure. Issue data is processed on Atlassian infrastructure for the app request, and the result is shown in Jira. The customer’s Jira site remains the system of record for issues.

The app may write operational log messages, such as error text and aggregate counts, to the Forge logging service. Those logs remain on Atlassian infrastructure. Sideways does not use them to assemble a separate copy of customer issue content.

Data sharing

Sideways does not sell customer data and does not share Jira issue data with advertisers or data brokers. Sideways does not send Jira issue data to a backend operated by Sideways.

Jira data accessed by Moving is processed through Atlassian Forge and Jira APIs on Atlassian infrastructure. Atlassian processes that data under its relationship with the customer.

If you contact Sideways for support, Sideways receives the contact details and any other information you choose to provide, such as your name, email address, and the contents of your message. Sideways uses that information to respond and to keep a record of the exchange. Sideways does not sell it.

External services

Moving depends on Atlassian Forge and Jira. It does not use external analytics, advertising trackers, or a third-party analytics service. It does not currently use third-party AI services.

This website is static HTML hosted on GitHub Pages. Sideways does not set cookies on it and does not add analytics, advertising, or tracking scripts. GitHub, as the host, may process connection data under GitHub’s own policies. Sideways does not control that hosting infrastructure.

Atlassian Forge

Moving is built and runs as an Atlassian Forge app. Forge executes the app on Atlassian infrastructure. Sideways does not host a separate application server for Moving, and the app is not configured to call out to a Sideways service.

The app’s Jira access is limited to the scopes installed with it. The scope currently used to read Jira work data is read:jira-work.

Security

Sideways relies on Atlassian Forge and on Jira’s permission checks. Because Jira requests run as the current user, Jira applies that user’s existing access.

No method of transmission or processing is perfectly secure. This policy does not claim a security certification, and Sideways does not guarantee that unauthorized access cannot occur.

Data retention

Moving does not keep a Sideways store of Jira issue content. When an app request finishes, Moving does not write that content to a database of its own. Issue data that remains in Jira stays under the customer’s and Atlassian’s control. Operational logs on Atlassian infrastructure are retained according to Atlassian’s practices.

If you contact Sideways, Sideways keeps that correspondence for as long as it is reasonably needed to handle the request and to keep a record of it, and deletes it when it is no longer needed.

Your rights

Depending on where you live, you may have rights to access, correct, or delete personal information, or to object to or restrict certain uses. This policy does not limit rights that applicable law does not allow to be waived.

Jira work data is stored in the customer’s Jira site. Requests about that data should be made to the customer’s organization or through Jira. Moving does not keep a separate copy of issue content, and it cannot delete issues from a customer’s Jira site.

Requests about information you sent directly to Sideways, including support email, can be sent to the contact address below. Sideways will respond within a reasonable time.

Changes to this policy

Sideways may update this policy by publishing a new version on this page and changing the “Last updated” date. The version on this page is the current policy.

Contact

Questions about this policy can be sent to Sideways.

Email: torres.schulten@gmail.com