Free AI safety guidance. No email required.Open the safety page

AI Safety

Stop. Switch. Confirm.

A simple response to AI-assisted phishing, cloned voices, fake video, urgent payment requests, and messages designed to make you act before you think.

01

Stop

Do not click, pay, share a code, install software, or continue the call just because the message feels urgent.

02

Switch

Leave the message or call. Use a trusted number, saved contact, official app, or website you open yourself.

03

Confirm

Verify the person, request, amount, and action through that separate channel before doing anything.

The simple list

Do this. Do not do that.

The scammer wants speed, secrecy, and a single channel. Your defense is time, separation, and independent confirmation.

Do

  • Pause when a message creates fear, urgency, secrecy, or unusual pressure.
  • Open the official app or website yourself instead of using the link in the message.
  • Call a known number from your contacts, statement, card, or official website.
  • Use a family or team verification phrase for emergencies.
  • Report suspicious messages so other people are warned.
  • Preserve screenshots, numbers, timestamps, and payment details when safe to do so.

Do not

  • Trust caller ID, a familiar voice, a logo, or a convincing video by itself.
  • Share passwords, one-time codes, recovery codes, or remote access.
  • Move money because someone says the request must remain secret.
  • Pay by gift card, cryptocurrency, wire, cash courier, or unfamiliar payment route under pressure.
  • Call the number inside a suspicious message to verify that same message.
  • Assume perfect grammar, personal details, or a realistic voice proves identity.

Recognize the pattern

AI makes old scams faster and more convincing.

The core warning signs did not retire. They put on a cleaner shirt.

@

Phishing message

Watch for unexpected account problems, fake invoices, delivery failures, shared documents, password resets, job offers, or urgent executive requests. Hover or inspect carefully, but verify through the official service rather than the embedded link.

Cloned phone call

A voice may sound like a child, manager, officer, doctor, bank worker, or vendor. Hang up and call the person or organization through a known number. Ask a question the caller would not know from public information.

Fake or altered video

Do not rely on visual realism alone. Confirm through another live channel and look for the business process that should surround the request: normal approval, known account, documented change, and a second person.

$

Money or access request

Any surprise change to bank details, payroll, password reset, remote access, account recovery, gift cards, or urgent transfer deserves a separate confirmation step.

For families and teams

Create the verification path before the emergency.

A good plan should still work while someone is frightened, tired, embarrassed, or in a noisy parking lot.

  1. Choose a verification phrase. Keep it memorable, private, and change it if exposed.
  2. Save trusted numbers. Family members, supervisors, bank fraud lines, IT support, and key vendors.
  3. Require a second channel. Voice request becomes a known-number call, in-person check, or approved business workflow.
  4. Require two people for high-risk changes. Money movement, bank details, account recovery, access, and public crisis messages.
  5. Practice once. A five-minute drill beats a forty-page policy nobody can find.

Information boundary

Use the Data Traffic Light.

When you are unsure, move the information up a risk level until the organization approves it.

Green

Public information, approved templates, generic examples, and content already intended for broad release. Normal review still applies.

Yellow

Internal operations, draft plans, non-public meeting notes, vendor details, or limited personal information. Use only in an approved tool with a clear purpose and review.

Red

Passwords, recovery codes, payment data, health information, protected client records, legal strategy, secrets, regulated data, or anything the organization has not approved for AI. Do not upload.

Something happened

Contain first. Explain later.

People delay reporting when they fear punishment. That gives the problem more time to move.

  1. Stop the action. End the call, disconnect remote access, stop payment if possible, or disable the affected workflow.
  2. Use the official incident path. Contact IT, leadership, the bank, service provider, or local authorities through trusted channels.
  3. Preserve useful evidence. Screenshots, timestamps, addresses, numbers, transaction details, and what was shared.
  4. Change exposed access. Passwords, sessions, tokens, recovery settings, and account permissions as directed.
  5. Warn the people at risk. Keep the message factual. Do not forward active malicious links.
Official guidance behind this page

The FTC, FBI, and CISA recommend pausing, independently verifying through known contact information, protecting account codes, and treating unusual urgency or payment methods as warning signs.

Next useful step

Give the team something they can use today.

Download the two-page guide or open the fuller starter kit with information classes, review rules, incident notes, and a 90-day adoption path.

Resource access

Get the resource

Enter an email address to receive access.

We use this information to deliver the resource and understand which materials are useful. We do not sell it. See the privacy page.

Your link is ready.

It expires after 24 hours. The link may also be emailed when delivery is configured.

Download the resource