Privacy Policy
What Nux stores, what it never stores, and how to delete all of it in one message.
1. Overview
Nux is a Klaviyo analytics bot for Telegram and LINE. This policy explains what data is collected, how it is used, and how you can delete it. Questions go to support@thenux.app.
2. What is collected
- Your Telegram or LINE user ID, to recognise you across sessions.
- Your Klaviyo OAuth access and refresh tokens, encrypted at rest with Fernet (AES-256-CBC plus HMAC-SHA256) before they are written to disk.
- Your preferences: default timeframe, conversion metric, alert thresholds, digest time and timezone.
- A per-campaign alert baseline, calculated from your Klaviyo campaign performance and used to detect an unusual deviation worth alerting you about.
3. What is never collected
- No Klaviyo profile data. Emails, phone numbers and purchase history are fetched live, used to format your reply, and discarded. None of it is written to disk.
- No message content from your chats is retained.
- No advertising identifiers, device fingerprints or behavioural tracking of any kind.
4. Token storage
Tokens live in a SQLite database on a private Railway volume. They are encrypted before being written, and the encryption key is an environment variable that never touches disk. The short-lived oauth_state rows used during authorisation expire after 10 minutes.
5. Retention
Running /disconnect on Telegram or sending disconnect on LINE deletes your stored OAuth tokens permanently, drops the in-memory Klaviyo caches kept for your account, and clears your recent chat history. Nux also calls Klaviyo's token revocation endpoint at the same time, so the token stops working server-side too. There is no retention period and no grace window on any of this — it happens in the same step as the command.
Your preferences (default metric, timeframe, alert thresholds, digest time, timezone) and the per-campaign alert baseline Nux calculates from your Klaviyo campaign history are not deleted by disconnecting. They are kept deliberately: reconnecting a Klaviyo account is almost always reconnecting the same account, and losing your configured thresholds and alert history on every reconnect would be worse for most people than keeping them. Deleting these too takes a manual request — email support@thenux.app — since there is no in-product control for it today.
6. Third parties
- Klaviyo. Tokens are exchanged with a.klaviyo.com. Klaviyo's own privacy policy governs what Klaviyo retains.
- Anthropic. If you use /chat, your query text is sent to the Claude API. This feature is optional and requires a key configured by the operator.
- Telegram and LINE. Message delivery is handled by these platforms. Nux does not control metadata beyond what their bot APIs expose.
- Sentry. Application errors are reported to sentry.io so faults get noticed and fixed. A report can include your Telegram or LINE user ID and, when a lookup fails, the email address that was searched for. It never includes your Klaviyo tokens. Active only when the operator configures it.
- Railway and Cloudflare. The bot and its database run on Railway. Nightly encrypted-at-rest database backups are copied to Cloudflare R2.
7. Security
Tokens are encrypted before storage, the database sits on a private volume, and no Klaviyo data is reachable through any public endpoint.
8. Changes
The date above reflects any change to this policy. Continued use after a change constitutes acceptance.