Privacy Policy
Pipeline Inbox for GitHub Actions (the "Plugin") for JetBrains IDEs, published by Lesstep.
This plugin is not affiliated with, sponsored or endorsed by GitHub, Inc. GitHub and GitHub Actions are trademarks of GitHub, Inc.
Last updated: October 24, 2026
What the Plugin does with your data
- The Plugin talks only to the GitHub hosts in its settings: github.com, and the GitHub Enterprise Server or GHE.com hosts you add (a host met in an address you paste is added to the settings). Run, job and log data travel directly between your IDE and that host, through the proxy configured in your IDE if there is one. Redirects are followed only on the host itself, with one exception: a job's log, which GitHub hands out at a short-lived address of its log storage. That address carries its own signature, and the log is read from it without your token.
- Your personal access tokens are stored in your IDE's password safe on your computer, one for each host. Each token is sent only to its own host, as the authentication header of those requests. No token is sent to any other server, and removing a host from the settings also removes its token from the password safe. Without a token, public repositories on github.com are read anonymously.
- To show which runs are yours, the Plugin reads, from each host you set a token for, your account's login, name and e-mail address, and, from the Git repositories open in your IDE, the e-mail address in Git's
user.email. They are compared with the runs on your computer and sent nowhere. - When you turn on Also list the repositories I was active in lately, the Plugin reads your account's recent activity on each host with a token (the repositories you pushed to, opened pull requests in or reviewed; with your own token GitHub includes private ones) to choose those repositories. It is read from GitHub and used on your computer only.
- To list a workflow's inputs for Run Workflow, the Plugin reads that workflow's file from the repository on GitHub, at the branch or tag you choose. It is read, not run, and kept only while the dialog is open.
- The Plugin keeps the addresses of your hosts, your list filter, and the refresh and notification options in your IDE settings on this computer (left out of Settings Sync). The repositories and owners each IDE project adds, and the repository chosen above its list, are kept in that project's workspace file, which is not shared through version control.
- When you choose to remember the inputs of Run Workflow for a workflow, the Plugin keeps their names and values in your IDE settings on this computer (not in the password safe, and left out of Settings Sync), so that they are filled in next time. Do not remember a value you would not keep in a settings file; running with Remember unticked clears what was kept for that workflow.
- From version 1.0.3, to ask you once for a rating on JetBrains Marketplace (earlier versions do not ask), the Plugin remembers, on your computer only, up to three dates on which its list showed runs, whether it has asked, and the day it asked. From version 1.0.8, the same dates are also used once to mention the free trial, if you have never started it, and the Plugin remembers whether and on which day it has done so. Nothing about this is sent anywhere.
- To tell you once, in the last three days of your 30-day trial, how much of the paid features you used during it, the Plugin counts, on your computer only, how many times you re-ran, cancelled a run, ran a workflow and reviewed a deployment while the trial was running, and remembers whether and on which day it has told you. From version 1.0.2, it also remembers the day your trial ends, as the IDE reported it, so that after the trial it offers to buy a license rather than a trial you can no longer start. Nothing about this is sent anywhere.
- The Plugin remembers whether it has shown its one-time hint on where to find the runs.
- The Plugin has no AI features and sends your code and logs nowhere but your GitHub.
What we do not do
- We do not run any server that receives data from the Plugin.
- We do not collect analytics, telemetry or usage statistics from the Plugin, and nothing is sent automatically when something goes wrong (see below).
- We do not sell or share any data. The Plugin sends us none; what you email us and the website's click counts below are used only by us, and our database provider stores the counts for us.
Our website
This is about lesstep.com only; the Plugin itself still collects nothing. lesstep.com counts how many times its links to JetBrains Marketplace are clicked. For each click it keeps the date and time, which Marketplace page the link leads to, and which lesstep.com page the link was on. It reads the request headers only to leave out automated visits and to find the page the link was on, and keeps nothing else from them. It sets no cookies and keeps no IP address, browser details or anything else that could identify you. The counts are stored with Supabase, our database provider. Like any website, lesstep.com is served by a hosting provider (Cloudflare), which handles each request, including your IP address, to deliver the page.
Error reports you choose to send
If the IDE reports an error in the Plugin, its error dialog offers Report to Lesstep by email. Choosing it opens an email to support@lesstep.com in your email program, containing the error (the exception and its stack trace, which can include names of your repositories, workflows or branches, or a GitHub host's address), the Plugin, IDE, Java runtime and operating system versions, and anything you wrote in the dialog. The whole report is also copied to your clipboard. You read the email before sending it, and nothing is sent unless you send it. We use a report only to fix the problem and to answer you, and delete it when it is no longer needed for that.
Licensing
Licenses are sold and checked through JetBrains Marketplace. JetBrains processes purchase and license information under its own privacy policy.
If you write to us
If you email support, we use your address and message only to answer you, and delete them when they are no longer needed for that.
Changes
If the Plugin starts handling data differently, we will update this page and the date above before releasing that version.