Legal Pages

Workspace and access

Pick a workspace first—legal content is stored per company. Without a workspace you only see a short prompt to select one.

Members who cannot edit the workspace see legal text read-only (the editor is disabled); the cookie-banner switch uses the same permission and shows a tooltip when you are not allowed to change it.

Legal disclaimer (required before editing)

At the top, a collapsible panel explains your responsibility for compliance and Okinta’s role as a hosting provider under EU rules (Digital Services Act, E-Commerce Directive). Expand or collapse it with the chevron.

You must tick the checkbox once to acknowledge that text. The app records that acknowledgment per user and per workspace (including version and exact wording) for audit purposes—each person who saves legal pages needs their own acknowledgment, not only the account owner.

Until you have acknowledged, the rich-text area is replaced by a placeholder with a shortcut to scroll back to the disclaimer. Save is also blocked with a toast if you try to save without acknowledging.

Cookie banner switch

A dedicated card lets editors turn the visitor-facing cookie banner on or off for the workspace (stored on the company record). This app does not include a separate field to edit the banner message body—that copy is whatever your workspace already uses on public pages.

Document types and where they are used

Required types (tracked in Progress as *completed* when saved with enough text): Terms of service, Privacy policy, and Legal notice—the UI notes they are intended for the website footer.

Optional types: Refund policy (typically linked from the payment flow), Conditions of use, Cookie policy, Return policy, Shipping policy, and Disclaimer—each shows a short Displayed in … hint (e.g. direct links only vs footer vs payment page).

Sidebar, progress, and mobile

On large screens, a left card lists all types under Required and Optional with a Progress badge (e.g. *2/3* until every required page meets the completion rule). A check icon means that type is saved with sufficient content; an empty circle means it still needs work.

On small screens, open the same list from a panel button so you can jump between documents without crowding the editor.

Editor, length rule, and save

After acknowledgment, each document opens in a rich text editor (Lexical-based). The active document’s title shows whether it is required and repeats where it is displayed.

Saving uses an explicit Save button (not continuous auto-save). Save stays disabled until you have unsaved changes and until plain text extracted from the editor reaches at least 200 characters—a counter shows *current / 200* so you know when you have met the minimum.

A note reminds you that saving updates the “last updated” behavior visitors rely on. The header can show last updated (date from the server) and an unsaved changes marker while edits differ from the last saved version.

Preview and public link

Preview (opens in a new tab) and copy link stay disabled until that document is complete (saved with enough text). Use them to check the live page or share the exact address once the policy is ready.