Permissions and safety
What Queek OS can see, what it can change, and how access is limited and revoked.
Queek OS is built so that connecting an AI app never gives it more power over your store than you have yourself — and usually less.
One store, one person
- A connection is bound to the single store you chose when you signed in. It cannot see or change any other store, even one your account also manages.
- It acts as you. Every action runs with your own Queek role: if your account cannot delete products or see payouts in the dashboard, Queek OS cannot either.
- On Claude Team or Enterprise, each member signs in with their own Queek account, so each person's connection carries only their own permissions.
Two levels of access
When you connect, you choose one of two levels:
| Read only | Allow changes to my store | |
|---|---|---|
| See products, collections, orders, customers, pages and analytics | Yes | Yes |
| Create and change products, collections, coupons, pages, posts, SEO and theme | No | Yes |
To change the level, disconnect and connect again. The full list of tools, with the access each needs, is on What Queek OS can do.
Built-in safeguards
- Products start as drafts. Every product Queek OS creates is unpublished.
Publishing is a separate step that only happens when you ask for it.
Products brought in with
import_productsare drafts too, and publishing an import stops and asks you to confirm first. - Permanent actions ask first. Deleting a product, collection, page, post, shipping zone, custom field or content type, switching theme, and rebuilding a page from the theme all stop and ask you to confirm in the chat before they run.
- Coupons are never deleted — only deactivated, so order history stays intact.
- Orders are read-only. Queek OS can look up any order, but cannot change its status, payment or items.
- Photos only come from you. Queek OS saves a photo only when you attach it in
the chat (in Claude, through a one-time upload link) or give it a public
httpslink. It will not fetch from private or internal network addresses. A photo it saves from the chat or a link is stored in a web format (turned upright from its camera orientation) with resized copies; Queek OS does not enhance or retouch photos. - Customer data comes a page at a time. Customer and invoice lists are searched and paginated; there is no bulk export.
What Queek OS cannot do
It has no payout, billing, subscription or refund actions, no way to change bank details, and no tools for domains, inviting or removing staff, or changing an order's status, payment or items. Those stay in the Queek dashboard. The one payout-related thing it can do is read settlement reports in analytics: read-only, and only for an account whose role includes the payouts permission.
Your data and your AI app
When you ask a question, Queek OS sends the answer — for example, your order list — to the AI app you are using, which processes it under that provider's own terms. Queek handles your store data under the Queek privacy policy. Only connect Queek OS to an AI account you trust with your store's information.
Revoking access
Open your Queek dashboard → Settings → Connections and choose Revoke on the Claude or ChatGPT connection. Access ends immediately. You can revoke your own connections; the store owner or an admin can revoke anyone's — useful when a staff member leaves.