Skip to content
Ladeworks
How it works Pricing Docs Contact
Log in Start free

Privacy policy

Effective date: October 13, 2026

This policy says what data Ladeworks collects, why, who sees it and what you can do about it. The short version: we collect what we need to run your workflows, we do not sell it, and we do not train AI models on it.

On this page

  1. Who we are
  2. Account data we collect
  3. Workspace data we process for you
  4. Messages you send us
  5. Logs and security data
  6. Cookies and similar storage
  7. How we use data
  8. Service providers (subprocessors)
  9. International transfers
  10. How long we keep data
  11. Security
  12. Your rights
  13. Children
  14. Changes to this policy
  15. Contact

Who we are

We are Ladeworks. This policy explains what personal data we handle when you use ladeworks.com and the Ladeworks app, and how we handle it.

We have two roles. For your account data we decide how data is used, so we are the controller. For the data that moves through your workspace, you decide what we do with it, so we act as your processor and handle it on your instructions.

Account data we collect

When you sign up and use Ladeworks, we collect:

  • your name and email address, and whether you have confirmed the address by clicking the link we email you
  • a hash of your password (we never store the password itself), or your Google account identifier and email if you sign in with Google
  • your time zone and theme setting
  • your two-factor authentication secret (stored encrypted) and recovery codes (stored as hashes), if you turn on two-factor authentication
  • your workspace memberships and roles
  • billing details: your billing email, plan, invoices and payment status. Card details are collected and held by Stripe. Ladeworks does not store card numbers.

Workspace data we process for you

To run your workflows we process the data you ask us to move. This can include:

  • integration settings and credentials, such as API keys, tokens and server passwords. These are encrypted at rest.
  • the records and files that move through your workflows, which may include personal data about your own customers, staff or partners
  • run history: what ran, when, the result, the requests and responses, and API call counts
  • payloads and output files from runs

We keep run history, responses, payloads and output files for the retention period of your plan (3 days on Free, 7 days on Starter, 14 days on Pro, 90 days or more on Business), then delete them.

We use workspace data only to provide Ladeworks to you. If it contains personal data about other people, you are responsible for having a lawful basis to use it and for telling those people as the law requires.

Messages you send us

If you write to us through the contact form on this website, we collect the name, email address and message you type. We use them only to answer you, and we keep the message so we can follow up. We do not send you marketing email because you wrote to us, and the form does not email a copy to the address you enter.

To limit spam, the form also uses your IP address in memory for a short time to count how many messages one address sends in an hour. We do not save that address with your message. To have a message deleted, email privacy@ladeworks.com.

Logs and security data

We keep server logs and security records, including IP addresses, sign-in attempts and sessions. We use them to protect accounts and investigate problems. Sign-in attempt records are cleared after a short time. Session records last as long as the session.

Error tracking is provided by Sentry (Functional Software, Inc.). Error reports are meant to hold technical details, not workspace data.

Cookies and similar storage

Ladeworks sets one cookie that lasts: a session cookie that keeps you signed in. It is needed for the service to work. It is HttpOnly, Secure and SameSite=Lax, and expires after 30 days without use. If you sign in with Google, we also set a cookie for a few minutes to finish the sign-in safely.

Your browser also stores your light or dark theme choice (in local storage) so the page looks right on load. It stays on your device.

Our pages load the IBM Plex fonts from Google Fonts, so your browser contacts Google to fetch them. When you add a card on the billing page, the app loads Stripe's payment form, which Stripe may use its own cookies or storage for. We do not use advertising cookies, analytics or tracking scripts of our own. For that reason there is no cookie banner. If that changes, we will update this page first.

How we use data

We use data to:

  • provide the service: run workflows, show run history, meter API calls, send alerts and keep accounts secure
  • bill you and handle payments and taxes
  • send service emails, such as invites, password resets, usage alerts and receipts
  • answer support requests, feedback and questions about plans
  • detect abuse, fix bugs and keep the service reliable
  • meet legal duties

Product news and tips by email are opt-in. The box at sign-up starts unticked, and you can turn it on or off at any time in Profile or Notifications. We also send one personal welcome email from the founder about a day after you sign up, and one getting started email if your workspace has not run anything after two days. Both have an unsubscribe link, and the link also turns product news off.

We do not sell your data. We do not use your workspace data, or the content of your records, to train AI models. We do not share personal data for advertising.

Service providers (subprocessors)

These providers help us run Ladeworks and may handle data on our behalf:

ProviderWhat forData involved
RenderHosting, database and background jobsAll data stored in Ladeworks
StripePayments and invoicesBilling email, plan, payment details held by Stripe
Sentry (Functional Software, Inc.)Error trackingTechnical error details
AnthropicReading public API documentation to help you set up integrationsPublic documentation pages only. No workspace data or customer records.
GoogleEmail delivery (Google Workspace), sign in with Google if you use it, and Google Fonts for page fontsRecipient email address and message content for email we send and receive. Your Google account identifier, name and email if you sign in with Google. Your IP address when your browser fetches the fonts.

If you connect Slack or Discord for alerts, alert text goes to the workspace you choose. Your own APIs and file servers receive the data you tell workflows to send them.

We will update this list before we add a provider that handles workspace data, and give notice of material changes.

International transfers

Ladeworks is hosted by Render in the United States. If you are outside the United States, your data is transferred there. Where the law requires it, we use approved transfer safeguards, such as standard contractual clauses, with our providers.

How long we keep data

  • Workspace run data (history, responses, payloads, output files): the retention period of your plan, then deleted.
  • Workspace data, including stored credentials and files: deleted from our database straight away when an Owner deletes the workspace. Copies in backups expire on the backup schedule.
  • Account data: while your account is open. You can delete your account yourself from Account settings after confirming: workspaces where you are the only member are deleted with it, and you are removed from the others. Email us for any other deletion request. Either way we delete your account data, except what we must keep by law.
  • Billing records: as long as tax and accounting law requires.
  • Logs and security records: a limited time needed for security and troubleshooting, up to 30 days.
  • Backups: they expire on the provider schedule and are not restored except to recover from a failure.

Security

We protect data with the measures described on the security page, including encryption of credentials at rest, encrypted connections, password hashing, and role based access. No system is perfectly secure. If a breach affects your data, we will tell you as the law requires.

Your rights

Depending on where you live, you may have the right to access your personal data, correct it, delete it, receive a copy in a portable format, object to or limit some uses, and withdraw consent. You can change much of your account data in the app, and you can delete your account from Account settings. For the rest, email privacy@ladeworks.com. We may ask you to confirm who you are.

If you are in the European Economic Area, the United Kingdom or Switzerland, you can also complain to your data protection authority. If you live in California or a similar state, you have the rights those laws give. We do not sell or share personal data as those laws define it, and we will not treat you worse for using your rights.

If your data is in a workspace owned by someone else, such as your employer, send your request to them first. We will help them respond.

Our legal basis for account data is mostly to perform our contract with you, our legitimate interest in running a secure service, and legal duties.

Children

Ladeworks is for businesses and is not meant for anyone under 16. We do not knowingly collect personal data from children. If you think a child has given us data, tell us at privacy@ladeworks.com and we will delete it.

Changes to this policy

We may update this policy. For material changes we will email account Owners or post a notice in the app before the change applies. The effective date at the top shows the latest version.

Contact

Privacy questions and requests: privacy@ladeworks.com.

Ladeworks
Pricing Docs Security Terms Privacy Contact © 2026 Ladeworks
Theme