Security and trust
Visibility software only works when people trust how it is used.
Kordano should present security and privacy as part of the product promise: clear permissions, practical controls, respectful visibility, and transparent product behavior.
Security posture page
Design the page to feel honest now, and ready to deepen later.
Do not fake certifications you do not have. Instead, explain the controls, architecture direction, privacy stance, and roadmap for future compliance work.
Permissions and access
Use role-based access, workspace-level organization, and manager-only visibility where appropriate.
Screenshot controls
Explain how screenshot history can be enabled carefully, with sensible access limits and optional blur patterns.
Data handling
Describe encryption in transit, secure storage plans, and how exported reports are controlled.
Transparent implementation
Tell buyers what the product tracks, how teams are informed, and how policies should be communicated.
Recommended future trust additions
Public security contact and response policy
Data processing and retention page
Status page link
Future compliance roadmap section