Privacy Policy
Updated October 13, 2026
Draft for review — not legal advice.
This policy explains what personal data Workflow Exit collects when you use https://workflowexit.com, why we collect it, who we share it with, and what rights you have. "We" and "us" mean the operator named in section 1.
The short version
- The free report runs in your browser. Your Pipedream export is parsed and analyzed on your device. It is not uploaded for the free report.
- Conversions are processed in memory. When you convert workflows, the workflow definitions are sent to our server over HTTPS, converted, and not stored after the response is returned.
- AI rewrite uses Anthropic. If a step needs an AI rewrite, the code of that step is sent to Anthropic's Claude API.
- Payments go through Polar. Polar is the Merchant of Record. We never see your card details.
- No advertising cookies. Our analytics (Vercel Web Analytics) does not use cookies.
1. Who is responsible for your data
The controller of your personal data is:
[Operator name] [Address] Republic of Moldova Email: hello@workflowexit.com
Workflow Exit is run by a private individual. It is not a company. Write to the email above for any privacy question or request.
We follow the EU General Data Protection Regulation (GDPR) and the personal data protection law of the Republic of Moldova.
2. What data we process, and when
2.1 When you visit the site
Our hosting provider, Vercel, processes technical data such as your IP address, browser user agent and the pages you request. This is needed to deliver the site and protect it from abuse.
To limit abuse of forms and conversions, our server keeps short-lived request counters keyed by a salted hash of your IP address (never the address itself). Expired counters are deleted within a few days.
We use Vercel Web Analytics to count page views. It does not use cookies. According to Vercel, visitors are identified by a hash created from the incoming request, and that visitor session is discarded after 24 hours. It records data such as the page URL, referrer, country or city, browser, operating system and device type. We see only aggregated statistics.
2.2 When you create a free report
The export you choose (a ZIP archive, a GitHub Sync repository or workflow JSON files) is read and analyzed entirely in your browser. It is not sent to us for the free report.
We record anonymous usage counts so we know how the tool is used:
- the number of workflows in the report;
- how many workflows got each traffic-light rating (green, yellow, red);
- the input format.
These counts contain no workflow names, code, props or other workflow content, and we do not link them to you.
If part of your export isn't recognized, the report offers a button to send us its structure. Only when you click it, your browser sends field names and value types of up to three files; every value (names, code, IDs, text) is replaced with a placeholder first, and you can preview exactly what is sent. We keep these samples for 24 months to improve the parser.
2.3 When you convert workflows (the free workflow and paid plans)
To convert a workflow, your browser sends its definition to our server over HTTPS. The definition includes the workflow structure, the code of code steps and the configured props that are not secret. Props can include personal data, such as email addresses, names in message templates or spreadsheet IDs. We use this data only to produce the conversion.
The definitions are processed in memory and are not stored after the response is returned to your browser.
For the free workflow, we store a fingerprint of the project (a hash of its workflow IDs), a salted hash of your IP address (we don't store the address itself) and a hash of the converted workflow's ID (or, for a workflow without a Pipedream ID, of its folder and name). We use them only to limit the free conversion to one workflow per project and a few per day, and delete them after 24 months. For paid plans we store, per order, a hash of each converted workflow's ID (or folder and name, as above), how often it was converted and how many AI calls were used, to apply your quota.
Pipedream exports never contain secret values or OAuth tokens. Pipedream replaces them with <redacted> or with an account ID before you download the export. We never ask for your Pipedream API key in the web app.
If your own code contains hard-coded secrets (for example, an API key typed directly into a code step), that code is sent to us like any other code. Remove or rotate such secrets before you convert.
2.4 When a step needs an AI rewrite
Some code steps cannot run on n8n as they are, for example because they import npm packages that n8n Cloud cannot load. For those steps, we send the code of the affected steps, with the context needed to rewrite it, to Anthropic's Claude API. Anthropic acts as our subprocessor.
Anthropic's Commercial Terms of Service state that Anthropic may not train models on customer content from its services. Anthropic handles API data under those terms and its privacy policy.
Steps that do not need an AI rewrite are not sent to Anthropic.
2.5 When you buy a plan
Polar (Polar Software Inc.) is the Merchant of Record and the seller of record for every purchase. Polar runs the checkout and collects your payment details, billing information and any data it needs for tax and invoicing. Polar's privacy policy and buyer terms apply to the checkout. We never see or store your card details.
After a purchase, Polar sends us the order details we need to deliver it. We keep an order record with:
- the order ID;
- the email address you gave Polar;
- the plan and its workflow quota;
- which Pipedream workflow IDs were converted under the order, and when;
- how many conversions were run.
We use this record to deliver your purchase, apply your quota, handle refunds and keep the accounting records the law requires.
If you use the key restore page, we check the email address and Polar order ID you enter against this record and, if needed, against Polar's record of the order. We do not store what you enter there.
2.6 When you contact us
If you email us or send a support request, we process your email address, your message and anything you choose to attach. We use it to answer you and to handle refunds or complaints.
2.7 Storage in your browser
The site stores two things in your browser:
- Your access key, in local storage, so you can return and use your plan without logging in.
- A purchase claim code, a random code in local storage and IndexedDB, so that only the browser that started a checkout can collect the access key afterwards. It contains no personal data.
- The parsed project, temporarily, in IndexedDB, so you do not have to upload your export again after you return from the Polar checkout. It is deleted once the payment page has loaded it, or after 24 hours.
Both are needed for features you ask for. Neither is used for tracking. You can delete them at any time by clearing the site data for workflowexit.com in your browser settings. Save a copy of your access key first. If you lose it, you can show it again on the key restore page, or email us with your order number.
We do not use advertising cookies or third-party tracking cookies. The Polar checkout runs on Polar's pages and is covered by Polar's policies.
3. Why we use your data and our legal basis
| Purpose | Data | Legal basis (GDPR Art. 6(1)) |
|---|---|---|
| Deliver and secure the website | Technical request data | Legitimate interests in running a secure website |
| Understand how the site is used | Cookieless, aggregated analytics; anonymous usage counts | Legitimate interests in improving the tool |
| Convert workflows, including the free workflow | Workflow definitions | Performance of a contract, or steps you ask for before a contract |
| AI rewrite of code steps | Code of affected steps | Performance of a contract |
| Deliver purchases and apply quotas | Order records | Performance of a contract |
| Keep accounting and tax records | Order records | Legal obligation |
| Answer support requests, refunds and complaints | Email address, messages | Performance of a contract or legitimate interests |
| Defend or exercise legal claims | Order records, correspondence | Legitimate interests |
Where we rely on legitimate interests, you can object (see section 7).
4. Who we share data with
We use the following providers. They process data only to provide their service to us, or, in Polar's case, to run the sale.
| Provider | What it does for us | Data involved |
|---|---|---|
| Vercel Inc. (USA) | Hosts the website and the server functions that run conversions; provides Vercel Web Analytics | Technical request data; workflow definitions while a conversion runs; aggregated analytics |
| Railway (USA) | Hosts our database. Data region: [Region] | Order records, anonymous usage counts, support requests |
| Polar Software Inc. (USA) | Merchant of Record: checkout, payment, sales tax, invoices and refund processing | Checkout, payment and billing data (collected by Polar); order details shared with us |
| Anthropic, PBC (USA) | Claude API for AI rewrite of code steps | Code of the steps that need a rewrite |
Their privacy policies: Vercel, Railway, Polar, Anthropic.
We do not sell your personal data. We do not share it for advertising. We may disclose data if the law requires it, for example to a tax authority or a court.
5. International transfers
We are based in the Republic of Moldova, and our providers are based in the United States. Your data may therefore be processed outside your country, including outside the EU and the European Economic Area.
When data leaves the EU or EEA, we rely on the safeguards our providers offer, such as the European Commission's Standard Contractual Clauses or, where a provider participates, the EU-U.S. Data Privacy Framework. You can ask us for more information about these safeguards.
6. How long we keep data
| Data | How long |
|---|---|
| Your Pipedream export (free report) | Never received by us; it stays in your browser |
| Workflow definitions sent for conversion | Not stored after the response is returned |
| Code sent to Anthropic for AI rewrite | Handled under Anthropic's Commercial Terms |
| Order records | As long as tax and accounting law requires |
| Anonymous usage counts | 24 months |
| Support emails and requests | 24 months after the last message |
| Request counters (hashed IP address) | Until the counting window ends, deleted within a few days |
| Access key and claim code in your browser | Until you clear them |
| Parsed project in your browser | Until the payment page loads it, at most 24 hours |
7. Your rights
Depending on where you live, you have the right to:
- access the personal data we hold about you and get a copy;
- correct data that is wrong or incomplete;
- delete your data, unless we must keep it, for example order records required by tax law;
- restrict how we use your data;
- receive your data in a portable format;
- object to processing based on our legitimate interests;
- complain to a data protection authority. In the EU, this is usually the authority in the country where you live. In the Republic of Moldova, it is the National Center for Personal Data Protection.
To use these rights, email hello@workflowexit.com. If your request is about a purchase, include your order number and write from the email address you used at checkout, so we can confirm it is you. We reply within one month.
We do not hold the content of your workflows after a conversion finishes, so we cannot return or delete it. There is nothing stored to delete.
8. Security
All traffic to the site uses HTTPS. Workflow definitions are processed in memory and not written to our database. Access to our hosting and database accounts is limited to the operator. No system is perfectly secure, but we keep the data we hold to the minimum the service needs.
9. Automated decisions
The traffic-light ratings and conversions are automated, but they assess workflows, not people. We make no decisions about you that have legal or similarly significant effects.
10. Children
Workflow Exit is a tool for developers and businesses. It is not intended for children under 16, and we do not knowingly collect their data.
11. Changes to this policy
If we change this policy, we will publish the new version on this page and update the date at the top. If a change is significant and we have your email address from a purchase, we will tell you by email.
12. Contact
Questions about this policy or your data: hello@workflowexit.com.
See also the Terms of Service and the Refund Policy.