Data & Permissions

This page explains what SEOVault AI needs to function, what product permissions are involved, and how those permissions relate to specific features across the Chrome Extension, WordPress connector, and Web App.

SEOVault AI is built for WordPress-focused publishing workflows. Some features work directly inside the browser, some work through the Web App, and some require secure communication with a connected WordPress site.

Each layer has a different role, and each permission exists to support a specific product function.

Product Components

SEOVault AI includes three main components:

• Chrome Extension
• Web App
• WordPress Connector Plugin

These components work together, but they do not all require the same permissions or access.

Chrome Extension

The extension supports in-browser and in-editor workflows such as:

• WordPress side panel access
• draft analysis
• selected text actions
• right-click tools
• screenshot workflows
• note and snippet workflows

Web App

The Web App supports centralized workflows such as:

• multi-site management
• post loading and editing
• draft history
• team workspace
• internal linking and autolinking
• save-to-WordPress actions

WordPress Connector Plugin

The connector plugin provides the secure communication layer between the Web App and a connected WordPress website.

It exists so the Web App can:

• connect to a WordPress site
• load posts
• save content back to WordPress
• support site-specific workflows from a central workspace

Why Permissions Exist

Permissions are required because the product interacts with:

• browser features
• WordPress admin and editor environments
• selected page content
• screenshots and clipboard workflows
• account-based cloud services
• connected WordPress websites

Without the required permissions, key features would not work.

SEOVault AI uses permissions to support product functionality, not to request unrelated access.

Chrome Extension Permissions

The Chrome Extension may require browser permissions so it can function as a publishing assistant inside WordPress and across selected browser workflows.

Side Panel Access

Used to open and run the SEOVault AI panel inside supported editing workflows.

Supports:

• side panel interface inside WordPress
• in-editor SEO and writing assistance
• extension-based workflow access while editing

Page Access on Supported Sites

Used so the extension can work on supported WordPress pages and respond to the editing environment.

Supports:

• draft analysis
• document outline features
• field interaction
• content injection where supported
• selected-text workflows inside the editor

Context Menu Access

Used for right-click actions.

Supports:

• Save to SEO Snippets
• Capture Screenshot
• text-based quick actions
• page-level workflow shortcuts

Selected Text / Page Interaction

Used when a feature depends on user-highlighted content.

Supports:

• AI Humanizer on selected text
• citation and link workflows
• selected-text analysis
• snippet saving
• table and formatting workflows based on selected content

Screenshot / Capture Access

Used for browser-based screenshot workflows.

Supports:

• screenshot capture on user request
• 1200x628 screenshot workflow
• fast visual content capture for publishing use

Clipboard Support

Used where copy-based workflows are part of the product flow.

Supports:

• copy-to-clipboard screenshot behavior
• faster transfer of generated or captured output into a post

Storage Access

Used to keep extension settings and local workflow preferences available.

Supports:

• interface preferences
• local settings persistence
• theme choices such as light or dark mode

Account / Session Access

Used to connect the extension to the user’s SEOVault AI account.

Supports:

• login state
• premium feature access
• authenticated use of account-based tools

Service Communication

Used when the extension runs features powered by SEOVault AI services.

Supports:

• AI generation
• deep analysis workflows
• cloud-backed writing and optimization features

WordPress Connector Plugin Permissions

The WordPress connector plugin exists to support communication between the Web App and a connected WordPress website.

It is a lightweight connector. It is not designed to be a bloated all-in-one SEO feature plugin.

What the connector is used for

The connector supports:

• site connection
• post loading into the Web App
• save-to-WordPress actions
• site-level workflow communication
• multi-site operations through the Web App

Why the connector is needed

The Web App runs outside the native WordPress admin screen. Because of that, it needs a secure communication layer to work with a WordPress site.

Without the connector, the Web App cannot function as a centralized WordPress workspace.

What the connector does not replace

The connector does not replace:

• the WordPress editor
• the Chrome Extension
• standard site administration
• the broader publishing workflow inside WordPress

Its role is connection and communication.

Web App Access and Permissions

The Web App uses account-level and connected-site access to provide centralized workflows.

It does not use browser-extension permissions in the same way the extension does. Its permission model is tied more directly to:

• authenticated account access
• connected WordPress site access
• team and workspace permissions
• feature-level workflows inside the application

Web App access supports

• connecting sites
• loading posts from connected sites
• editing content in the workspace
• saving drafts back to WordPress
• internal linking and autolinking workflows
• team workspace actions
• draft history and cloud saves

Team and Workspace Permissions

Inside the Web App, workspace access can also be role-based.

Depending on the workspace configuration, different users may have different levels of access such as:

• owner
• admin
• editor
• viewer

These roles help control who can manage the workspace and who can participate in content workflows.

Role-based access supports:

• cleaner collaboration
• clearer responsibilities
• safer multi-user workflows
• controlled access across content operations

What Data Access Supports in Practice

The product’s access and permissions are tied to visible features.

If a user opens the extension in WordPress

The extension needs enough access to:

• recognize the page context
• display the side panel
• analyze the draft
• interact with selected content where supported

If a user uses right-click tools

The extension needs context-menu and related interaction permissions.

If a user captures a screenshot

The extension needs capture-related access to complete that request.

If a user connects a site in the Web App

The WordPress connector plugin is required so the Web App can communicate with that site.

If a user saves content back to WordPress

The Web App needs an active connected-site context through the connector plugin.

If a team uses the Web App together

Workspace roles control who can access and manage shared workflows.

Product Access by Workflow

Extension-only workflows

These rely mainly on browser permissions.

Examples:

• side panel access
• selected-text tools
• right-click actions
• screenshot workflows
• SEO Snippets
• in-editor assistance

Web App-only workflows

These rely mainly on authenticated account access and connected-site access.

Examples:

• multi-site management
• team workspace
• draft history
• centralized post editing
• advanced internal linking
• autolinking

Connector-dependent workflows

These rely on the WordPress connector plugin.

Examples:

• connecting a site to the Web App
• loading site content into the Web App
• save-to-WordPress actions
• central workspace communication with WordPress

What Permissions Are For

Permissions exist to support product features.

They are used so SEOVault AI can:

• function inside the WordPress editor
• respond to user-selected content
• run right-click browser tools
• capture screenshots when requested
• persist settings
• authenticate accounts
• connect Web App workflows to WordPress sites
• support team and multi-site operations

Each permission category maps to a real workflow in the product.

What Permissions Are Not For

Permissions are not intended for unrelated access or feature use outside the product workflow.

SEOVault AI is built around a WordPress publishing workflow. Its permissions are tied to that publishing environment, its browser utilities, and its connected-site features.

Product Transparency

The Data & Permissions model should remain aligned across:

• the extension’s real permission set
• the published Chrome Web Store listing
• the Privacy Policy
• the WordPress connector documentation
• the public product documentation

This keeps the product easier to understand and easier to trust.

Summary

SEOVault AI uses permissions across three layers:

• Chrome Extension permissions for browser-based and in-editor workflows
• WordPress connector access for secure Web App to WordPress communication
• Web App account and workspace access for centralized publishing, multi-site, and team workflows

Each permission exists to support a specific feature path inside the product.

Related Documentation

• Install the Chrome Extension
• Extension Permissions: What SEOVault AI Needs and Why
• Connect Your First WordPress Site
• Extension vs Web App: Which Workflow Should You Use?
• Team Workspace Guide