Website legal documents

Any site that takes orders or collects contact details needs legal pages: a privacy policy, terms of service, return and delivery terms, a cookie policy. You do not have to write them from scratch or pay for a separate generator — the constructor assembles them from your answers and publishes them.

Where: Marketing → “My Website” → the “Legal documents” card (for an external site), and when publishing as storefront pages — Marketing → “Websites” → “Articles & pages” → “Legal documents”. The widget window also opens by direct link — ?widget=legal on the “My Website” page, and the install-code window is ?panel=install.

What you configure#

For an external site there is no step-by-step wizard: every option sits on a single widget panel — country, documents, questions, company details, language, the collapsed autofill and preview blocks, the validation findings and the “Publish N documents” button. You edit everything in place, in any order.

When publishing as storefront pages, the same set is split into five sequential steps: country → documents → parameters → company details → preview and publish. The content is identical; the blocks are described below.

1. Country. Pick the legal system: Georgia, Russia, the European Union, the United States, Türkiye, Albania or the international set. It determines both wording and mandatory sections (data subject rights under the GDPR, or how return shipping costs may be allocated, for example).

2. Documents. Which of the five to generate. All of them by default.

3. Business parameters. Checkboxes that decide which clauses are included:

Questions that do not apply to the chosen country and document set are simply not shown. And answers that contradict the ones already chosen are shown locked, with an explanation of why they cannot be enabled — they do not vanish silently, and they do not lead to a “⛔ cannot publish” after the click. Country-level prohibitions behave the same way: you see both what is forbidden and what would unlock it.

Alongside is a list of named services: payment, analytics, email and advertising. Named services appear in the documents, the way Termly and iubenda do it. Leave a field empty and its clause is skipped.

4. Company details. Legal name, registration number, address, contact email and phone, voluntary return window (14 days by default). Fields are prefilled from your location profile.

You do not have to fill them in by hand — there are two autofill options:

• From your website. We read your external site and suggest company details and answers: each suggestion shows a confidence level and its source — the page and the quote it came from. Nothing is overwritten silently: applying a value is always an explicit click, and only empty fields are filled automatically.
• From your code (GitHub). If your site or app has a repository, you can grant access to 1–5 repositories (public ones need no token; private ones use a read-only contents token that the server never hands back). We read manifests, config examples and sources and suggest answers backed by the same evidence — for example, which analytics and payment services you actually use.

5. Preview and publish. Every document is shown in full before publishing, and you can see which pages will be created and which updated.

Where the documents are published#

Two modes:

• As pages of your storefront. Each document becomes a regular site page with a stable address (privacy-policy, terms-of-service, return-policy, cookies-policy, delivery-terms) and a footer link. Publishing again updates the existing page instead of creating copies.
• On our hosting (for an external site). Pages are placed on our CDN in every language of your site, with correct canonical and hreflang, a language switcher and navigation between neighbouring documents.

If you would rather host the documents yourself, the preview step offers copy HTML and export to HTML or Markdown.

Your own link or your own text instead of the constructor#

The constructor is optional. If you already have terms of sale, a privacy policy or a returns policy — on your chain's website, in Google Docs, in a PDF from your lawyer — point to them directly. Articles and pages → “📄 Site documents”: for each document (terms of sale, privacy policy, returns, delivery, cookies) choose how it is provided:

• Not set — the storefront footer keeps the platform text, and the checkout line does not mention this document;
• Site page — a document built by the constructor or carried over by the store import, or any page you have published;
• Own link — the address of the document anywhere on the web; guests open it in a new tab. Only http(s) links are accepted; a domain without https:// is completed automatically;
• Own text — the text right in the setting, up to 4,000 characters, without formatting (line breaks are kept). Guests read it in a window over the page. Anything longer — publish it as a page.

The choice is made per location: each location (each site) has its own documents. The storefront footer, the order page, the cookie banner and document links from widgets lead where you pointed. If you switch a document from a page to your own link, the old page is not deleted and disappears from the footer — you can switch back without publishing again. A new constructor publication returns the published documents to the “Site page” mode.

The consent line in checkout and bookings#

When a location has its terms of sale and/or privacy policy set (in any mode), the storefront shows a line next to the place-order button:

“Terms of sale” and “privacy policy” link to your documents: a page opens in a new tab, your own link too, your own text in a window — the filled-in order form is not lost. For a location in Russia the wording names the public offer and the personal data processing policy. Bookings with a prepayment (a table deposit or a service booking deposit) show the same line above the pay button: “By booking with a prepayment, you accept…”.

If only one of the two documents is set, the line names only that one. If neither is set, there is no line: the platform texts in the footer are the terms of the service, not your venue's terms of sale, and must not be presented as yours.

Why “have read” rather than “agree to the processing of data”: placing an order accepts your terms, while the policy is published for information. Consent to personal data processing is a separate action (in Russia, Federal Law 152-FZ requires it to be given separately from other documents); such checkboxes live in the booking form and in mailing settings. This is not a legal guarantee: have a lawyer review the wording and the content of your documents.

The widget for an external site#

Once published on our hosting, the documents appear on your site with a single line of code (see My Website). Three options:

• Links — a block of links to all documents, usually in the footer;
• Modal — the document opens on top of the page, so the visitor stays on your site;
• Inline text — the document body is embedded into your own layout (on a /privacy page, for instance).

