Welcome, Data-Protection Assistant

Summit Workplace Solutions wants an AI tool that can summarize information from its internal support database. The first design pulled in far more data than the task actually needed — including customer and employee details nobody asked for. Your job is to fix that.

The situation at Summit Workplace Solutions

A database can answer almost any question you ask it — which is exactly the problem. Before any data reaches an AI tool, someone has to decide what's actually necessary, what needs to be anonymized, and what should never leave the database at all.

Important: nothing here is a real, live database

This lesson never connects to a real database. Every table, record, and query you'll see is fictional and simulated, built entirely into this page using made-up sample data. You will never be asked to enter real database credentials anywhere in this lesson.

Essential question

How much of a database should an AI tool actually be allowed to see — and how do you make sure it only sees that much?

Estimated time

About 50 minutes, in 12 steps. Your progress is saved automatically, so you can pause and come back.

What you will be able to do by the end of this lesson

  • Read a simple database schema and identify its tables, records, and fields.
  • Build a simplified, safe SELECT query using guided options.
  • Identify when a query retrieves more data than a task actually needs.
  • Explain why parameterized queries are safer than building queries by gluing in raw text.
  • Decide what data should be minimized, anonymized, or removed before it reaches an AI tool.
  • Respond appropriately to a suspicious, injection-like entry in submitted data.

Before you begin

Enter your name so your completion report can be prepared. This stays on this device only — it is never sent anywhere.