Should you paste your weclapp or Shopify API token into ChatGPT?

The shortcut everyone is tempted by

It usually starts like this: “Here is my weclapp API token, please fetch my open orders.” Or a Shopify Admin API token pasted into a custom GPT, a browser extension or a no-code automation. The AI writes a few lines of code, the data appears, and it feels like magic.

It is worth pausing, because an API token is not a password for reading a report. It is a key that acts as you, often with administrator rights, for as long as it remains valid.

What actually happens to a pasted token

Once a token is in a conversation, it is part of that conversation. In practice, that means:

• It stays in the chat history. Anyone who can open that chat, now or later, can copy it. That includes shared links, team workspaces and synced devices.
• It is processed by the AI provider. Depending on your plan and settings, conversations may be retained or used to improve models. Your token is treated like any other text.
• The AI can repeat it. A model that has seen the token can include it in generated code, summaries or answers you then forward to a colleague or a freelancer.
• It carries the token owner’s full rights. weclapp tokens act as the user who created them. Shopify Admin API tokens carry every scope of their app, which can include customers, orders and refunds.
• It is hard to take back. To be safe, you must create a new token, update every place that used the old one and then revoke it. Most people never do.

The business risk in plain language

Think of an API token as the master key to one of your business systems. Pasting it into a chat is like handing that key to a helpful contractor and letting them keep a copy indefinitely.

The risks are not exotic hacker scenarios. They are ordinary business situations:

• A colleague leaves the company, but still has the old chat containing the key.
• A chat link is shared for a quick question, and the key goes with it.
• The AI “helpfully” runs an update with the token and changes 200 prices because the request was ambiguous. No one checked it first.
• An auditor or customer asks who had access to customer data, and you cannot answer.

Under the GDPR, uncontrolled access to customer data is also a compliance question, not just an IT one.

A safer pattern: keep keys in a vault, not in the conversation

The safe pattern is simple to describe:

1. The key goes into a protected store once, entered by an administrator into a field built for secrets.
2. The AI never receives the key. It asks a trusted service to make a request, and that service adds the credentials.
3. Every request is checked against what the person asking is allowed to do.
4. Changes become proposals that a responsible person approves before they run.
5. Access is managed per person, so removing someone does not require a new key.

How Steward applies that pattern

Steward was built around exactly this approach for weclapp, Shopify and ASA HOTEL:

• Protected fields, encrypted storage. Credentials are entered once in Settings → Connections, stored encrypted and never displayed back, not even to the person who entered them.
• No credentials in AI code. When Steward’s AI writes code to analyze your data, that code runs in an isolated environment without your credentials. Requests to your business tools go through Steward, which adds credentials and enforces permissions.
• Project roles. Viewers follow results, Contributors use configured connections and prepare changes, and Managers approve. Invited project members need no separate connection grant.
• Review before changes. The default Ask for approval mode turns every change into a proposal. Approval rules keep reviews mandatory for selected actions.
• Shopify without long-lived tokens. For Shopify, Steward recommends your own app’s Client ID and secret. Steward exchanges them for short-lived access tokens.
• A shared, reviewable history. Questions, proposals, approvals and results stay in the team’s project.

Pasted token versus Steward

	Token pasted into a chat	Steward connection
Where the key lives	In chat history, possibly shared	Encrypted, never displayed
Does the AI see it?	Yes	No
Whose rights apply	The token owner’s, without limits	Narrowed per person and per project
Before a change	Usually nothing	Proposal and approval by default
When someone leaves	Rotate the token everywhere	Remove their access
Who did what	Hard to reconstruct	Shared history with approvals

Already pasted a token? A short checklist

1. Create a new token in weclapp (personal settings) or rotate the app credentials in Shopify.
2. Revoke the old one once nothing else depends on it.
3. Delete the chats that contain it, including shared links.
4. Check recent changes in the system for anything you did not expect.
5. Connect the system properly, for example in Steward, so that nobody needs the raw token again.

Get started

Read how teams use Steward instead of a do-it-yourself weclapp MCP server, or connect your first tool and ask a question in Read only mode.