# Keep keys and passwords safe

An API key is a password that lets one program use your account on another service, such as Make or OpenAI. Anyone who has it can use your account, and you may pay for what they do. So keep keys out of chats, documents and shared folders. Projects keep them in a file called .env that is never shared, and each key gets only the access it needs.

## What to do
In File Explorer, tick View, then File name extensions, so you can see a file’s full name. In your practice folder, make three files in Notepad (choose Save as type: All files): 1) .env with one made-up line, FIXIT_DEMO_KEY=demo-not-a-real-key-123; 2) .env.example with the same name and no value, FIXIT_DEMO_KEY=, so others can see which keys the project needs; 3) .gitignore with the line .env, which stops the file being uploaded if you ever put the project on GitHub. Then paste this made-up line into your AI app and ask it to find any secret and say how to fix it: send_email(api_key="demo-not-a-real-key-123", to="owner@example.com"). Last, find where Make lists API keys in your profile, without making one, and write down what you’d do if a key leaked.

## It worked if…
The three files are in your practice folder with made-up values only. The AI found the key written into the code and said to read it from .env instead. You can name the three steps if a key leaks: delete it, make a new one, and check what it was used for.

## Your notes
- Which tool you used, and its version:
- What you started with:
- What you expected to happen:
- The steps you took:
- What actually happened:
- Where your screenshots are:
- What went wrong, and what you changed:
- What happened when you tried again:

Official guide: https://cheatsheetseries.owasp.org/cheatsheets/Secrets_Management_Cheat_Sheet.html

## Note down
- Where your .env file is:
- What .env.example shows:
- What .gitignore says:
- What the AI found in the code:
- What you’d do if a key leaked:
