Peak Chat · Security & privacy
Conversations belong
in your workspace.
Security and privacy in Peak Chat: one workspace, roles and rights, row-level security in the database, AI only through the Peak AI Gateway. No certification claims.
What do you want to settle before using Peak Chat?
2 questions in the plan. First question: Who on our team should read and answer website conversations?
What Peak One does today
One workspace. Clear rights.
Who on our team should read and answer website conversations?
A chat collects trust. And data.
People who write on your website share names, questions and sometimes more. So Peak Chat follows the same rules as the rest of Peak One: everything lives in one workspace, roles and rights decide access, and the database enforces those rights on every row. In the inbox, Peak Chat reads and sends through the accounts your workspace connected itself. For Peak Helpdesk's guest live chat, Peak stores a visitor's access token only as a hash. Whether that covers your obligations is a question for your privacy advisor.
From reading to doing
Your review questions. For your team.
Talk this through before you start.
2 questions selected
- Who on our team should read and answer website conversations?
Decide which roles see conversations. Workspace guests see only what is shared with them.
- Through which accounts should Peak Chat read and send?
The inbox uses the accounts your workspace connects itself, such as Gmail, Outlook, Slack, Teams or WhatsApp Business.
What protection
consists of today.
Peak Chat is not an island. It runs in the same workspace as the other Peak One apps and uses the same rules for access and AI.
Who on our team should read and answer website conversations?
Decide which roles see conversations. Workspace guests see only what is shared with them.
One workspaceConversations, contacts and tasks live in the same workspace, not in a second database.
Roles and rightsOwner, admin, member and guest. The database checks on every read who may see a record.
AI through the gatewayEvery model call goes through the Peak AI Gateway, never straight to a provider.
The playbook
How to review Peak Chat before you use it.
Who may
see what?
Workspace → role → record
- 01
Roles first. Then conversations.
Check who in your workspace is owner, admin, member or guest. The database enforces these rights on every read, not just the interface.
ExampleEveryone sees every conversation
Sales and service see website chats, guests do not. - 02
Connect on purpose.
Connect only the accounts Peak Chat should read from and send through. Peak uses your workspace's connections, not credentials of its own.
Check before connectingA colleague's personal mailbox
The workspace's shared team account - 03
AI through one door.
No Peak One module calls an AI model directly. Every call goes through the Peak AI Gateway with its rules and budgets. New AI features in the chat are meant to take the same route.
Narrow AI down
AI only via the Peak AI Gateway, with approvalAI simply reads everything
Your quality check
Have you covered the essentials?
Tick what you have checked. Your selection stays in this view only.
0 of 4 points checked
What this article is based on.
Overview of what Peak One does today, not legal advice and not a certification. Workspace, roles, row-level security and the Peak AI Gateway exist today; most AI features inside the chat are planned. We do not promise compliance with any specific law.
- Editorial demo
Editorial example with made-up sample data. The Peak Chat inbox and Peak Helpdesk's guest live chat exist today; everything else is marked as planned or example.
Settled before the first conversation.
See which accounts and apps Peak Chat connects today.
Frequently asked questions
Is Peak Chat certified?
We do not claim any certifications. The page only describes how Peak One handles access and AI today.
Who sees the conversations?
Whoever has the required role in your workspace. The database checks rights on every read.
How are guest chats on the website protected?
In Peak Helpdesk's live chat, a visitor's access token is stored only as a hash.
Is using it automatically GDPR compliant?
We do not promise that. Your obligations depend on your company; settle them with your privacy advisor.