Skip to content
Odexly
Products
All docs
PasteGuard extension iconProduct docs

PasteGuard

Sensitive data warnings before risky sharing.

Pending reviewPrivacy shieldLocal-firstPro roadmap
Safe setup notes

Install only after checking the current product status.

These docs combine product-page data with refined overview guidance so the setup notes stay clear, professional, and easy to scan. Use the product page as the source of truth for screenshots, availability, and Chrome Web Store status.

Product page
Extension overview

What this extension helps you do.

PasteGuard is a privacy-oriented warning layer for moments when sensitive text may be typed, pasted, or prepared inside browser input fields.

It helps users notice possible secrets, credentials, personal identifiers, verification codes, wallet-related data, banking patterns, and other high-risk text before it is shared by accident.

Core capabilities

  • Detect patterns commonly associated with API keys, access tokens, private keys, passwords, OTP-like codes, recovery phrases, wallet data, banking patterns, phone numbers, and personal identifiers.
  • Surface clear risk labels and short explanations instead of overwhelming the user with technical detail.
  • Support developer workflows involving environment variables, credentials, tokens, and project secrets.
  • Support everyday privacy situations such as phone numbers, payment-related patterns, verification codes, and private notes.
  • Keep the warning experience calm, readable, and focused on helping the user pause before sharing risky text.

Practical workflows

  • Review copied text before sending it into forms, messages, support replies, or web tools.
  • Catch obvious high-risk strings before they leave the browser field.
  • Build a habit of checking sensitive text during fast copy-paste workflows.

Install and first use

  1. 1Write or paste as usual: Use normal browser text fields, editors, forms, and message boxes.
  2. 2PasteGuard reviews risky patterns: When text looks sensitive, the extension raises a clear warning instead of silently letting the mistake pass unnoticed.
  3. 3Decide before sharing: Review the reason, remove or redact the risky content, then continue only when the text is safe to send.

Privacy and data handling

  • Designed as a local-first safety layer
  • No backend is required for the core warning workflow
  • No raw secrets should be stored as product data
  • Warnings are intended to create user awareness before sharing

Troubleshooting

  • Confirm the extension is enabled in Chrome and allowed on the current site.
  • Reload the page after changing extension permissions or settings.
  • When contacting support, include the product name, Chrome version, expected behavior, and actual behavior. Do not send secrets.

Common use cases

Avoid pasting API keys into AI chatsCatch OTP codes before sending messagesNotice wallet or recovery phrase patternsReduce accidental sharing of phone or bank-related numbersReview support replies that may contain customer dataDouble-check developer docs and bug reports

Good to know

  • Chrome Web Store review is pending. A public install link should be added only after the listing is live.