LynkMind

Security at LynkMind

Protecting customer information is part of how LynkMind is designed and operated.

This page describes our current security approach and will be updated as controls and certifications evolve.

Security approach

LynkMind applies security practices appropriate to an early-stage CRM, with an emphasis on least privilege, secure development, careful handling of customer data, and deliberate failure recovery. Only verified controls and current certifications should be treated as commitments.

Access control

  • Limit access to systems and customer information to authorised personnel and services.
  • Use least privilege for administrative and operational access.
  • Review access as roles change and remove access for former users.
  • Protect credentials and notify LynkMind of suspected unauthorised access.

Application and infrastructure security

Application security includes code review, dependency review, testing, and vulnerability management appropriate to the product. Hosting, database, storage, regions, network controls, and operational providers will be identified only after engineering verification.

Encryption, backups, and incidents

Encryption behavior, backup frequency, recovery objectives, retention, and incident-notification timelines require verified operational records and the applicable customer agreement. LynkMind will not publish unsupported certification or availability claims.

When a security incident is confirmed, LynkMind follows its incident-response process and provides notice as required by law and contract.

Customer responsibilities

  • Use strong, unique credentials and multi-factor authentication where available.
  • Assign permissions carefully and remove former users promptly.
  • Review connected-integration access and revoke it when no longer needed.
  • Do not upload data that LynkMind is not approved to support.
  • Report suspected security issues through the available contact channel.

Compliance and reporting

Current certifications: none publicly claimed on this page until independently verified.

A formal vulnerability disclosure process and security reporting address will be published when there is an operational process to receive and handle reports.