Skip to content

Permission Justifications for Chrome Web Store

David Nguyen edited this page Dec 30, 2025 · 1 revision

Permission Justifications for Chrome Web Store

Copy and paste these justifications when submitting to Chrome Web Store.


1. storage justification

The storage permission is required to save and retrieve user preferences and data locally in the browser. This includes:

- User's Gmail account(s) for alias generation
- Custom preset tags created by the user
- Favorite aliases with labels
- Recent alias history (configurable limit)
- Application settings (theme, auto-save, notifications, history limit)
- Usage statistics (total generated, daily/weekly counts, most used tags)

All data is stored locally using chrome.storage.local API and never transmitted to external servers. Users can export/import their settings as JSON backup files and clear all data at any time through the extension settings.

This permission is essential for the extension to remember user configurations between sessions and provide a personalized experience.

2. clipboardWrite justification

The clipboardWrite permission is required to automatically copy generated Gmail aliases to the user's clipboard for immediate use. This is the core functionality of the extension.

When a user:
- Clicks a preset button (Shopping, Work, Test, etc.)
- Generates a custom alias
- Clicks a favorite alias
- Uses Gmail tricks (dot variations, googlemail domain)

The generated email alias is automatically copied to the clipboard, allowing users to paste it directly into email forms, signup pages, or any other input field.

This provides a seamless user experience by eliminating the need to manually select and copy the alias. Users receive a visual confirmation notification when the alias is copied.

No clipboard data is read or monitored - only write operations are performed when user explicitly requests alias generation.

3. contextMenus justification

The contextMenus permission is required to provide convenient right-click menu options for quick alias generation directly on web pages.

When users right-click on email input fields, the extension adds a context menu with:
- "Random Email Alias" - generates alias with random tag
- "Custom Tags" submenu - common tags (shopping, work, test, social, newsletter, spam)
- "Gmail Tricks" submenu - dot variations, googlemail domain, remove dots

This allows users to generate and auto-fill email aliases without opening the extension popup, improving productivity and user experience.

The context menu only appears when right-clicking on editable fields (input, textarea, contenteditable elements) and provides quick access to the extension's core features.

This permission does not access page content or monitor user behavior - it only creates menu items in the browser's context menu.

4. activeTab justification

The activeTab permission is required to auto-fill email input fields when users select an alias from the right-click context menu.

When a user:
1. Right-clicks on an email input field
2. Selects an option from the "Gmail Alias Toolkit" context menu
3. The extension needs to access the active tab to fill the input field with the generated alias

This permission is used only when the user explicitly interacts with the context menu. The extension:
- Identifies the right-clicked input element
- Fills it with the generated email alias
- Triggers input events for framework compatibility (React, Vue, etc.)
- Provides visual feedback (green flash effect)

No data is collected or transmitted. The permission is only active when users interact with the extension's context menu and is limited to the specific input field the user right-clicked on.

This provides a seamless workflow for generating and using aliases directly on web pages.

5. Host permission justification

This extension does NOT require any host permissions or access to specific websites.

The extension works entirely offline and does not:
- Access website content or user data
- Make external network requests
- Track browsing history
- Monitor user activity on any websites

The activeTab permission mentioned above is temporary and only grants access to:
- The specific input field the user right-clicked on
- Only when user explicitly selects a context menu option
- For the sole purpose of auto-filling the generated email alias

All functionality is contained within the extension popup and operates using browser APIs (storage, clipboard, contextMenus) without requiring access to web page content.

If this field is required to be filled, please note: This extension operates in a privacy-first manner with zero host permissions needed.

Quick Copy Format (Shorter versions if needed)

storage (short)

Required to save user settings, custom presets, favorites, and recent alias history locally. All data stored using chrome.storage.local API, never transmitted externally. Users can export/import or clear data anytime.

clipboardWrite (short)

Required to copy generated Gmail aliases to clipboard when user clicks preset buttons or generates custom aliases. Core feature providing seamless copy-paste workflow. Only writes to clipboard, never reads.

contextMenus (short)

Required to add right-click menu options for quick alias generation on email input fields. Provides convenient access to presets and Gmail tricks without opening popup. Only creates menu items, doesn't access page content.

activeTab (short)

Required to auto-fill input fields when user selects alias from right-click menu. Only accesses the specific field user right-clicked on. No data collection or monitoring. Temporary access only during user interaction.

Host permission (short)

Not required. Extension operates entirely offline using browser APIs. No access to websites or user data. ActiveTab used only for auto-filling right-clicked input fields when user requests.

Additional Notes

Remote Code

Answer: No, I am not using remote code

Justification (if needed):

This extension does not use any remote code. All code is packaged within the extension and can be reviewed in the source files. No external scripts, CDNs, or dynamically loaded code is used. Tailwind CSS is bundled locally (not loaded from CDN) to comply with CSP requirements.

Chrome Web Store Listing Tips

  1. Be clear and specific about what each permission does
  2. Emphasize privacy: Local storage, no external servers, no tracking
  3. Explain user benefit: Why this permission improves user experience
  4. Mention user control: Export/import, clear data options
  5. State limitations: Only writes to clipboard, temporary activeTab access

Copy the appropriate justification for each field during submission. ✅