PowerShell Genie

Privacy

PolicyPlain-language summary

Lessons are public. Google sign-in is optional for progress sync and required for category and topic sandboxes.

Without an account

Learning progress is stored in your browser using local storage. It stays on that browser and device unless you sign in. Clearing site data can remove it.

When you continue with Google

Google authenticates you. PowerShell Genie receives a verified Google account identifier plus the name, email address and profile image supplied by Google. PowerShell Genie never receives your Google password.

The site stores completed-learning markers and your most recent learning page so that you can resume on another signed-in device.

What is not uploaded for course sync

Commands typed into browser practice tools, tenant credentials, PowerShell session data and files from your computer are not required for progress sync. The browser labs use their documented sample data unless a page explicitly says otherwise.

Sessions

After sign-in, the site uses a secure, HttpOnly, SameSite cookie. The database stores a one-way hash of the session token rather than the token itself. Signing out invalidates that session.

Analytics

PowerShell Genie may use site analytics already configured on the website to understand page use and learning interactions. Account sync is separate from those analytics.

Your choice and deletion

You can use the public lessons without creating an account. Signing out does not delete progress already stored in that browser. When signed in, use Delete synced data in the account panel to remove the account and cloud progress stored by PowerShell Genie; local browser progress remains unless you clear it separately.

Daily practice and last-topic shortcut

The daily challenge stores exercise IDs, solved or missed status, and practice dates in your browser. A last-topic shortcut stores the most recently opened learning page. These features do not sync through Google. Use Clear daily history on the daily page to reset challenge history, or clear this site’s browser data to remove both. Command text and correction-report contents are not sent by these features. Correction reports are generated locally for download.

Learning analytics may record exercise starts, successful checks, retries, registration steps and lab downloads. These events use page paths and exercise identifiers, not pasted command text, Google credentials or report contents.

Timed category sandbox data

Sandbox commands are sent to the site for simulated execution and checking. They cannot run on your device or the website server. Use the supplied fictional data; do not paste passwords, tenant tokens or personal records.

While an attempt is active, the database holds its temporary virtual files, variables, function definitions, checked task IDs and server deadline. Command history is held only in browser memory. Temporary workspace data is deleted when you finish, when a destructive attempt blocks access, or on your next lab request after expiry. Expired workspaces cannot execute even before cleanup.

The retained result contains the category and version, checked-task count, total tasks, finish time, elapsed time and outcome. A sandbox access block retains the account ID, time and reason code. It does not retain the attempted command. Deleting synced account data also deletes these records.

Short topic sandbox data

Untimed lesson, command, script and project tasks send commands to the site for simulated execution and checking. The service rebuilds the fictional workspace for each request; it does not save this command history or these temporary files to the account database. The browser holds them in memory while the exercise is open and clears them when you leave.

Checked task identifiers and completion dates use the existing learning-progress store and Google account sync. Investigation exercises send selected answer numbers for checking. Daily sandbox selection uses completed topics where available and starts with beginner tasks otherwise. The original daily checkpoint archive keeps its separate local solved and missed history.

The same account sandbox block policy applies to prohibited commands. Public lessons remain accessible.