# OpenClaw Safety Tips

This guide explains how to use your assistant safely.

Your assistant can be very helpful, but some actions are powerful and should be handled carefully.

The safest rule is simple:

If an action could change your computer, your files, your accounts, your money, your private information, or someone else's information, slow down and ask what will happen first.

---

## Start With A Sandbox Mindset

For beginners, the safest way to use OpenClaw is to keep it in a sandbox.

That means you should not casually connect it to your most private or financially important accounts.

Do not give the assistant direct access to:

- your personal email account
- your bank account
- your credit cards
- your payment accounts
- your tax accounts
- your medical portals
- your insurance accounts
- your password manager
- your identity documents
- your Social Security number
- your recovery codes
- your two-factor authentication codes
- private folders that contain sensitive personal records

Why this matters:
If an assistant, browser tool, account connection, command, or script gets too much access, a mistake could expose your identity, reveal private information, damage your finances, delete important files, or create a security breach.

Safe beginner rule:
Use the assistant first with test files, public information, project folders, and non-sensitive documents.

Do not connect private accounts until you understand the risks, have a clear reason, and are using a supported setup process.

---

## Protect Existing Assistants

If you already have another Claw/OpenClaw assistant installed, keep it separate from Builder Kit.

Do not delete, rename, reset, or overwrite `~/.openclaw` unless you are sure you are intentionally changing that separate assistant.

Builder Kit should normally use its own shared folder:

```text
~/.builder-kit
```

The default Builder Kit assistant runtime should normally use:

```text
~/.builder-kit/instances/main/.openclaw
```

A separate standalone Claw/OpenClaw assistant may use:

```text
~/.openclaw
```

Why this matters:
If Builder Kit and another assistant share the same folder, port, token, or runtime, you may accidentally open the wrong assistant or damage a working setup.

Safe beginner rule:
Treat `~/.openclaw` as private to another assistant unless you know for sure it belongs to the setup you are changing.

---

## 1. Things That Are Usually Safe

These are usually low-risk:

- asking questions
- brainstorming ideas
- summarizing text
- writing drafts
- explaining documents
- creating checklists
- organizing notes
- helping you understand a file
- suggesting next steps

Even with low-risk tasks, you should still review important answers before relying on them.

---

## 2. Things That Need Your Approval First

The assistant should ask before doing these:

- creating files
- editing files
- deleting files
- replacing files
- running commands
- installing software
- changing settings
- connecting accounts
- sending messages
- submitting forms
- making purchases
- changing calendar events
- moving or deleting emails
- changing Google Drive files
- posting to social media

If the assistant is about to take one of these actions, it should explain what it plans to do in plain English.

---

## 3. Do Not Paste Passwords, Keys, Recovery Codes, Or Identity Information Into Chat

Do not paste these into the assistant chat:

- passwords
- private API keys
- recovery codes
- two-factor authentication codes
- bank logins
- credit card numbers
- Social Security numbers
- passport numbers
- driver license numbers
- tax account logins
- medical portal logins
- insurance portal logins
- private legal documents unless you understand the risk
- private medical details unless you understand the risk
- documents that could be used to steal your identity

Better option:
Use a password manager or a secure setup process.

If an API key or password is needed, the safer approach is usually to place it in a protected configuration file, not in normal chat.

Best beginner rule:
If the information could let someone log in as you, spend your money, steal your identity, or access private records, do not paste it into chat.

---

## 4. Be Careful With Commands

Commands can be useful, but they can also damage files or change your system.

Be extra careful with commands that:

- delete files
- overwrite files
- change permissions
- install software
- expose secret keys
- stop services
- change networking
- modify system folders
- run unknown scripts from the internet

Before running a command, ask:

- What does this command do?
- What files or settings will it change?
- Can it be undone?
- Is there a backup?

The assistant should explain risky commands before running them.

---

## 5. Be Careful With File Editing

The assistant may be able to edit files.

This is powerful.

Before editing important files, ask the assistant to:

- show the proposed change
- explain why the change is needed
- make a backup if appropriate
- edit only the file you approved
- confirm what changed afterward

For beginners, complete file replacement is often safer than complicated partial edits because it is easier to review.

---

## 6. Be Careful With Email

Email can contain private information.

The assistant should not:

- read private email without permission
- send email without approval
- delete email without approval
- move or label email without approval
- reply to someone without showing you the draft first