Republish a document in the dashboard and your site updates itself; there is no markup to edit.

Relation to the cookie policy#

The cookie banner and the documents are different tools with different “countries”: the banner has per-country modes (how it behaves before the visitor decides), while the builder has a legal set of wording. The cookie policy is the one document with live content: its cookie table is assembled from the results of scanning your site and updates together with the declaration. It is the same document the consent banner links to — see Cookies & Consent.

Which legal sets exist — and what is not in them#

A set is a library of wording the builder assembles your documents from. There are ten of them, and you choose which one to use (the hint based on your venue's country is only a hint). None of the sets is "certified", and none of them determines which law you fall under.

⚖️ Disclaimer. Below is what our templates rely on — not a statement that a given rule applies to your business. The documents are generated as templates and are not legal advice (the same disclaimer is the final block of every document). The primary sources are listed so that you and your lawyer have something to check against.

What is not there, honestly:

• country sets for most of the world. Didn't find yours — take the international one: it is written to work both where the rules are strict and where they are loose, but by definition it knows nothing about national specifics (a mandatory Impressum, the language of the documents, industry requirements);
• Ukraine, Armenia, Azerbaijan — we studied those jurisdictions but have not built a separate set yet: the international one is available;
• automatic choice of jurisdiction. We do not decide which law you fall under: you pick the country yourself, and the "who do you serve" question only adds sections for buyers from that region;
• tracking legal changes for you. When a rule changes, the documents do not rewrite themselves: update the answers and publish again;
• verification of your facts. Company details, return windows and the list of services come from your answers; we do not check them against any registry.

And separately: the language of a document and the jurisdiction are different things. Documents are published in every language of your site, but the legal set stays the one you chose.

Limitations#

• The documents are templates, not legal advice. A disclaimer saying so is shown in the dashboard and in the document export (marked “remove before publishing”); in the published document a visitor sees only the revision date. Have the result reviewed by a lawyer before publishing, especially if your sales model is unusual, you process sensitive data, or you operate across several jurisdictions.
• The widget for an external site is a paid add-on. On a site generated by our website builder the widget is included free of charge. The check that the add-on is paid for, on sites using the shared widget code, currently runs in observation mode and switches nothing off; on the Russian brands (cenaly.ru) there is no such check at all — the widget works there without a purchase.
• A document appears on the site only after publishing. Changes to your answers take effect when you publish — publishing rebuilds the documents in every language of the storefront.
• Some options are locked on purpose. A setting that contradicts answers you have already given is unavailable, with an explanation of exactly why: for example, a document cannot be removed while an answer that requires it is switched on.
• The widget renders nothing on its own. Your page needs containers for the links or the text; without them it silently outputs nothing (the programmatic call remains available).
• Only the cookie policy has live content — its table is assembled from the results of scanning your site (cenaly.ru has no scanning yet, so no table either). The other documents are updated by republishing.
• We do not track legal changes for you. When we revise the templates of a set, the widget panel shows “the document set has been updated — republish” and lists the sections whose text will change; republishing takes one button. Changes in the law that are not yet in the templates are yours to track.
• Own text is limited to 4,000 characters, without formatting. Publish a longer document, or one with tables, as a site page or via your own link.
• The consent line in checkout has no checkbox. It informs the guest of the terms but does not collect a separate consent to data processing.

Troubleshooting#

The site shows neither the links nor the document text.

1. Nothing has been published — the widget panel shows the “Publish N documents” counter and the list of what is already published: check that publishing went through.
2. No containers on the page — the link block and the inline text are rendered into your containers; without them there is nowhere to output them.
3. Tag not found — click “Check installation” in the My Website section. A tag inserted through Google Tag Manager is not detected by the check — nor are several other cases from the list “What the installation check does not see”.
4. Changes have not arrived — widget files are served through a CDN with a 5-minute cache: wait, then reload the page with the cache cleared.

The document is shown in the wrong language. The widget uses the language of your page; if the document does not exist in that language, the main publication language is shown, and if that is missing too, the first available one. Publish the missing language.

The “Publish” button does nothing. Look at the findings panel above the button: publishing is gated by a check of your answers — missing company details or contradictory answers are listed there with an explanation.

A link I already placed has stopped working. That should not happen: document addresses are stable, and republishing updates the content at the same addresses. Check that the document was not removed from the set during the last publication.

Related topics#

• My Website — the widget install code
• Cookies & Consent — banner and live cookie declaration
• Articles & pages (CMS) — where published pages live
• App Store — enabling the add-on

FAQ#

Can I link my own offer instead of using the constructor? Yes. “Articles and pages” → “📄 Site documents” → “Own link” for the document (or “Own text”, up to 4,000 characters). Footer links and the checkout line will lead there.

Why does checkout not show a line about the terms? The line appears only when the location has at least one of its own documents set — the terms of sale or the privacy policy. Set them in “Site documents”.

Are the documents available in every language of my site? Yes. The core wording of each country set is authored in the market's languages, other languages come from translation packs, and all languages of your site are published.

What happens if I change my answers and publish again? Existing pages are updated at their stable addresses, so links you have already shared keep working.

Does this work for a site that is not on your platform? Yes — that is exactly what the hosted mode and the widget are for.

Does this replace a lawyer? No. It is a solid market-grade draft that is cheaper and faster to review than to write from scratch.