Webflow Localization vs. a Translation Script: Which Fits?

By Updated 9 min read

You built your site in Webflow, it works and now customers in other countries are asking for it in their language. Translating a Webflow site comes down to two realistic paths: Webflow’s own Localization add-on or a third-party translation script that you paste into your site’s custom code. Both can get you live in a new language within days, but they differ a lot in what they translate, how search engines see the result and what you pay per language. This guide compares the two side by side so you can choose with real numbers instead of marketing copy.

Why translating your Webflow site is worth the effort

The business case is well documented. In a 2020 survey of 8,709 consumers in 29 countries, CSA Research found that 76% of online shoppers prefer to buy products with information in their own language and 40% will never buy from websites in other languages. The same study reports that 65% prefer content in their language even if the quality is poor. That last number is not an excuse for sloppy translation, but it does tell you that a decent translation today beats a perfect one next year.

If you are still unsure whether your site needs more languages at all, our post on why your website needs multiple languages walks through the signals to look for.

How native Webflow Localization works

Webflow Localization (Webflow now brands it “Localize”) is built into the Designer. You build your site in a primary locale and add secondary locales, where a locale is a language or a language plus country. According to the Webflow Localize overview, every secondary locale inherits content, styles and presentation from the primary locale until you override it. You can then localize text, assets, element visibility and styles per locale and reset any override to fall back to the original.

Translation itself can happen in three ways. You can let Webflow’s AI translate content, type translations yourself or connect a translation management system through a Webflow App or the API, as the guide on translating site content explains. You can try the features for free, but publishing a secondary locale requires a paid Localize add-on.

What Webflow Localization gets right for SEO

This is where the native option is strongest. Each locale lives in a subdirectory such as /es/ and Webflow sets the HTML lang attribute per locale. According to Webflow’s article on localized SEO and locale routing, it also adds page level hreflang tags and includes hreflang entries for static and dynamic pages in the auto generated sitemap. You can translate meta titles and descriptions per locale.

That matches what Google asks for. Google Search Central says it recommends using different URLs for each language version of a page and lists subdirectories as easy to set up with low maintenance. Its hreflang documentation adds that each language version must list itself and all other versions, which Webflow handles for you.

Where Webflow Localization hits limits

The biggest gap affects shops. The Localize overview states plainly that Localize does not support Ecommerce Site plan features, so products, categories and ecommerce pages cannot be localized when both are enabled. If you sell through Webflow Ecommerce, native Localization will leave your product catalog in one language.

Other limits depend on the plan. Localized URL slugs, asset localization and automatic visitor routing are only included in the Advanced and Enterprise tiers according to Webflow’s pricing page. AI translation also draws on a monthly word allowance. The AI translation usage article explains that allowances are pooled across your site and that once they run out, further translations are blocked until the monthly reset unless you opt in to Webflow AI credits or buy more locales. Translations reused from translation memory do not count against the allowance.

One more detail for anyone who cleans up old URLs: Webflow notes that 301 redirects are relative to your root domain and do not apply to localized subdirectories, so /old-url and /es/old-url need separate redirect rules.

What Webflow Localization costs

Prices change, so treat these numbers as a snapshot and check the Webflow pricing page before you decide. At the time of writing, Webflow lists two self serve Localize tiers that are priced per added locale (your primary language is not counted):

  • Essential: $9 per locale per month billed yearly or $12 billed monthly, up to 3 added locales, 10,000 AI translated words per locale per month.
  • Advanced: $29 per locale per month billed yearly or $35 billed monthly, up to 10 added locales, 50,000 AI translated words per locale per month, plus localized URLs, asset localization and automatic routing.
  • Enterprise: custom pricing and a custom number of locales.

The add-on comes on top of your Site plan. On the same page, the cheapest custom domain plan (Basic) is listed at $15 per month billed yearly. So a small marketing site that adds German, French and Spanish on Essential pays 3 × $9 = $27 per month for Localize on yearly billing, before the Site plan. Move to Advanced for localized slugs and the same three languages cost $87 per month billed yearly. The jump matters once you need a fourth language, because Essential caps out at three.

How a translation script works on Webflow

