Help & FAQ

Cloak intercepts messages before they're sent to ChatGPT, automatically detecting and replacing sensitive information (like emails, phone numbers, credit cards) with tokens. When ChatGPT responds, Cloak restores your original data so you see the real information, but ChatGPT never received it.

No. All processing happens locally in your browser. Cloak never sends any data to external servers. Your sensitive information is only stored temporarily in your browser's local storage to restore it in responses.

Cloak detects and protects 16+ types of PII including: email addresses, phone numbers (including international formats), credit card numbers, SSN, EIN, NINO, IP addresses (IPv4/IPv6), API keys, MAC addresses, IBAN, routing and account formats, UUIDs, dates of birth, passport numbers, driver's license numbers, UK postcodes, and more.

Yes. Click the Cloak extension icon in your browser toolbar to open the popup, then toggle the "Protection" switch to enable or disable anonymization.

Currently, Cloak is optimized for ChatGPT. Support for other AI chatbots may be added in future versions.

Yes. In the extension popup, open the Settings section and toggle individual PII types on or off according to your needs.

No. Cloak is designed to be lightweight and fast. The anonymization and restoration processes happen almost instantly and shouldn't noticeably impact ChatGPT's performance.

Yes, Cloak is completely free and open source. There are no hidden fees or premium features.

1. Check if Cloak is enabled

• Click the Cloak extension icon in your browser toolbar
• Ensure the "Protection" toggle is ON

2. Verify you're on ChatGPT

• Cloak only works on chat.openai.com or chatgpt.com
• Make sure you're on the correct domain

3. Refresh the page

• Sometimes a refresh is needed after installation or updates
• Press F5 or Cmd/Ctrl + R

4. Check browser console

• Open Developer Tools (F12 or Cmd/Ctrl + Shift + I)
• Go to the Console tab
• Enable Debug Mode in the extension popup for detailed logs

1. Check conversation context

• Make sure you're in the same conversation where you sent the anonymized message
• Cloak tracks entity maps per conversation

2. Verify anonymization worked

• If you see tokens like [EMAIL_1] in your sent message, anonymization worked
• If you see the original PII, anonymization didn't trigger

3. Try Debug Mode

• Open the extension popup, enable "Debug Mode"
• Check the browser console for restoration logs

If Cloak is anonymizing something that isn't actually sensitive:

• This is rare but can happen with certain patterns
• Disable specific PII types in Settings if needed
• Report the issue so we can improve detection

1. Pin the extension

• Click the puzzle piece icon in your browser toolbar
• Find Cloak and click the pin icon to keep it visible

2. Check installation

• Go to chrome://extensions/ (or edge://extensions/)
• Verify Cloak is listed and enabled

Debug Mode gives detailed logging for troubleshooting:

1. Open the Cloak extension popup
2. Enable the "Debug Mode" toggle
3. Open Developer Tools (F12 or Cmd/Ctrl + Shift + I)
4. Go to the Console tab
5. You'll see logs of anonymization and restoration

Note: Turn Debug Mode off for normal use.

• Make sure you're using the latest version of Cloak (v2.0+)
• Try disabling and re-enabling the extension
• Clear browser cache and cookies for chat.openai.com
• Check if other extensions might be interfering
• Contact us with Debug Mode logs if needed