No compliance badges — just an accurate account of what happens to your data.
We're a small team without ISO 27001, SOC 2, or HIPAA certifications, and we won't claim ones we don't have. Here's exactly what happens to your workflow data at each step of using this tool.
Basic conversion stays in your browser
Converting between n8n, Logic Apps, Power Automate, and Make JSON happens entirely client-side. What you paste is parsed and converted in your browser tab — it's never sent to our servers, logged, or stored, unless you explicitly run a paid Pro conversion.
We never carry over credentials
When a step references a connection or credential, the converter doesn't extract, invent, or write a secret value into the output — ever. It's replaced with a clearly labelled placeholder and flagged in the manual-review report so you reconnect it yourself on the target platform. This only covers recognized credential references, though — if you hardcode a real secret directly into a field (an API key in a URL, say), that value is just part of the file, so please don't.
Pro conversions are opt-in and scoped
Only when you pay for and run a Pro conversion does any workflow data leave your browser. We send the specific step(s) our rule-based engine couldn't map — and the overall shape of your workflow — to Anthropic's Claude to suggest a fix, not a copy of your whole file. Claude may use web search to confirm a real connector or API exists, so its search terms can reflect step content.
What we actually store
If you're signed in and run a Pro conversion, we save the result — the converted output, the review report, and any AI suggestions — to your account, so you can find it again on your dashboard. That's the only workflow content we keep. It's protected by row-level database security scoped to your account, and you can ask us to delete it at any time.
Payments never touch our servers
Checkout happens on Stripe's own hosted page. We never see or store your card details — only a Stripe customer ID and a ledger of the credits you've bought and spent.
Sign-in is handled by Supabase
Accounts use Supabase Auth — email and password, Google sign-in, or a one-time emailed code. Your password is never stored by, or visible to, our own code; Supabase manages it directly.
No analytics, no trackers
No third-party analytics scripts, ad pixels, or session-recording tools run on this site.