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.

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 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.

An important limitation#

These documents are templates, not legal advice. The disclaimer is shown in the dashboard and included as the final block of every generated document. 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.

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#

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.