Skip to main content
A connector that can read your customer list deserves a straight answer about what happens to that data. Everything below is how the connector works, not policy language.

​
The controls

​
Changes need your confirmation

All seven tools that change something work in two steps:
  1. Preview. The AI’s first call changes nothing. It returns a summary of exactly what would change, any warnings (for example, turning off a channel or adding new report recipients), and a one-time confirmation ticket — or a refusal with the reason.
  2. You confirm in the chat. The AI shows you the summary. Only when you say yes does it call the tool again with the ticket, and the change is made.
The ticket lasts 5 minutes, works once, and is tied to that tool, your store and the exact same arguments. If anything about the request changes, the ticket no longer fits and the AI has to preview again. A Read only token can never change anything at all.

​
Change tools with extra limits

  • Test sends go only to your store’s own addresses — staff accounts, report recipients and sign-up alert recipients — and at most 20 an hour. They are real sends and use your allowance.
  • CSV export links work for anyone who has the link, for 24 hours. Treat one like the file itself: don’t paste it anywhere you wouldn’t paste the CSV.
  • Unsubscribing a customer can’t be undone from the connector.

​
What leaves your store

Only what a tool returns, only to the AI client you connected, only when it calls a tool. Your AI provider’s own data handling then applies to that conversation. If that matters for your customers’ data:
  • Grant tools narrowly.
  • Prefer aggregate reports (get_analytics) over per-person lookups (get_entity_details).
  • Remember that a chat transcript is a copy of whatever was returned into it.

​
How to switch it off, fastest first

​
Good token hygiene

  • One token per client, named after the client.
  • Read only unless that client genuinely needs to change something.
  • An expiry for anything temporary — agencies, contractors, experiments.
  • Check Last used occasionally and revoke what has gone quiet.
  • Never paste a token into a chat, a shared doc, a ticket or a screenshot.
If a token leaks, press Regenerate rather than deleting and starting over. It stops the old secret at once and keeps the token’s name, tools and expiry, so the legitimate client is back in one paste.

​
Privacy policy

Notifylyst’s full privacy policy and data-retention terms are published on the Shopify app listing and inside the app. This page does not restate them, so there is only ever one authoritative copy.

​
Next

Troubleshooting — symptom, cause, fix.