A translation script is a small piece of JavaScript from a third-party vendor. You paste one script tag into the site wide custom code and the script swaps text on each page into the visitor’s language. Webflow explicitly supports this: according to its help article on custom code in head and body tags, you can add site wide scripts if your site has an active Site plan or sits in certain paid Workspaces. Webflow recommends placing script tags before the closing body tag for load speed and notes that its support team cannot help with custom code.

The appeal is coverage and speed. A script sees the rendered page, so it can translate everything a visitor sees, including text inside components, CMS output and ecommerce pages that native Localize leaves alone. You do not need to touch the Designer for each new language and adding a fifth or tenth language is usually a setting rather than a new plan tier.

The SEO question you must ask a script vendor

Scripts differ widely in how search engines see the translated pages. Google processes JavaScript in crawl, render and index phases and can only index content present in the rendered HTML. The same page warns that not all bots can run JavaScript. Google also advises against showing different languages on the same URL, because Googlebot usually crawls without an Accept-Language header and might miss your variations.

So before you install any script, ask the vendor directly: does each language get its own URL (for example a subdirectory or subdomain) with hreflang tags? If the answer is no and translations only appear on the original URL, the script serves human visitors well but your translated pages will probably not rank on their own.

Quality control still matters

Machine translation is not a problem in itself, but publishing it at scale without review can be. Google’s spam policies list scaled content abuse, which includes automated transformations such as translating when they provide little value to users. Whichever path you choose, have someone who speaks the language check your most important pages. Our guide to post translation editing shows how to do that without rereading every sentence.

Webflow Localization vs. translation script compared

The table below sums up the main differences based on the sources above. Script details vary by vendor, so read that column as typical behavior to verify rather than a guarantee.

Factor Webflow Localization Translation script
Setup Inside the Designer, per locale One script tag in site wide custom code
Webflow Ecommerce products Not supported Usually translated on the rendered page
Separate URL per language Yes, subdirectories with hreflang Depends on the vendor, ask first
Localized slugs Advanced and Enterprise only Depends on the vendor
Pricing model Per added locale, plus a word allowance Varies (often by words, characters or page views)
Language cap 3 on Essential, 10 on Advanced Depends on the vendor
Designer control per locale Styles, assets and visibility per locale Usually text only

The pattern is clear. Native Localization wins when you run a content site or a marketing site in a few languages and want Webflow to handle URLs and hreflang for you. A script wins when you sell through Webflow Ecommerce, want many languages without per locale fees or need translation on more than one platform.

Which option should you pick?

Choose native Webflow Localization if your site has no Webflow Ecommerce, you need three to ten languages and organic search in each market is a priority. You get subdirectories, hreflang and a sitemap without writing code and you can adjust layouts where German headlines run longer than English ones.

Choose a translation script if you run Webflow Ecommerce, want to cover many languages on a fixed budget or manage several sites on different platforms. Agencies and freelancers often like that the same approach works on Webflow, WordPress, Shopify and plain HTML. Just make the URL question part of your vendor checklist.

heylingo is one example of the script approach: one script tag, AI translation with translation memory, inline corrections directly on your live site and more than 30 languages for EUR 20 per 1,000,000 translated characters per month. Whatever vendor you test, compare pricing on your actual content volume, because per word and per character plans are not directly comparable.

A hybrid is also possible. Some teams use Localize for their core marketing pages and a script for areas Localize cannot reach. If you go that way, avoid translating the same page twice and keep one clear owner for each language. Our list of common website translation mistakes covers more traps like this.

FAQ

Is Webflow Localization free?

You can try Localize features for free on any plan, but publishing a secondary locale requires a paid add-on. At the time of writing, the Essential tier starts at $9 per locale per month billed yearly according to Webflow’s pricing page.

Can I translate Webflow Ecommerce products with Localization?

No. Webflow’s own documentation says products, categories and ecommerce pages cannot be localized when Localize and Ecommerce are both enabled. A translation script that works on the rendered page is one way around this.

Does a translation script hurt my Webflow SEO?

Not by itself, but it may not help either. If translations only appear on the original URL, search engines will mostly see your primary language. Ask the vendor whether each language gets its own URL with hreflang tags, since Google recommends separate URLs per language.

How many languages can I add with Webflow Localization?

Up to 3 added locales on Essential and up to 10 on Advanced. Enterprise offers a custom number of locales.

