Data Reference
Every Klaviyo endpoint Nux reads, the scope it needs, and what Nux never does.
Which way data flows
One direction only: Klaviyo → Nux → your chat. Nux reads your connected Klaviyo account and formats what it finds into a Telegram or LINE reply. It sends nothing back into Klaviyo, which is why it creates no metrics, no profiles and no branded events — there is no write path in the code for it to use.
Endpoints and scopes
Connecting Nux grants eight read-only OAuth scopes: accounts:read, campaigns:read, profiles:read, events:read, lists:read, metrics:read, flows:read and segments:read. The table below lists every Klaviyo endpoint Nux calls and the scope each one needs.
| Endpoint | Scope | Why Nux calls it |
|---|---|---|
| /api/campaign-values-reports | campaigns:read | Per-campaign performance statistics |
| /api/campaigns | campaigns:read | List and search sent campaigns |
| /api/events | events:read | Recent events for a looked-up profile |
| /api/flow-values-reports | flows:read | Per-flow performance statistics |
| /api/flows | flows:read | List and search flows |
| /api/lists | lists:read | List names and member counts |
| /api/metric-aggregates | metrics:read | Opens, clicks, bounces, spam, revenue per campaign |
| /api/metrics | metrics:read | Resolve metric names to IDs |
| /api/profiles | profiles:read | Look up one profile by email |
| /api/segments | segments:read | Segment names and member counts |
What Nux stores
Your encrypted OAuth tokens, your preferences (default metric, timeframe, alert thresholds, digest time and timezone), a rolling per-campaign baseline used for deviation alerts, and usage analytics (which commands ran, when, and on which platform). See Privacy Policy for the full account, including what each of these is used for and how long it's kept.
What Nux never does
No writes to your Klaviyo account — no campaigns, no flows, no metrics, no profiles, no list or segment changes. No exports of your data anywhere. No customer PII beyond what a single /profile lookup displays, live, to the person who asked for it — it is never written to disk.
Deleting your data
Run /disconnect on Telegram or send disconnect on LINE. This deletes your stored OAuth tokens, drops the in-memory Klaviyo caches kept for your account, clears recent chat history, and revokes the grant at Klaviyo — all in the same step. Your preferences (default metric, timeframe, alert thresholds, digest time, timezone) and the per-campaign alert baseline Nux has calculated from your Klaviyo history are kept, not deleted: reconnecting is almost always reconnecting the same account, and starting over on settings and alert history is not what most people who disconnect and reconnect want. See Privacy Policy for what to do if you want those removed too.