Linkrium security
Security starts with clear boundaries and controlled access
Linkrium handles business conversation data. Its security posture therefore depends on encrypted transport, controlled workspace access, provider-safe integrations and responsible operational practices.
Linkrium is a multi-channel web application; security covers the path between channel providers, Linkrium services and authenticated workspace members.
Core controls
The public product description commits to encryption in transit, role-aware access and auditable actions. Exact controls can evolve as the platform matures.
- TLS for data in transit
- Authenticated workspace access
- Role-aware authorization
- Activity and audit records where supported
- Secrets kept outside the public frontend
Connected-channel responsibility
Each provider has its own permissions, tokens and account rules. Workspace owners should grant only the access required and revoke connections that are no longer used.
Responsible reporting
Report suspected vulnerabilities privately. Do not access other users' data, disrupt production or publish sensitive details before remediation.
Related guides
Frequently asked questions
Is customer data encrypted?
Linkrium states that messages are encrypted in transit. Storage and retention details should be reviewed against the current privacy policy and workspace agreement.
Does connecting a channel share its password?
A connection should use the provider's supported authentication method. Users should never email passwords to Linkrium.