AI Usage · No-Coders Module 5 of 7 · must pass

🔒 This module opens once you've passed the one before it.

Go to module 4 · Back to the hub

Module 5 · about 10 minutes · mandatory

The red lines: what never goes into an AI tool

This is the one module everyone has to pass, and the one habit that protects you, your colleagues and our players. It's short, and it's not complicated.

If you wouldn't pin it on the office noticeboard, don't paste it into an AI tool.
  • 1 · The red lines
  • 2 · Sort 10 snippets
  • 3 · Quick quiz
  • 4 · One thing to remember

1 Why this matters, in one paragraph

When you paste something into an AI tool, it leaves your hands. Even in a tool the company has approved, you should assume the text may be stored, seen by someone else, or turned up later. That's fine for a draft newsletter. It is not fine for a player's details, a password, or a contract we've promised to keep confidential. The rule is not "be careful". The rule is "these things never go in, full stop".

The red lines

🎰

Player and customer data

Names with emails, IDs, addresses, deposits, bets, account numbers, support history. Anything that points at a real person who plays or buys from us.

🔑

Passwords and access

Logins, Wi-Fi keys, door codes, the long access codes IT hands out for a system, "the shared password for...". Whatever the tool, whoever built it: never.

📜

Contracts under NDA

The text of agreements we've promised to keep confidential, and the figures inside them: rates, shares, fees, penalties.

🤫

Unreleased deals and news

Acquisitions, partnerships, launch dates, results, anything not yet announced. "It's public next week" means it isn't public now.

🧑‍🤝‍🧑

Anyone's personal information

Colleagues count too: salaries, health, home addresses, performance notes, personal phone numbers.

What's fine

Your own wording. Public information. Templates. General descriptions with the identifying details taken out ("a client", "[amount]", "[date]").

The trick that makes almost everything usable: strip it first

You rarely need the sensitive bit to get good help. You need the shape of the situation.

Never paste

"Jonas Berg (player ID 88213, jonas.berg@example.com) deposited €2,400 on 3 May and is asking about his missing bonus. Write him a polite reply."

Safe to paste

"A player made a deposit and is asking about a bonus that hasn't appeared. We're looking into it and will update within one working day. Write a polite, reassuring reply. Use [Name] as a placeholder."

Same help, zero risk. You put the name and the number back in yourself, at the end, in your own systems.

If you realise you've already pasted something you shouldn't have: don't hide it and don't try to "delete the chat and forget it". Tell your manager or IT straight away. Nobody gets in trouble for reporting a slip. People get in trouble for burying one.

2 Mini-game · Safe to paste, or never?

Ten real-looking snippets, the kind that land in your day. Sort each one. Get one wrong and you'll see why, then you can re-sort it. You need all ten right to unlock the quiz, because this is the module where "mostly right" isn't enough.

Sorted correctly
0 / 10

3 Quick quiz

🔒 Finish the sorter above with all ten right, and the quiz appears here.

One thing to remember

Noticeboard test. If it couldn't be pinned up in the office for anyone to read, it doesn't go into an AI tool. Strip the details, then ask.

Pass the quiz to open module 6.