Safe beginner request:
"Draft a reply, but do not send it."

---

## 7. Be Careful With Calendar

The assistant should not:

- create meetings without approval
- move meetings without approval
- cancel meetings without approval
- respond to invitations without approval
- invite other people without approval

Safe beginner request:
"Help me draft a meeting plan, but do not create the event yet."

---

## 8. Be Careful With Google Docs, Drive, and Sheets

Google files may contain private or business information.

The assistant should not:

- open private files without permission
- edit documents without approval
- move files without approval
- delete files without approval
- change spreadsheet data without approval
- share files with other people without approval

Safe beginner request:
"Summarize this file, but do not change it."

---

## 9. Be Careful With Websites

The assistant may help with websites, but some website actions are risky.

The assistant should not:

- enter passwords for you
- submit forms without approval
- buy products without approval
- change account settings without approval
- send messages without approval
- click financial, medical, legal, or account-management buttons without approval

For logged-in websites, you should usually handle the login yourself.

---

## 10. Be Careful With Money, Banking, and Purchases

Do not let the assistant directly control:

- bank accounts
- investment accounts
- payment accounts
- credit cards
- tax filing
- purchases
- bill payments
- money transfers

The assistant can help explain, organize, draft, or summarize information, but important financial actions should be handled by you or a qualified professional.

---

## 11. Be Careful With Medical, Legal, Tax, and Financial Advice

The assistant can help explain general information.

The assistant should not replace:

- a doctor
- a lawyer
- a tax professional
- a financial advisor
- a licensed therapist
- an insurance professional

For important decisions, use the assistant to prepare questions, organize information, or understand options — then check with a qualified expert.

---

## 12. Be Careful With OCR and Image Reading

OCR means reading text from images, screenshots, scanned pages, receipts, or forms.

OCR can make mistakes.

Always verify:

- names
- dates
- phone numbers
- addresses
- prices
- totals
- legal language
- medical information
- account numbers
- instructions

Safe beginner request:
"Extract the text, but mark anything you are unsure about."

---

## 13. Be Careful With Image Generation

Generated images may look convincing but still be wrong.

Be careful using generated images for:

- logos
- medical images
- legal documents
- product claims
- official forms
- real people
- exact brand designs
- anything that must be accurate

Always review images before publishing or selling them.

---

## 14. Be Careful With Voice and Audio

Voice tools may involve recording or uploading audio.

Before using voice features, understand:

- whether audio is stored
- where audio is sent
- whether transcripts are saved
- whether private information is included
- whether the transcript may contain mistakes

Always verify important names, numbers, dates, medical details, legal details, or financial details.

---

## 15. Be Careful With Automation

Automation means asking the assistant to do something repeatedly or in the background.

Automation can be useful, but it needs clear limits.

Be careful with automation that:

- checks accounts
- sends messages
- changes files
- posts online
- monitors websites
- makes decisions
- runs commands
- handles private information

Safe automation rule:
The assistant can monitor or draft, but should ask before taking important actions.

---

## 16. Always Keep Backups

Before important changes, make backups of:

- project files
- configuration files
- documents
- databases
- scripts
- settings

If something goes wrong, backups make recovery much easier.

---

## 17. Good Safety Questions To Ask

Before approving a risky action, ask:

- What will this change?
- What file will be edited?
- What command will run?
- Can this be undone?
- Is there a backup?
- Will this expose private information?
- Will this contact another person?
- Will this affect money, accounts, or legal obligations?
- Should I ask an expert first?

---

## 18. Best Rule For Beginners

When in doubt, ask the assistant to explain first.

Good request:

"Explain what you are about to do before doing it."

Even better:

"Show me the proposed change, but do not apply it yet."

---

## 19. When To Get Expert Help

Get expert help before using the assistant for:

- legal decisions
- medical decisions
- tax decisions
- investment decisions
- security changes
- business-critical systems
- deleting important data
- changing production websites
- connecting private accounts
- handling sensitive customer information

The assistant is a helper, not a replacement for expert judgment.

---

## 20. Safe Default Behavior

A safe assistant should:

- explain before risky actions
- ask before changing files
- ask before running commands
- ask before sending messages
- ask before accessing private accounts
- avoid storing sensitive information unless requested
- admit uncertainty
- suggest expert help when appropriate
- help the user stay in control

The goal is not to make the assistant weak.

The goal is to make it useful, safe, and trustworthy.