Skip to content
Docs

Practical notes for using Odexly tools safely.

These docs cover installation expectations, browser limitations, local data, privacy boundaries, and support handoff. Product-specific guides can expand from this base as each extension matures.

Getting started

Install only the tools you need, open each extension from Chrome's toolbar, and check the product page for availability before looking for a Store link.

  • Start from the Products catalog and choose a tool by workflow, not by bundle pressure.
  • Public tools link to the Chrome Web Store; pending tools stay clearly labeled until review is complete.
  • Most settings live inside the extension popup, options page, or browser storage.

Permissions and browser limits

Chrome extensions can only run where Chrome and the target site allow them. Some browser pages and restricted frames are intentionally unavailable.

  • Extensions generally cannot modify Chrome system pages such as chrome:// URLs.
  • Some websites restrict iframes or editor surfaces, so behavior can vary by page.
  • Odexly pages avoid pretending that a browser extension can cover every possible site.

Local data and backup

Odexly tools are designed around local-first workflows where possible. Backup and export behavior depends on the individual extension.

  • Drafts, snippets, rules, notes, block lists, and presets may be stored in browser storage depending on the product.
  • If a product supports JSON import/export, keep your own backup before clearing browser data.
  • Uninstalling an extension or clearing browser storage can remove locally stored data.

Privacy model

Product pages explain what each extension claims today. Privacy-sensitive products should not be treated as perfect security tools.

  • Do not send passwords, API keys, private keys, OTPs, or full payment data through contact forms.
  • Detection-based tools reduce accidents but cannot guarantee that every sensitive value is caught.
  • Paid sync or account features will only be described if they are actually implemented later.

Troubleshooting checklist

When something does not work, collect the product name, Chrome version, page URL pattern, and a short expected-vs-actual description.

  • Check that the extension is enabled and allowed on the current site.
  • Reload the page after installing or changing permissions.
  • If the issue continues, contact support with reproduction steps but without secrets.
Need details?

Use product pages for exact status and privacy notes.

Odexly avoids publishing final install links, screenshots, pricing, or data claims before they are verified for the specific product.

Ask a support question