Conclusion

Translating a Webflow site is no longer a big project, but the right tool depends on what you sell and how many languages you need. Native Webflow Localization gives you clean SEO structure and design control for a handful of languages, at a per locale price and without ecommerce support. A translation script gives you broader coverage and simpler scaling, provided you confirm how it handles URLs. Start with the one or two markets where you already see demand, check the result with a native speaker and expand from there.

Want to see what one script tag can do for your site? Check heylingo pricing.

Sources

JE

Written by

Jermaine builds and runs heylingo single-handedly from Germany and answers every support email personally.

More from the blog

Information pursuant to § 5 DDG (German Digital Services Act).

Jermaine J. Ernst
c/o Block Services
Stuttgarter Str. 106
70736 Fellbach
Germany

Email: info@heylingo.io
VAT ID: DE370296865

Responsible for content pursuant to § 18 (2) MStV: Jermaine J. Ernst, address as above.

Consumer dispute resolution

We are neither willing nor obliged to take part in dispute resolution proceedings before a consumer arbitration board.

Liability for content

As a service provider we are responsible for our own content on these pages under general law, pursuant to § 7 (1) DDG. Under §§ 8 to 10 DDG we are not obliged to monitor third-party information that is transmitted or stored, or to investigate circumstances that indicate illegal activity. Obligations to remove or block the use of information under general law remain unaffected. Liability in this respect is only possible from the moment we become aware of a specific infringement. As soon as we learn of such an infringement, we will remove the content immediately.

This website links to external websites of third parties whose content we cannot influence, so we cannot accept any liability for that content. The respective provider or operator of a linked page is always responsible for its content. The linked pages were checked for possible legal violations when the link was set, and no illegal content was apparent at that time. Permanent monitoring of linked pages is not reasonable without concrete indications of an infringement. If we become aware of an infringement, we will remove the link immediately.

The content and works created by the site operator on these pages are subject to German copyright law. Reproduction, editing, distribution and any kind of use beyond the limits of copyright law require the written consent of the respective author or creator. Where content on this site was not created by the operator, the copyrights of third parties are respected and such content is marked as such. If you nevertheless become aware of a copyright infringement, please let us know. As soon as we learn of an infringement, we will remove the content immediately.

Last updated 10 October 2026

Privacy policy

This privacy policy explains which personal data we process when you visit heylingo.io, contact us or buy heylingo. It also explains how data is handled when one of our customers uses the heylingo translation service on their own website.

Controller

The controller within the meaning of the EU General Data Protection Regulation (GDPR) is:

Jermaine J. Ernst
c/o Block Services
Stuttgarter Str. 106
70736 Fellbach
Germany

Email: info@heylingo.io

Please use this address for any question about data protection and to exercise your rights.

Overview

heylingo.io is a static website. When you browse it:

Personal data is processed only in the cases described below: delivery of the website by our host, images in blog posts, YouTube videos you choose to play, contact by email and the purchase of heylingo through Stripe. A separate section covers the heylingo translation service.

Hosting and server logs

heylingo.io is hosted by Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. Each time you open a page, Cloudflare processes the following server log data:

Cloudflare uses this data to deliver the website to you and to protect it from attacks and misuse. We do not use it to identify you or to create user profiles.

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is the secure and reliable delivery of our website.

Cloudflare may process data outside the European Union, including in the USA. Cloudflare, Inc. is certified under the EU-U.S. Data Privacy Framework, so transfers to it are based on the adequacy decision of the European Commission (Art. 45 GDPR). Where the Data Privacy Framework does not apply, transfers are based on the EU standard contractual clauses (Art. 46(2)(c) GDPR).

More information: Cloudflare privacy policy.

Blog images and videos

Images

Images in our blog posts are loaded from assets.seobotai.com, an external image host. When you open a blog post, your browser requests these images directly from that host. The host thereby receives your IP address and the technical information that is part of every request, such as the requested file, the address of our website and your browser’s user agent.

The host needs your IP address to deliver the images. We have no influence on how the host processes this data.

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is showing images in our blog posts.

YouTube videos

Some blog posts contain YouTube videos. They are not loaded when you open the page. No data is sent to YouTube until you click “play”. Only then is the video loaded from youtube-nocookie.com.

