Security at Worknize

Website safeguards

• HTTPS-focused browser protections, including strict transport, content-type, framing, referrer, and permissions policies.
• A content security policy that limits the sources the website can load.
• Validation, request-size limits, origin checks, timeouts, and abuse controls on the demo enquiry endpoint.
• Automated build, code-quality, and production dependency checks before landing-page changes are merged.

Product access

Worknize separates administrator and employee experiences and is designed to require authenticated access to product data. Security controls can change as the product evolves, so organisations should request the current control details that matter to their review.

Shared responsibility

• Use unique credentials and protect access to your email and devices.
• Review who has administrative access when staff roles change.
• Do not submit passwords, identity documents, payroll files, or other sensitive personal data through the public demo form.

Security questions

For a security review or to report a suspected issue, use the contact form and write “Security review” in the message. Do not include exploit code, credentials, or personal data in the first message; the team can arrange an appropriate follow-up channel.