Privacy Policy

When you sign up we store your name, email address and, for email sign-up, a bcrypt hash of your password. With Google sign-in we store the name, email, profile image and Google account ID Google returns.

Verification and password-reset emails, and the emails of Send Email nodes, are sent through Resend, which receives the recipient address and the message. While a verification or reset link is valid we store a hash of it and its expiry with your account; the link itself is not stored.

Profile fields you choose to fill in (phone, company, job title, profile image) are stored with your account, together with a username generated from your name. Profile images are uploaded to the image host configured for this deployment.

To enforce plan limits we store the number of workflow runs your account started in the current month.

Workflows you build, including node settings such as URLs and headers, are stored in the database and are visible only to you and to administrators of this deployment.

When you run a workflow or test a node, HTTP request, Slack and Discord nodes send the data you configured to the addresses you entered. Send Email nodes send the subject and message you configured to your own account's email address.

Records written by Database Update nodes are stored in the database until a workflow deletes them. Each run is stored with every step's output, including data received by a webhook, and deleted after 30 days.

When a workflow's webhook URL is called, the run stores the request it received: method, query parameters, body and headers. The Authorization, Cookie and Proxy-Authorization headers are dropped; every other header is kept, including User-Agent and the X-Forwarded-For and X-Real-IP headers that carry the caller's IP address. The workflow's owner can read them in the run history, and they are deleted with the run after 30 days.

Paid plans are processed by Stripe. Card details are entered on Stripe's pages and are not stored by this app. When you first start a checkout, Stripe receives your name, email address and account ID to create your customer record. We store your Stripe customer ID, subscription ID, plan and subscription dates. If you give a cancellation reason when cancelling, it is stored with your account and sent to Stripe with the cancellation.

Messages sent through the contact form are stored in the database with the sender's IP address and browser user agent, and are visible to administrators. Email addresses entered in the newsletter form are stored with the sign-up date, and the address receives one email with a confirmation link that works for 7 days. An address becomes a subscriber, visible to administrators, only when that link is opened and its Confirm button pressed; an address that is not confirmed is deleted when its link expires. A confirmed address is kept with its confirmation date and deleted 30 days after confirmation, or earlier through the unsubscribe link in every newsletter email. No IP address or user agent is kept with these addresses. The software sends no other email to them.

To slow down abuse, sign-in, sign-up, email requests, the contact and newsletter forms, the newsletter confirm and unsubscribe buttons, uploads, checkout, workflow runs and webhook calls are rate limited. Each limit keeps a short-lived counter keyed by your IP address, the email address entered at sign-in, at reset or in the newsletter form, your account ID or the webhook URL. When the deployment uses Upstash Redis, the counters are stored there under a hash of the IP address, email address or ID, never the value itself; otherwise they are kept in the server's memory. A counter expires at the end of its window, which is at most 24 hours.

The typefaces (Inter, Geist and Geist Mono) are served by this site, so loading a page contacts no font service.

Stripe's checkout and billing pages and Google's sign-in page are served by those companies when you use them, and profile images are loaded from the image host or, for a Google profile image, from Google.

You can edit your profile at any time. To have your account deleted, send a request through the contact form. An administrator then deletes the account together with its workflows, run history, stored records and every profile image it uploaded to the image host.