IA 360
Current Affairs

Elementor AI: what is actually underneath

Elementor AI's terms state the company “solely serves as a platform” to third-party services — OpenAI, Stability AI, Azure, Anthropic — that are “not vetted, endorsed, or controlled by Elementor.” That sentence describes what you buy when a program you already used adds an AI button: not a model of its own, but a conduit to someone else's. What happens to what you type, who answers for the output, and the three questions that work for any embedded AI.

Admin IA360 2 min read AI-generated Leer en español
Elementor AI: what is actually underneath

The Elementor AI terms and conditions, last updated in December 2023, contain a sentence that appears in no advertisement for the product: "Elementor solely serves as a platform to such services offered by the Technology Partners, and such services are not vetted, endorsed, or controlled by Elementor."

Read it twice, because it describes with surgical precision what you are buying when a program you already used adds a button marked "AI." There is no Elementor model. There is a conduit to somebody else's model, and the company charging you states in writing that it does not control it.

Scale is what stops this being a curiosity. The official WordPress plugin registry credits Elementor with "10+ million" active installations. When a generation feature appears inside an installed base that size, the small print stops being a matter between a company and its lawyers and starts describing the daily practice of an enormous number of people who will never read it.

Who is actually underneath the button

The terms name the providers themselves: "OpenAI, LLC, Stability AI Ltd., Azure, Anthropic, etc." That list — including its "etc.," which also means something — answers the question almost nobody asks when trying an embedded AI feature: whose model is this?

The product's help documentation sets out what can be generated from inside the editor: text, page and post excerpts, images, a logo, custom code, custom CSS, containers, and even "an entire website from scratch." It is a broad catalogue, and it explains the appeal: generation happens where you are already working, with no tab-switching and no copy-pasting between tools.

That convenience is real and it has value. But it is worth knowing that what you pay for is not the intelligence: it is the integration. The model is rented from a third party; what the user buys is that somebody else did the plumbing.

What happens to what you type

The same document says it plainly: any text you type in, or images and other content you upload to the AI Products — what the terms call the "Input" — "will be shared with the Technology Partners," and those partners "may use such Input to train and improve their services."

This is neither a scandalous clause nor unique to Elementor: it is standard for integration layers. But it has practical consequences worth deciding coolly rather than mid-project. If the text pasted into the editor includes a client's sales positioning, the terms of a contract, or data that is not yours, that material leaves your machine and enters the infrastructure of a third party you never contracted with and never read.

Who answers for the result

Here are the two sentences that should weigh most in any professional workflow. The first: "Elementor makes no warranty or guarantee as to the accuracy, completeness, or reliability of the Output." The second, less quoted and more awkward: "We cannot guarantee that the Outputs will be unique or will not be similar to Outputs of other users."

That second sentence matters especially to anyone generating images or copy for a client. The tool does not promise originality. And the terms are equally clear about where responsibility lands: "You are responsible for any Input, as well as the resulting material you generate, such as images, code, or text."

The division of labour, summarised: the provider supplies the model, Elementor supplies the pipe and states that it does not control what runs through it, and the user supplies the signature. It is a perfectly legitimate arrangement — and, again, a near-universal one — but you only learn it by reading a document almost nobody opens.

The credit as the unit

The last piece of the puzzle is economic. The product documentation describes a shared credit system spread across all the tools included in the subscription, rather than unlimited access. That turns generation into a metered resource: every action draws down a common balance.

The practical consequence is that the real cost of an embedded AI feature is not on the software's price tag but in how much balance your actual work consumes. It is the difference between the price of a car and what it burns over the miles you personally drive.

The toll on convenience

It is worth seeing the trade clearly, because it is the same one in dozens of products and it has no single right answer. Going direct to the model provider is usually cheaper per unit and gives you the newest version the day it ships, but it means building the plumbing yourself and leaving your working environment. Using the built-in feature spares you all of that in exchange for three things: a margin on the price, an intermediary deciding which version of the model you get and when, and one more dependency.

That second concession is the least obvious and the most consequential. Whoever does the integrating picks the model, the configuration and the moment to switch it; the user sees the effects — results that get better or worse from one month to the next — without the explanation being anywhere to hand. When somebody says "this tool's AI has got worse," they are often describing, without knowing it, a procurement decision taken somewhere else.

None of this is an argument against built-in features. It is the price of a real service, and for many people it is comfortably worth paying. But it is a price worth seeing.

The capability: three questions for any embedded "AI"

This is the usable part, and it will still be usable once this particular product has changed its name three times. Whenever a program you already pay for announces that it now "has AI," find its terms document — there always is one, and it is nearly always linked in small print — and answer three things:

One: whose model is it, and who answers for it? If the company billing you states that it neither vets nor controls the underlying service, you have two suppliers and only one contract. Know which is which.

Two: where does what I type go, and is it used for training? This is the question that decides what material may be pasted in there and what may not. It is a decision best made in writing, especially where clients are involved.

Three: what is the unit of consumption, and what happens when it runs out? Credits, prompts, tokens or messages: the name is irrelevant. What matters is whether the work you routinely do fits inside the quota, and what happens on the day it does not.

Where to go next, with no middlemen

Everything cited here is public and free. The Elementor AI terms and conditions are the decisive document and the only one that answers all three questions above. The help section lists what can be generated and how. And for contrast, it is worth then opening the terms of whichever provider sits underneath in each case.

None of this makes Elementor AI a bad product: integrating generation properly into the place where you already work is a legitimate service that plenty of people happily pay for. The capability you take away is telling the integration apart from the model — and knowing that when a product adds "AI," the former is usually what you are buying.

This article was produced with artificial intelligence under human editorial oversight.

Share this article

This website uses cookies to improve the browsing experience. Cookie policy.

↑↓ navigate ↵ open esc close