YouTube is operated by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Once the video is loaded, Google receives at least your IP address and the address of the page. Google may also store information on your device or read it from your device, for example cookies, and may process data about how you use the video. Google may process data in the USA; Google LLC is certified under the EU-U.S. Data Privacy Framework.

The legal basis is your consent, which you give by clicking “play” (Art. 6(1)(a) GDPR and, for storing and reading information on your device, § 25(1) of the German Telecommunications and Digital Services Data Protection Act, TDDDG).

Your consent applies only to the video you start. You can withdraw it at any time with effect for the future: do not start any further videos and close or reload the page. You can delete cookies set by Google in your browser settings.

More information: Google privacy policy.

Contact by email

If you email us, we process your email address, your message and any other information you provide, such as your name or company. We use this data only to answer your request.

If your request relates to a contract with us or to concluding one, the legal basis is Art. 6(1)(b) GDPR. Otherwise the legal basis is Art. 6(1)(f) GDPR; our legitimate interest is answering requests sent to us.

We delete the data once your request has been fully dealt with, unless statutory retention obligations apply (see “Retention”).

Purchasing heylingo via Stripe

You sign up for heylingo through Stripe Checkout, which you reach via a payment link on heylingo.io. Invoices, your payment method and cancellation are managed in the Stripe Customer Portal. There is no user account on heylingo.io.

The payment provider is Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland. Stripe processes the data you enter during checkout and in the customer portal. This includes your name, email address, billing address, company name and VAT ID if you provide them, your payment details, and transaction and invoice data.

You enter your payment details directly with Stripe. We do not receive your full card or account details.

We receive from Stripe the data we need to manage your subscription and bill your usage, such as your name, email address, billing details and payment status. To bill you, we report your usage (the number of translated characters) to Stripe.

The legal basis is Art. 6(1)(b) GDPR, because the processing is necessary to conclude and perform the contract. We keep invoices and accounting records to meet our retention obligations under German commercial and tax law. The legal basis for this is Art. 6(1)(c) GDPR.

Stripe also processes some data under its own responsibility, for example to prevent fraud and to meet its legal obligations as a payment provider. Stripe may transfer data to Stripe, Inc. in the USA, which is certified under the EU-U.S. Data Privacy Framework.

More information: Stripe privacy policy.

The heylingo translation service

This section is for our customers and for visitors to websites that use heylingo.

Our role

heylingo makes a customer’s website multilingual. When a customer uses heylingo, we process the content of the customer’s website on the customer’s behalf. For any personal data of visitors to that website, the customer is the controller and we act as a processor (Art. 28 GDPR).

If you visit a website that uses heylingo, please read that website’s privacy policy and send requests about your data to its operator.

Customers can request a data processing agreement under Art. 28 GDPR at info@heylingo.io.

In the visitor’s browser

The customer adds the heylingo script to their website. The script shows a language switcher and picks the visitor’s preferred language. It stores the chosen language in the visitor’s browser (localStorage) so the website appears in that language on later visits. The script sets no cookies.

The entry stays in the browser until the visitor deletes it. Storing it is limited to what is strictly necessary for the language function the visitor uses (§ 25(2) no. 2 TDDDG).

Translation

To translate a page, the script sends the page’s text to our translation service. Because the visitor’s browser connects to the service, the service also receives the visitor’s IP address and the technical information that is part of every request.

Page text usually contains no personal data. If a page does contain personal data, for example names on a team page or text shown only to a logged-in user, this text is sent to us as well. The customer decides on which pages the script runs.

Text that is translated for the first time is translated by AI. For this we use a large language model of Anthropic PBC, USA, through its API, as a sub-processor. Transfers to Anthropic are based on the EU standard contractual clauses (Art. 46(2)(c) GDPR).

Each translation is stored in a translation memory for that website. Later visitors receive the stored translation, so the same text is not sent to the AI provider again.

The translation service and the translation memories run on servers of netcup GmbH in Germany.

Inline editing

Customers can correct translations directly on their live website. This edit mode can only be used by the site owner. Corrected sentences are stored in the translation memory and are never re-translated.

Deletion

When a customer cancels, the script stops translating and the website shows its original language. The website’s translation memory, including manual corrections, is deleted 30 days after the cancellation takes effect.

