PLIX← Back to PLIX
PLIX · SynergiX OÜ

Security and privacy

Updated 28 October 2026

Your business, conversations and knowledge have their own access scope. Find the controls we apply and the relevant processing terms here.

Separate access for each business

PLIX applies organisation permissions and database isolation controls. Access to conversations, contacts and knowledge must match the authorised business and user. We test cross-organisation access and permission revocation.

Protection and continuity

We use HTTPS, protected sessions, webhook signature checks and off-site backups encrypted before transfer. We monitor availability and backups. A verified backup is not equivalent to a tested full restoration. No system eliminates every risk.

Clearly identified AI

PLIX assistance uses selected business knowledge and per-request authorisation controls. Anthropic is identified in our provider inventory. PLIX does not use customer conversations to train general-purpose models. We do not claim provider zero retention without an applicable agreement.

When direct AI assistance is enabled, people must be able to recognise it from the first interaction. The notice can use the business brand, for example: “I am the AI assistant for [business]”. A real human support route must be configured. This explanation does not mean automatic messaging is enabled.

Documentation

Report an incident

Email admin@plixbot.com with the date, affected page and a description. Do not send passwords, API keys or complete customer conversations. If you encounter another business’s information, stop accessing it and report it without downloading or sharing it.