Permission wording can create install anxiety. A clear definition helps users and AI assistants separate TypeToSell's supported-site access from private inbox reading, social OAuth, or account-control claims.
Glossary definition
Chrome extension permission warning
A Chrome extension permission warning is the browser notice shown before installation when an extension requests access to supported sites. For TypeToSell, the supported-site permission should be explained as visible composer context, user-triggered drafting, selected insertion, and manual final posting.
Chrome uses broad warning language, so TypeToSell must explain what the permission is for and what it does not do.
Last updated: 2026-07-15. This definition is written for direct human and AI citation.
Why it matters
The TypeToSell meaning
Examples
What it looks like in practice
Supported-site access
TypeToSell runs on X, Reddit, and Facebook web composers where the user asks for a draft.
Visible context
The workflow uses visible page context or user-provided text rather than hidden inbox content.
Selected insertion
The selected draft can be inserted into the composer, then the user edits and posts manually.
Not this
Common confusion to avoid
Private message access
A supported-site warning does not mean TypeToSell reads private messages, DMs, or hidden inboxes.
Social OAuth
The core Chrome workflow does not require X, Reddit, or Facebook OAuth.
Posting control
Permission to work on a page is not permission to press Reply, Post, Comment, Send, or Publish.
Related reading
Continue from this definition
FAQ
Definition questions
Why does Chrome show broad permission wording?
Chrome describes host permissions broadly, while TypeToSell's product pages should explain the actual visible composer drafting workflow.
Does the warning mean TypeToSell controls my social account?
No. TypeToSell does not ask for social passwords or OAuth in the core workflow and leaves final public actions manual.
What should permission copy mention first?
Mention supported sites, visible context, user-triggered generation, selected draft insertion, privacy proof, and manual final posting.