Privacy Policy
What Penstock collects, why, for how long, and what you can ask of us. This page is a description of what the software does today.
Last updated: 27 October 2026
Short version
- The editors and the command line have no telemetry. They do not report what you do, what you open or what your diagrams contain.
- Your diagrams stay on your machine. They go only to the process engine you configure, when you deploy, and to the AI agent you choose, if you use the AI chat.
- The licence service sees a licence key or token, a one-way hash of your machine's id, the host name as a label, and the network address a request comes from. It never sees a diagram.
- Payments are handled by Polar, the merchant of record. We never see your card.
- The website sets no cookies and has no advertising or social trackers.
- We do not sell your data.
1. Who is responsible
The controller of the personal data described here is Oleksandr Havrysh, an individual in Poland (European Union). Write to oleksandr.havrysh5@gmail.com for anything about this policy or your data.
2. The software: plugin, extension and command line
Penstock sends something over the network only when you act, apart from the daily licence renewal. The complete list, with when, where to and what is sent, is the table on Security and privacy. In short:
- Deploy sends the file you deploy and the profile's credentials to the engine address you configured, and nothing else.
- Opening the connector browser asks
api.github.comandcodeload.github.comfor public connector templates, at most once a day. No credentials and no project data go with it. - The licence service is described below.
- The AI chat starts an agent of your choice on your machine. What that agent sends to its provider is between you and that provider.
There is no update polling, no crash reporting and no usage statistics. Passwords and secrets go to the secret store of your tool, never to a project file.
3. The licence service
The licence service is a small program (a Cloudflare Worker) that turns a trial, a licence key or a Team key into a signed token. This is everything it receives and keeps.
| When | What it receives | What it keeps |
|---|---|---|
| A machine starts its 30-day trial | A one-way hash of the machine's id, and the network address of the request. | The machine hash, the start of the trial, and a shortened one-way hash of the network address. The address itself is not stored. |
| You activate a licence on a machine | The licence key, the machine hash and the host name as a label. | The id of the key, the id of the activation, the machine hash and the time. The key and the label are passed to Polar, which holds the activation. |
| The daily renewal, and releasing a machine | The signed token it issued before. | Nothing new, except the release of a machine's place. |
| A pipeline asks for a token | A Team key and the runner's machine hash. | The id of the key, the runner's machine hash and the time, to cap the number of runners. |
It does not receive your e-mail address. When you sign in, the code is requested from Polar directly. It does not receive diagrams, file names or project names. The host name is sent as a label so that you can recognise a machine, and it can contain a name if you gave your computer one. The network address of a request is visible to the service and to Cloudflare, which runs it, as it is to any web server, and is used to limit abuse: at most five new trials a day from one address, and a rate limit on requests.
How long it is kept
- The shortened hash of the network address of a trial is kept for 90 days after the trial starts, and then deleted.
- The machine hash and the start of a trial are kept so that reinstalling does not start a second trial. They are not linked to your name or e-mail address by the licence service.
- Activation records are kept while the licence they belong to exists, so that a place on a key can be freed and counted correctly.
The purposes are the trial and the licence you asked for, the limit of three machines for each key, and protection against abuse. The legal basis is the performance of the contract you enter by using the software under its licence (GDPR Article 6(1)(b)) and our legitimate interest in preventing abuse and keeping the service secure (Article 6(1)(f)).
4. Payments
Payments, VAT, invoices and refunds are handled by Polar Software, Inc. (polar.sh), the merchant of record, and its payment processors. When you buy, you give your payment details and e-mail address to Polar under Polar's own privacy policy, and Polar is an independent controller of that data. As the seller we can see in Polar's dashboard your e-mail address, country and subscription status. Penstock never sees your card number. Signing in on a new machine asks Polar to e-mail you a code.
5. This website
- No cookies, no advertising and no social trackers. The fonts are served from this site.
- The site is hosted on GitHub Pages, which keeps its own server logs under its own policy.
- It counts page views with Cloudflare Web Analytics, which uses no cookies, does not fingerprint visitors and does not follow them across sites. That script is the only thing the site loads from another address.
- A Buy button is a link to Polar's checkout. Opening it sends you to a page that Polar operates under its own policy.
- The links to the marketplaces, to GitHub and to npm lead to sites with their own policies. We see only the aggregate download and page-view counts they show us.
6. Support and e-mail
If you write to oleksandr.havrysh5@gmail.com or open an issue on GitHub, we use what you send only to answer you and to reproduce the problem. A GitHub issue is public. Do not post a diagram you do not want to share. A file sent by e-mail is used only to reproduce the problem.
An application for a free education or open-source licence, sent to the same address, is read by the owner and deleted after the licence is issued or the request is declined. The licence key itself is issued through Polar, which then holds the address it was issued to, as it does for a paid licence.
7. Who else handles data
- Cloudflare, Inc. runs the licence service and its database. It acts as a processor on our behalf.
- Polar Software, Inc. is the merchant of record. It is an independent controller for payments and holds licence keys and activations.
- GitHub Pages hosts this website.
These providers can process data outside the European Economic Area. They describe the safeguards they use, such as standard contractual clauses, in their own documentation. We do not sell or share personal data with anyone else.
8. Your rights
Under the GDPR you can ask for access to your data, for correction, for erasure, for restriction, for a portable copy, and you can object to processing that is based on our legitimate interest. Write to oleksandr.havrysh5@gmail.com. We answer within one month.
The licence service keys its records by hashes that we cannot link to a person on our own. To find yours we will tell you what we need from you, for example the licence key or the machine. You can free a machine yourself at any time by signing out in your tool, which releases its place on the key.
You can complain to the supervisory authority. For Poland it is the President of the Personal Data Protection Office (UODO), uodo.gov.pl. You may also complain to the authority of the country where you live or work.
9. Children and changes
Penstock is a tool for professionals and is not directed at children. If this policy changes, the date at the top changes.
10. Contact
Oleksandr Havrysh, oleksandr.havrysh5@gmail.com. See About and contact. The technical detail behind this page is on Security and privacy and Buying and signing in. The terms of sale are on Terms.