Visitor chat is off until an org owner or admin accepts the Art. 28 DPA in Organization → Settings. After that, signed-in visitors on published sites with visitor login enabled see a chat button above their avatar menu — including on pre-launch coming-soon pages. Messages appear in Dashboard → Inbox.
Before you enable chat
Visitor support chat involves personal data — message content, account identity, and optional attachments. Your organization is the data controller; Aveiro processes messages on your behalf as Auftragsverarbeiter under Art. 28 GDPR.Before chat can go live:
Update your site privacy notice — tell visitors that you operate support chat, that Aveiro processes messages for you, that sign-in requires a platform account, and how long messages are kept.
Accept the agreement — an organization owner or admin opens Organization → Settings, reviews the visitor support chat section, and accepts the data processing agreement.
Set retention — choose how long messages are stored. Messages older than the selected period are deleted automatically; Indefinitely disables automatic deletion.
Until the agreement is accepted, the chat button does not appear on published sites — visitors never see a disabled or “setup required” bubble on the public site.
Enable visitor login on the site
Chat is only available to signed-in visitors. Enable the login chrome on each site where you want chat:
Open the site in the editor.
Go to Settings → Visitor login.
Turn on Enable visitor login and pick Bottom right or Bottom left.
Publish Site settings so the live site updates.
Human support chat works on fully live sites and on pre-launch (coming soon) pages — as long as the site has published public content and visitor login is enabled. The AI visitor assistant (when enabled in site settings) only appears after the site leaves coming soon mode.See Visitor login for details on positioning and publish behavior.
What visitors see
Visitor state
Chrome on the live site
Anonymous
Aveiro login bubble only (if visitor login is enabled)
Signed in, chat disabled for org
Avatar menu only — no chat button
Signed in, chat enabled
Chat button stacked above avatar menu in the same corner
When a signed-in visitor opens chat:
A support panel opens in the same corner with message history and a composer.
They can send text, emoji, and image attachments.
The conversation stays tied to their Aveiro account if they return later.
Opening the panel loads an existing conversation when one exists. A new thread is created only when the visitor sends their first message — opening the widget alone does not add an empty entry to your Inbox. Aveiro does not fetch chat history until the visitor opens chat (data minimization).
Authentication flow
Sign-in uses the auth bridge:
Visitor taps Sign in on your site.
They authenticate on the Aveiro platform (existing account or new sign-up).
Aveiro redirects back to your site and sets a host-bound visitor session on your domain (including custom domains and *.aveiro.page).
The site reloads with the signed-in chrome.
The bridge only returns visitors to published site URLs on your allowlisted hosts.
Message retention
Organization → Settings includes a Message retention control for visitor support messages.
Setting
Effect
Preset periods (e.g. 3, 6, 12 months)
Messages older than the period are deleted automatically
Indefinitely
No automatic deletion — you remain responsible for storage limitation (Art. 5 GDPR)
Only organization owners and admins can change retention.
Re-acceptance
If the data processing agreement is updated, chat may pause until an owner or admin re-accepts the current version. Check Organization → Settings if conversations stop accepting new visitor messages.
