AI connectors privacy notice

This notice supplements the Queek Privacy Policy and applies when a merchant connects their Queek store to an AI assistant such as ChatGPT (OpenAI) or Claude (Anthropic) through Queek's merchant connector. Everything in the main Privacy Policy continues to apply; this page only describes what is different when a store is managed through an AI assistant.

Queekx Technology Limited ('Queek', 'we', 'us') operates the connector. It lets a merchant manage their own store from a chat conversation, in place of the Queek merchant dashboard, using the merchant's existing Queek account.

For the merchant's own account data, Queek is the data controller. For the customer records that belong to a merchant's store, the merchant is the data controller and Queek acts as a data processor on the merchant's instructions, in the same way as for connected messaging channels.

Once a merchant connects a store and grants access, the assistant can read and, only if the merchant also grants write access, change the following for that one store:

Store profile: name, slogan, description, support contact, address and opening hours.

Catalogue: products, prices, stock, descriptions, images, collections and coupons.

Orders: order number, status, items, payment method or channel, and delivery or rider assignment, for orders belonging to that store only.

Customers: names, phone numbers and emails as they appear on that store's own order and customer records. Never a cross-store or platform-wide customer list.

Content: storefront pages, blog posts, SEO settings and theme settings.

Shipping: the store's shipping zones and rates.

Team (read-only): staff names and roles on that store. The connector cannot change team membership or permissions.

The connector never accesses payment card numbers, bank account details, wallet balances, or government identity documents. It has no tool for payments, refunds or money movement. Where the merchant's own account holds the payouts permission, the analytics report can return settlement figures (pending settlement, total paid in the period and balance mode); without that permission those figures are refused.

The connector never asks for, receives or stores the merchant's password or one-time codes. Sign-in happens on Queek's own pages and the assistant only ever holds an authorisation token that the merchant can revoke.

Each request returns only the data needed to answer it. The connector does not read the rest of the conversation and does not receive anything the merchant has not asked it to act on.

When the assistant carries out a request, the results of that request are returned into the conversation so the assistant can answer or complete the action. This is the only way store data reaches the AI provider, and it happens only in response to the merchant's own request in that conversation.

Queek does not send store data to OpenAI, Anthropic or any other AI provider for training, analytics or any purpose other than completing the merchant's request.

Queek does not control how the AI provider retains conversation content. That is governed by the provider's own privacy policy and the merchant's settings in ChatGPT or Claude.

The AI provider hosting the conversation (OpenAI for ChatGPT, Anthropic for Claude), as the processor passing the merchant's requests to the connector.

Queek's own platform, which is the system of record for the store. The connector is a pass-through and does not keep a second copy of store, order or customer data.

No other third party receives data through the connector.

Queek's platform and the connector are hosted on servers in Frankfurt, Germany, in the European Union.

The AI provider processes the conversation, including any store data returned into it, in the locations described in its own privacy policy. For OpenAI and Anthropic this includes the United States.

Queek is established in Nigeria. By connecting an AI assistant the merchant instructs Queek to make the store data described above available to that provider for the purpose of the merchant's own requests.

The connector does not keep its own copy of store, order or customer data. Every request is served live from the Queek platform.

The connector holds the authorisation material for the connection itself: the access and refresh tokens issued when the merchant connected, and the registration record of the AI client. This material is encrypted at rest and scoped to the connector.

Tokens are revoked through disconnect, revocation or rotation, and unusable token records are removed or expire under token lifetimes. The AI client's registration record has no automatic expiry and remains until removed by Queek, including after disconnect; removal can be requested at the privacy contact below.

Store, order and customer data is retained according to the Data Retention section of the Queek Privacy Policy. Connecting an AI assistant does not change those periods or create any new retention.

Token records are retained for the life of the connection; on disconnect or revocation, tokens are revoked and unusable token records are removed or expire under token lifetimes. The AI client's registration record has no automatic expiry and is kept until removed by Queek; removal can be requested at the privacy contact below.

At connection time the merchant chooses which one store the assistant may manage and whether it gets read-only access or read and write access.

The merchant can disconnect at any time from the Queek merchant dashboard or from the assistant's own connected-apps settings. Disconnecting stops further requests; a call already in flight or served from a short-lived cache may still complete.

Deleting a product, collection, page, post, shipping zone, custom field, content type or content entry, or switching the store's theme, requires the merchant's explicit confirmation in the chat before it takes effect, through a server confirmation step. The assistant cannot approve these on the merchant's behalf. Other edits, such as updating product details, apply without that confirmation step. New products need no separate confirmation before creation: they are created immediately as unpublished drafts, and are published only on the merchant's explicit instruction (or previewed first where the merchant asks for that).

Merchants keep every right described in the Your Rights section of the Queek Privacy Policy: to access, correct, erase and restrict the processing of their personal data. Connecting an AI assistant does not change these rights.

To exercise them, or to request deletion of the connection's authorisation material, email [email protected]. Account and data deletion requests follow the process at usequeek.com/data-deletion and are actioned within 30 days, subject to legal retention obligations.

Customers of a merchant's store should direct requests about their own data to that merchant, who can raise them with Queek.

The connector is a business tool for merchants operating a Queek store. It is not directed at, and is not intended for use by, anyone under 18 in a personal capacity.

It does not knowingly collect data about end customers under 13 for any purpose beyond the store's own order and customer records described above.

This notice is governed by the laws of the Federal Republic of Nigeria, including the Nigeria Data Protection Act 2023 (NDPA), in the same way as the Queek Privacy Policy.