Retention

We keep personal data only as long as it is needed for the purpose it was collected for, unless a statutory retention obligation applies. While such an obligation applies, we use the data only for that purpose.

Your rights

You have the following rights regarding your personal data:

To exercise your rights, email info@heylingo.io. If your request concerns a website that uses heylingo, please contact the operator of that website first, as it is the controller. We support our customers in answering such requests.

Right to object

Where we process your data on the basis of Art. 6(1)(f) GDPR, you can object to the processing at any time on grounds relating to your particular situation (Art. 21 GDPR). We will then stop processing your data, unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves to establish, exercise or defend legal claims.

Right to lodge a complaint

You can lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the EU member state of your habitual residence, your place of work or the place of the alleged infringement. The authority responsible for us is Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg (the State Commissioner for Data Protection and Freedom of Information of Baden-Württemberg).

No automated decision-making

We do not use automated decision-making, including profiling, within the meaning of Art. 22 GDPR. The AI used by heylingo translates text; it does not make decisions about people.

Changes to this policy

We update this policy when our services or the legal requirements change. The current version is always available on heylingo.io. The date of the last update is shown at the end of this policy.

Last updated 10 October 2026

Terms of service

These terms of service govern the use of heylingo, a service that makes websites multilingual. heylingo is offered to businesses only.

1. Scope and parties

These terms apply to all contracts for the use of heylingo between Jermaine J. Ernst, c/o Block Services, Stuttgarter Str. 106, 70736 Fellbach, Germany, email info@heylingo.io (“we”, “us”) and our customers (“you”).

heylingo is offered exclusively to entrepreneurs (Unternehmer) within the meaning of § 14 BGB. These are natural or legal persons or partnerships with legal capacity who conclude the contract in the exercise of their commercial or independent professional activity. Consumers are not our target group. By concluding a contract, you confirm that you are acting as an entrepreneur.

Your own terms and conditions do not apply, even if we do not expressly object to them, unless we have agreed to them in text form.

2. The service

heylingo makes your website multilingual. You add one script tag to your website. The script shows a language switcher, selects the visitor’s preferred language, stores the chosen language in the visitor’s browser, sends the page’s text to our translation service and replaces it with the translation.

Text that has not been translated before is translated by AI (a large language model) and stored in a translation memory for your website. Later page views receive the stored translation.

All languages supported by heylingo are included. The currently supported languages are listed on heylingo.io.

You can correct translations directly on your live website, in an edit mode that only you as the site owner can use. Sentences you have edited manually are never re-translated.

There is no user account or dashboard on heylingo.io. Invoices, your payment method and cancellation are managed in the Stripe Customer Portal.

For the term of the contract, you receive a non-exclusive, non-transferable right to use the heylingo script on your website. All other rights to heylingo remain with us.

We may use subcontractors to provide the service, in particular for hosting and AI translation. We may develop heylingo further and change its features, provided the core function described in this section is preserved and the change is reasonable for you.

3. Conclusion of the contract

The description of heylingo on heylingo.io is not a binding offer.

You sign up through Stripe Checkout, which you reach via the payment link on heylingo.io. By completing the checkout, you make a binding offer to conclude the contract. We accept it by activating your subscription, which normally happens immediately after checkout.

The contract language is English. These terms can be viewed, saved and printed on heylingo.io at any time.

4. Prices and billing

heylingo has one pricing model: pay per use. The price is a monthly price per one million translated characters, as listed on heylingo.io (currently EUR 20 per 1,000,000 characters per month). It includes all supported languages.

The characters counted for a month are the characters of the translated text that heylingo keeps for your website in its translation memory, across all target languages. Page views and the number of visitors do not affect the price.

Billing runs through Stripe as a metered subscription. Your usage is billed monthly in arrears and charged to the payment method you stored with Stripe. Invoices are available in the Stripe Customer Portal.

All prices are net prices. VAT is added where applicable.

We announce price increases by email at least 30 days before they take effect. A new price applies from the first billing month after it takes effect. As you can cancel at any time, you can avoid a price increase by cancelling before it takes effect.

If a payment fails, we may suspend the service after notifying you until the outstanding amount has been paid. During a suspension, your website shows its original language.

