Privacy policy
What CyberGuard Academy collects, why, who else can see it, and how to get it back or have it deleted.
Last updated November 12, 2026
This document is not finished.
The details below have not been filled in yet, so this page is not indexed by search engines and must not be relied on. Each one appears in the text as a visible marker rather than a guess.
- The legal name of the business selling the service.
- A monitored address for privacy requests and legal notices.
- A postal address where a legal notice can be served.
This policy covers [to be completed: legal business name] and the CyberGuard Academy service. It is written to be read, not to be survived, so it is in plain English and it is specific about what actually happens.
One distinction shapes everything below. When a company signs up, that company decides what employee information goes into the service and what training is assigned. We hold and process that information on their instructions. In data-protection language they are the controller and we are the processor; in practical terms, if you are an employee asking why you were assigned a course, your employer is the right place to start, and we will help them answer you.
What we collect
From the person who signs a company up: their name, work email address, the company name, and a password that is stored only as a hash by our authentication provider — we never see or hold the password itself.
About each employee added to a company account, only what training requires:
Name, work email address, and preferred language (English or Spanish).
Their role in the account — employee, administrator or owner — and whether the account is active.
Training records: which courses were assigned, which lessons were completed and when, time spent on a lesson, quiz attempts with the score and the answers given, and whether a certificate was issued.
Phishing simulation results, where a company runs them: the address the simulation was sent to, whether it was delivered, and whether the employee clicked the link or reported the message — each with a timestamp.
An audit record of significant account actions, such as an invitation being created or accepted, a course being assigned, or a simulation being launched.
What we deliberately do not collect
These are design decisions, not omissions, and each one is enforced in the product rather than promised in a policy:
Passwords are never captured by a phishing simulation. Some products in this category simulate a login page and record what the employee types. Ours does not, and the page an employee lands on contains no form of any kind. A page that collects a real corporate password — even to discard it — has held a real corporate password, and it teaches staff that typing credentials into an unfamiliar page is something their employer does.
We do not measure whether an email was opened. There is no tracking pixel and no
openedfield in our database. Mail providers and corporate scanners fetch remote images on a recipient's behalf whether or not anyone read the message, so an open rate is a number largely assembled by machines. Clicking a link and reporting a message are deliberate human acts, so those are what we record.No advertising or analytics trackers. There is no Google Analytics, no advertising pixel, and no session-recording tool anywhere in the product. The application also ships a Content Security Policy that only permits connections to our own servers, our database provider and Stripe, so a tracker introduced later would be blocked by the browser rather than quietly start collecting.
No card numbers. Payment details are entered on pages hosted by Stripe and never pass through our systems. There is no card field anywhere in this application.
No selling, ever. We do not sell personal information, and we do not share it for advertising or cross-context behavioural advertising. We have no advertising business for it to serve.
Why we hold it
To deliver the training a company has assigned, to show that company who has completed it, to issue and verify certificates, to run the simulations they ask for, to bill the account, and to keep the service secure and working.
We do not use employee training records to build profiles, to train machine-learning models, or for any purpose a customer has not asked for.
Who else processes it
We run on four services, all of them US-based. Each one is listed here with what it actually touches, because a subprocessor list that only names companies tells a reader nothing:
Supabase — the database and the authentication system. This is where employee records, training progress and quiz results are stored.
Vercel — application hosting. Processes requests and keeps operational logs, which include IP addresses for a limited period as part of normal server operation.
Stripe — payments. Receives the billing contact and the number of seats on the account. Holds the card details, which we never see.
Resend — transactional email: invitations, training reminders and simulation messages. Receives the recipient address and the message content.
How long we keep it, and how to get it out
An administrator on a company account can export that company's full record at any time, from Settings. The export is machine-readable and covers employees, assignments, progress, quiz attempts, certificates and simulation results — everything the account holds, not a summary of it.
An administrator can also request deletion of the entire account from the same screen. Deletion is permanent and it removes employee records, training progress, quiz attempts, certificates and simulation results. Two things deliberately survive it: the audit record of the deletion itself, and the billing records we are required to keep for tax and accounting purposes.
If an account is closed and no deletion is requested, we keep the data so that the company can come back to it, and we delete it after twelve months of inactivity.
An employee who wants their own record exported or deleted should ask their employer's administrator, who can do both. If that is not possible, write to us at [to be completed: contact email] and we will help.
Your rights
Depending on where you live you may have the right to see what we hold about you, to correct it, to have it deleted, to receive a portable copy, and not to be discriminated against for asking. California residents have these rights under the CCPA as amended, and residents of several other US states have equivalent ones.
You can exercise all of them by writing to [to be completed: contact email]. We will not charge you for it and we will not ask you to create an account to do it. If your information is in an employer's account, we will work with that employer to answer you, and we will tell you that is what we are doing.
Children
This is a workplace product sold to businesses for their employees. It is not directed at children and we do not knowingly collect information from anyone under 16.
Security
Each company's data is isolated in the database itself rather than by filters in application code, so a request for another company's records is refused by the database regardless of what the application asks for. We describe the specific measures, and what we do not claim, on the security page.
No system is perfect. If you believe you have found a vulnerability, write to [to be completed: contact email] and we will respond. We will not pursue anyone who reports a genuine issue to us in good faith.
Changes to this policy
The date at the top changes whenever the text does. If a change meaningfully affects what we collect or who we share it with, we will tell account administrators by email rather than relying on anyone noticing a new date.
Contact
[to be completed: legal business name]
[to be completed: mailing address]
[to be completed: contact email]
This page is a description of how the service works and how we handle information. It is not legal advice, and it does not replace advice from your own counsel about your obligations.