Security overview
Whitnu Aware · last updated October 31, 2026
This page describes the security measures in place for Whitnu Aware, which is owned by CKL Technologies LLC, a limited liability company ("CKL"). CKL develops, hosts and operates Whitnu Aware itself: the software is written and maintained by CKL, and the server described below is rented and administered by CKL (the "operator" on this page). Whitnu and Whitnu Aware are trademarks and trade names (assumed business names) of CKL Technologies LLC, under which CKL develops, hosts and operates the Service. They are not separate legal entities, companies, subsidiaries or divisions; every right, obligation, contract, warranty, licence, indemnity, data-processing role and notice described in these documents is CKL Technologies LLC's. This page describes practices as the software and server are set up; it is a description, not a warranty or certification. It is referenced by the Terms of Service and the Privacy Notice. We update it when the measures change. Whitnu Aware is not designed to receive, store or process patient information, including any individually identifiable health information; the measures below are not offered as safeguards for patient information, customers must not enter it (Terms, sections 3.2 and 6.5), and CKL does not offer or sign a Business Associate Agreement. Security questions and incident reports: info@whitnu.com, or by mail to CKL Technologies LLC, 631 Brawley School Road #300-80, Mooresville, NC 28117.
Hosting
- The service runs on a dedicated virtual server at DigitalOcean (region: not declared by the operator yet), in a container, behind a web server that only accepts HTTPS. The host has a deny-by-default firewall, automatic security updates and brute-force protection on its remote-administration port.
- A host monitor checks the server, its configuration and its backups and alerts the operator.
- The web server's access logs (network address, browser type and the page requested, without sign-in link tokens) are kept for 14 days.
Access control
- Every account uses a second sign-in step. Administrators and the platform operator use a passkey. Sensitive actions (money, security settings, agreements, deletions) ask for the password and second step again.
- Repeated failed sign-ins lock the account for a while; passwords are checked against known breached passwords; idle sessions are signed out, sooner for administrators.
- Each organization's data is separated in the application: every query is scoped to the signed-in user's organization, and tests check that one organization cannot reach another's records.
- The service is administered by CKL; production access is limited to the people CKL authorizes.
Data protection
- Personal-data fields (names, email addresses, network addresses, audit details, agreement records and similar) are encrypted in the database with AES-256-GCM under keys derived from a master key; lookups use keyed fingerprints.
- The master key is kept in the server's protected configuration, or, in sealed mode, only in memory.
- Passwords are stored only as salted one-way hashes; authenticator secrets are encrypted; simulated-phishing link tokens are stored as hashes.
- The audit log of administrative actions is append-only and each entry is chained to the previous one with a keyed hash, so changes are detectable.
- Whitnu Aware has no feature for staff to report, submit or check a real email, so no real email's subject, text or attachments are received or stored through the Service.
- Pages are served with a strict content-security policy and other protective headers; state-changing requests from other sites are refused.
Backups and deletion
- Encrypted backups are made nightly. They are kept for 14 days on the server and, where the off-site copy is switched on, in DigitalOcean Spaces (location: not declared by the operator yet) for the lifetime set on the bucket (35 days).
- When an organization closes its account, its records are deleted from the live service after a 30-day export window, counted from the closure request or, where a second administrator must confirm it, from the confirmation. Backups cannot be selectively erased; they expire on the schedule above and are restored only to recover the whole service.
- Email is sent through an authenticated email provider. In production, simulated phishing is sent from its own sending address and domain, separate from the service's own mail (the service refuses to send simulations without one unless the operator explicitly allows the shared sender). Bounced and complaining addresses are suppressed.
Incident response
- We keep a written incident-response plan. If we discover a security incident that resulted in, or that we reasonably believe resulted in, unauthorized access to an organization's data, we notify its administrators without undue delay and in any case within 72 hours after discovering it, or sooner where the law requires, and we update them as we learn more.
- Vulnerability reports: see the vulnerability-disclosure policy.
Providers
The providers that process data for us are listed on the subprocessors page.