Security
This page explains what Pipeyard can and cannot access, how credentials are handled, and where your data goes.
What permissions Pipeyard requests
Pipeyard requests the following read-only Forge scopes:
read:workspace:bitbucket— to discover the workspace and validate access.read:repository:bitbucket— to list repositories and read repository metadata.read:pipeline:bitbucket— to read pipeline status, step results, and build metadata.read:runner:bitbucket— to read self-hosted runner status.
It does not request write, admin, or delete scopes.
Why those permissions are needed
The dashboard must know which workspace and repositories you can access, and it must read pipeline and runner status to display it. Each scope maps to a specific Bitbucket API resource. Without these read-only permissions, the app cannot build the dashboard.
What customer data is accessed
Pipeyard accesses the following data through Bitbucket APIs:
- Workspace name and slug.
- Repository names, slugs, and pipeline settings.
- Pipeline status, branch, commit, duration, and step results.
- Self-hosted runner status and labels.
What customer data is not collected
Pipeyard does not read or store:
- Source code.
- Build logs.
- Pull request contents.
- Bitbucket app passwords or personal access tokens.
- Names, email addresses, or payment information.
Whether pipeline information is stored
Pipeline information is not stored permanently. It is held in short-lived cache (30 seconds to 5 minutes) while the dashboard is open and is not written to persistent storage. Workspace slug and refresh preferences are stored in Atlassian Forge storage to remember your settings.
How credentials are handled
Pipeyard does not store Bitbucket passwords or tokens. User authentication and token management are handled by Atlassian Forge and Bitbucket OAuth. The app can only make API calls on behalf of a user who has explicitly approved the connection.
Privacy Policy
For more details, read the Pipeyard Privacy Policy.