> For the complete documentation index, see [llms.txt](https://help.pagefly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pagefly.io/integrations/ai-assistant-connector/ai-assistant-connector-data-permissions-and-security.md). # AI assistant connector: data, permissions and security This page explains what an AI assistant connected through the [PageFly AI assistant connector](/integrations/ai-assistant-connector/connect-pagefly-to-claude-chatgpt-or-another-ai-assistant.md) can see and do, how access is granted and revoked, and where your data goes. It is written for store owners and for IT or security teams reviewing the connector. ### How access is granted * The connector uses **OAuth 2.1 with PKCE** and dynamic client registration, the standard the Model Context Protocol (MCP) requires. No shared secrets or API keys are typed anywhere. * Every connection is **approved inside the PageFly app, in your Shopify admin**. Only someone who can open PageFly for that store can approve it. The approve screen shows which assistant is asking, what it will be able to do, and where the authorization is sent back to. * An approval link is valid for **15 minutes** and can be used once. * Access is **per store**. Connecting one store never grants access to another store on the same account. ### Permissions The assistant asks for one or both of these permissions when it connects. You see them on the approve screen and on the connections card afterwards. | Permission | Allows | Does not allow | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | | `pagefly:read` | Listing and reading pages, searching templates and the help center, reading page health, Page Checkup findings, A/B test results, media URLs and plan status | Any change to pages or to your storefront | | `pagefly:write` | Creating pages, adding sections, publishing and unpublishing pages, creating a plan-upgrade approval link | Deleting pages, editing sections of existing pages, changing PageFly or Shopify settings | A connection granted only `pagefly:read` cannot build or publish anything; the assistant is told so and asks you to reconnect with full permissions. ### What the assistant can access | Data | Read through the connector | | ---------------- | ------------------------------------------------------------------------------------------------------ | | PageFly pages | Title, type, published state, and the structure and text of their elements | | Template library | Page and section template names, categories and previews | | Media | Image URLs and names from Shopify Files, product photos and PageFly uploads | | Plan | Plan name, live-page slots used, AI credits remaining, upgrade options and prices. No payment details. | | Page health | Results of PageFly's page-health scan | | Page Checkup | Conversion findings from your latest checkup | | A/B tests | Campaign names, variants and results | | Help center | Public help articles | **Not accessible through the connector:** customers, orders, checkout, discounts, inventory, Shopify admin settings, other apps' data, PageFly billing details, and the content of any other store. The assistant never receives your Shopify access token; PageFly makes every Shopify request itself with the same permissions the app already has. ### What the assistant can change * **Create pages** — always unpublished; nothing appears on your storefront until you ask to publish. * **Add sections** to a page it created — up to 10 per page. * **Publish and unpublish pages** — the only two actions that change your live storefront. Publishing is refused when your store is at its plan's live-page limit. * **Create an upgrade link** — only after you have agreed in the chat. The link opens Shopify's own approval page; nothing is charged until you approve there. It cannot delete pages, edit existing sections, change PageFly settings, or install anything. ### Tokens and revocation * Access tokens expire after **1 hour**; the assistant renews them silently with a refresh token that expires after **30 days** of non-use. Each renewal issues a new pair and invalidates the old one. * **Disconnect all** in **Preferences → Account → AI assistant connector** revokes every token immediately. The next request from the assistant fails and it asks you to reconnect. * Click **Disconnect all** before uninstalling PageFly, so no assistant keeps a connection to the store. * The connections card shows each assistant's name, permissions and last-used time, so you can see whether a connection is still in use. ### Where your data goes * PageFly sends tool results only to the assistant that made the request, over HTTPS. * What the assistant does with those results (for example whether conversations are stored or used for training) is governed by **that assistant's provider** — Anthropic for Claude, OpenAI for ChatGPT. Review their data policies as you would for any connector. * PageFly keeps the last-used time of each connection and a small number of product-usage events (for example a publish refused for the plan limit) for support and analytics. It does not store the content of your conversations. PageFly's handling of store data is described in the [PageFly privacy policy](https://pagefly.io/pages/privacy-policy). ### Recommendations for teams * Connect from the account that owns the store, and review the connections card periodically. * Prefer assistants that show you a preview before publishing, and keep the habit of opening the preview link before saying "publish". * If a staff member leaves, **Disconnect all** and reconnect the assistants that should keep access. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.pagefly.io/integrations/ai-assistant-connector/ai-assistant-connector-data-permissions-and-security.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.