Skip to main content
Security and Data Privacy

How MCO (Fairwords) secures customer information

Updated over 12 months ago

SOC 2 Type II compliant

MCO (Fairwords) demonstrates the integrity of our security controls and procedures annually through a Service Organization Controls (SOC) 2 Type II audit.

Data Privacy & Guide Analytics

Guide statistics are captured, by default, anonymously without storing any user content. Guide is further designed to never capture any data marked as sensitive by applications, such as passwords and social security numbers.

Customers have the option of requesting Guide be set to non-anonymous mode, aka User Identity mode, to provide more specifically actionable context alongside the default training metrics. When capturing this additional context data, Guide automatically masks all sensitive numerical data and personal identifiers. This sensitive data is never stored as it serves no meaningful purpose in Guide notifications or analytics.

Data secure in transit and at rest

Fairwords customer data is always stored and transmitted encrypted.

  • Guide for Desktop uses AES 256 bit encryption and transmits over TLS 1.2

  • Messages sent to Fairwords via batch over SFTP

  • Email journaling supports Forced TLS

  • Data stored using AES 256 bit encryption

  • Web application access and messaging API uses HTTPS (TLS 1.2)

Application Authentication

Fairwords leverages industry-standard secure password policies for user-defined passwords. These policies are enforced when initially creating and subsequently updating them.

Microsoft Login (SSO)

Organizations may optionally use their Microsoft Entra ID tenant for SSO. Some organizations consider this easier to manage and keep consistent with enterprise security policies, including Multi Factor authentication (MFA).

See Microsoft Login (SSO) for more information.

Did this answer your question?