Documentation · Account · Updated 2026-09-12n
Terms, privacy and cookies
Terms and Privacy live in the footer. An admin can replace them with a CMS page on the same slug. The cookie banner is short: accept is stored in the browser, the link goes to Privacy.
Forms (register, contact, chat, leads) require a GDPR tick. The LAI chat stores name, email, phone and the thread for the session and for staff — it is not anonymous.
Where the copy lives
Footer → Terms and Privacy. A different wording means CMS overlays the slug. That is intended.
This documentation explains the product. It does not replace the contract. On conflict, Terms win.
What data we touch
Account (including Google id if you use Google sign-in), sites, leads, LAI chat, payment receipts (no full card number in demo). Export/delete from Profile, handled manually.
Cookies
Login session, locale, banner accept, LAI chat token (~2 hours). No ad network by default. Customer-site analytics are first-party counters.
Step by step
1
Read
Footer → both legal pages in your language.
2
Consent on forms
Required. Same idea in chat and on your site form.
3
Rights
Profile → GDPR, or Contact if you have no login.
Watch-outs
Do not paste customer personal data into tickets unless needed to fix the issue.
The banner does not return after Accept in that browser (localStorage).