5. Your obligations

You must hold all rights needed to have the content of your website translated, stored and displayed, including in translated form.

You grant us a non-exclusive right to process, translate, store and deliver your content and its translations, to the extent necessary to provide heylingo. This includes the right to have our subcontractors do so. The right is limited to the term of the contract and the deletion period in section 8.

You must not use heylingo for unlawful content, in particular content that infringes the rights of third parties or violates criminal law.

You are responsible for integrating the script correctly, as described by us, and only on websites that you operate or are authorised to operate.

You must not misuse heylingo. In particular, you must not:

If a third party asserts claims against us because of content on your website or because you breached these terms, you indemnify us against these claims, including the reasonable costs of legal defence. This does not apply if you are not responsible for the breach.

6. AI translations

Translations are produced automatically by AI. We do not review them before they are shown on your website.

Machine translations may contain errors, omissions or wording that does not fit the context. We provide machine translation, not a reviewed or certified translation.

You should review translations, especially where errors can have legal or financial consequences, such as legal texts, prices, product information and safety notices. You can correct any translation in the edit mode on your website.

You are responsible for all content published on your website, including its translations.

7. Availability

We aim to keep heylingo available and working, but we do not guarantee a specific availability or uptime. Interruptions can occur, for example due to maintenance, updates or disruptions at our subcontractors.

If heylingo is unavailable, your website shows its original language. As you pay only for translated characters, no charges arise for text that is not translated.

8. Term and cancellation

The contract starts when it is concluded and runs for an indefinite period.

You can cancel at any time in the Stripe Customer Portal or by email to info@heylingo.io. Usage up to the effective date of cancellation is billed.

We can cancel the contract with 30 days’ notice by email.

The right of both parties to terminate for good cause without notice remains unaffected. Good cause for us exists in particular if you are in default of payment despite a reminder, use heylingo for unlawful content or seriously breach your obligations under section 5. In these cases, we may instead suspend the service for your website.

After the contract ends, the script stops translating and your website shows its original language. We delete your website’s translation memory, including manual corrections, 30 days after the contract ends. We recommend removing the script tag from your website.

9. Data protection

We process personal data in accordance with the GDPR and our privacy policy.

When you use heylingo, we process the content of your website on your behalf. For any personal data of visitors to your website, you are the controller and we act as your processor. A data processing agreement under Art. 28 GDPR is available on request at info@heylingo.io.

You are responsible for meeting your own data protection obligations towards the visitors of your website, in particular for informing them about the use of heylingo in your privacy policy.

10. Liability

We are liable without limitation for intent and gross negligence, for injury to life, body or health, where we have given a guarantee, and under the German Product Liability Act (Produkthaftungsgesetz).

For slight negligence, we are liable only for breach of an essential contractual obligation. This is an obligation whose fulfilment makes the proper performance of the contract possible in the first place and on whose fulfilment you may regularly rely. In that case, our liability is limited to the damage that is typical for this type of contract and foreseeable when the contract was concluded.

Otherwise, liability for slight negligence is excluded. Strict liability for defects that already existed when the contract was concluded (§ 536a(1) BGB) is also excluded.

These limitations also apply in favour of our vicarious agents and subcontractors.

11. Changes to these terms

We may change these terms for a valid reason, in particular because of changes in the law or case law, or changes to heylingo. We will notify you of changes by email at least 30 days before they take effect.

You can object to the changes within this period. If you do not object, the changed terms are deemed accepted. We will point this out specifically in our notice. If you object, the contract continues on the previous terms, and we may cancel it in accordance with section 8.

This procedure does not apply to changes to the main obligations of either party. Price changes are governed by section 4, changes to the service by section 2.

12. Final provisions

German law applies, excluding the UN Convention on Contracts for the International Sale of Goods (CISG).

If you are a merchant (Kaufmann), a legal entity under public law or a special fund under public law, or if you have no general place of jurisdiction in Germany, the exclusive place of jurisdiction for all disputes arising from this contract is the competent court for Fellbach, Germany. We may also bring an action at your general place of jurisdiction.

If any provision of these terms is or becomes invalid, the remaining provisions remain valid. The invalid provision is replaced by the statutory provisions.

Last updated 10 October 2026