Question 1

How is organizational data protected in transit and at rest?

Accepted Answer

LINK is designed around end-to-end encryption. Messages are encrypted on the sender's device and decrypted only by the verified recipient; our managed infrastructure acts as a transport layer and does not hold message decryption keys. Data at rest on our infrastructure is encrypted with AES-256, and all transport is TLS 1.3. This describes our architecture, it has not yet been validated by an independent third-party audit, and we will publish those results here when they exist.

Question 2

What is your deployment and infrastructure model?

Accepted Answer

LINK is delivered as a fully managed, multi-tenant SaaS environment with per-tenant isolation. This turnkey model provides secure deployment without the weeks of server hardening, database hosting and ongoing patching required to maintain self-hosted open-source alternatives. Customers do not run, patch or scale any infrastructure.

Question 3

Does the platform meet international privacy benchmarks?

Accepted Answer

LINK is built to GDPR and UK GDPR requirements. A Data Processing Agreement with EU Standard Contractual Clauses and the UK International Data Transfer Addendum is available to enterprise customers, alongside a contractual 72-hour breach notification commitment. We do not currently hold a SOC 2 Type II attestation or ISO 27001 certificate; external penetration testing and independent audits are planned and the reports will be published here.

Question 4

How do you handle HR investigations without compromising E2EE?

Accepted Answer

Users flag policy violations by submitting encrypted, watermarked incident reports from their client. Only your organisation's authorised HR or compliance officers hold the keys to decrypt those specific reports, LINK cannot read them, and no blanket surveillance of private chats is possible. Reports are pseudonymous rather than anonymous: the reporter's identity is withheld from HR by default, but LINK retains the reporting account's username and can be compelled to disclose it under a binding legal order. HR may ask a reporter to identify themselves voluntarily and the reporter may refuse.

Question 5

Who can access our tenant data internally?

Accepted Answer

Access to production systems is restricted to a small number of named engineers, requires multi-factor authentication, and is logged. No LINK employee can read message content, because we do not hold the decryption keys. Support access to tenant metadata is time-boxed and recorded in an audit log available to your administrators on request.

Question 6

What happens to our data when we leave?

Accepted Answer

On termination, tenant data is exported on request in a machine-readable format and then deleted from live systems within 30 days, and from backups on the next rotation cycle (maximum 35 days). Deletion is confirmed in writing.

Trust & Security Center

CISO FAQ

Documentation & contact