Privacy approach

Awareness insight with privacy-conscious defaults.

Smish-Aware is designed to limit information to the authorised security-awareness purpose and to make aggregate insight the normal reporting experience.

Data minimisation Aggregate insight Small-group protection
Privacy by Design

Privacy is part of the architecture.

The awareness purpose shapes how information is collected, interpreted, accessed and reported.

⌁

Data minimisation

The platform is designed to use the information needed to operate an authorised simulation and provide awareness education. Campaign interaction data supports awareness reporting; it is not presented as forensic evidence.

◇

Access control

Access to operational information is designed around authorised users and legitimate awareness purposes. Aggregate reporting is the default for broader campaign insight.

◫

Small-group protection

Aggregate reporting protects small groups by suppressing applicable results rather than presenting fabricated zero values.

↺

Lifecycle-based handling

Data collection and retention are designed to remain proportionate to the authorised awareness purpose, with lifecycle governance treated as part of the platform's privacy design.

◎

Measure awareness without profiling people.

Smish-Aware is designed to help authorised teams understand awareness outcomes without turning individual behaviour into a permanent employee risk label.

  • Aggregate reporting is preferred for broader campaign insight.
  • Applicable small-group results are suppressed.
  • The platform does not create employee risk rankings.
  • Awareness events are not presented as proof of a person's intent.
✦

Interpret signals with appropriate limits.

Security-awareness data has context. A send, click or other platform interaction describes an observed event; it should not automatically become a judgement about the person behind it.

  • Provider acceptance is not proof of handset delivery.
  • Interaction data supports awareness reporting.
  • Automated analysis does not prove a message is safe or malicious.
  • Operational evidence should be interpreted for its stated purpose.
Product-level information, not legal advice.

This page describes privacy principles in the application. It is not a legal privacy notice or a substitute for an organisation's approved privacy policy. External services, backups and infrastructure have their own governance requirements; this page does not make third-party deletion claims.

Smish-Aware

Security awareness can be useful without being invasive.

Build practical awareness around authorised simulations, proportionate information use and reporting designed around learning.