Two settings pages in the Contract & legal group cover the legal side of your platform. Legal holds the documents your members and buyers accept or read, and Cookie Banner asks visitors for consent before optional cookies are used.
Your legal documents
The Legal page has five documents: Terms of Service, Privacy Policy, Imprint, Shipping information and Withdrawal policy. Each one starts as Off. Pick one of two ways to provide it:
- URL links to a page that already exists. The address must start with https://, http:// or a relative path like /terms.
- Content lets you write or paste the full text in the editor. Your platform then shows it on its own page, for example /legal/terms on your domain.
Where each document appears:
- Terms of service and privacy policy are part of the consent checkbox and are linked in the checkout footer.
- The imprint is linked in the checkout footer and the cookie banner. It is never part of the consent checkbox.
- Shipping information and the withdrawal policy are linked in the checkout footer. The withdrawal policy sits next to the online withdrawal form.
The checkout belongs to Payments. If Payments is off in your workspace, turn it on under Settings > Features.
Consent at registration and checkout
As soon as terms of service or a privacy policy are set up, new members tick a checkbox when they register. It links to whichever of the two documents you provide. Without the tick, registration stops with "Please accept the legal documents to sign up." Registration through Google sign-in does not show this checkbox.
Buyers see the same kind of checkbox in the first step of the checkout and cannot continue without it.
When someone registers, the acceptance is stored with the time, the IP address and the version of the document.
How versions work
Every document has a version that starts at 1. When you save a switch between Off, URL and Content, or a change to the URL or text, the version goes up by one. Saving without a change keeps the version. New acceptances always record the version that is current at that moment.
Choosing Content and leaving the editor empty is refused with a message. The same goes for URL without an address.
The data processing agreement
At the top of Legal, the Data Processing Agreement card explains how MemberArea processes personal data on your behalf under Art. 28 GDPR. Read the DPA opens the agreement, and Accept the DPA accepts it for your business. Only the owner or an admin can accept it. Your name, the date and time and your IP address are stored with the acceptance.
When a new version of the agreement is published, the card shows the date of the new version and asks you to accept again.
Turning on the cookie banner
The cookie banner is off in a new workspace. Its page has three tabs: Banner, Cookies and Consent log. Every change saves right away.
On Banner, switch on Show banner under Visibility & behavior. It then appears on your checkout pages. A checkout embedded on another site only shows it when Embedded checkouts is on, which is only needed if your embedded checkout loads tracking scripts.
- Reopen badge is on by default and lets visitors change their choice at any time.
- Enforce statistics consent blocks statistics scripts until the visitor agrees.
- Consent categories decides which of Statistics, Marketing and Preferences visitors can toggle. All three start off. Necessary cookies are always on.
Banner copy holds the text for each language, and the language list next to it switches between them. Unless you fix a language, the banner follows the language of the page, then the visitor's browser. Layout sets how the banner appears on the page, and Design sets a preset and colors.
Leave Privacy policy URL and Imprint URL under Links empty. The banner then uses the privacy policy and imprint from the Legal page.
Declaring cookies
On Cookies, Cookies you declare lists every cookie visitors see in the preferences dialog, grouped by category. Add cookie adds one with its name, provider, type, duration and purpose. Declared by MemberArea shows the keys the platform writes itself, so you do not need to add them.
Scan your site fetches a Page URL and detects third-party scripts. The results are suggestions. Add as cookie takes one into your list.
The consent log and asking again
Consent log shows every decision with Date, Surface, Decision, Categories and Locale, plus counts for all entries and for the last 30 days, both following your filters. Filter by surface, decision and date range. Export CSV downloads the filtered list.
After a policy change, Consent reset asks everyone again. Pick Re-ask all visitors, then Click again to confirm. The current version becomes today's date, and every visitor sees the banner again because their earlier choice belongs to the old version. Asking again works once per day.