Nothing. Big Vik Claw does not operate any servers that process your data. All AI model calls go directly from your machine to the provider you configured (Anthropic, OpenAI, DeepSeek, xAI, Ollama). All OAuth tokens and credentials are stored locally in %APPDATA%\BigVik\vault\ on Windows (or the equivalent on macOS/Linux). We have no telemetry, no analytics endpoints, and no "home-call" pings.
When you connect Gmail, Slack, Notion, Figma, Spotify, or any other third-party service via OAuth, Big Vik Claw holds the refresh token locally (encrypted-at-rest via Windows DPAPI / macOS Keychain / Linux secret-service where available). Big Vik Claw uses that token only to make the API calls you direct it to make. The third-party service has its own privacy policy which governs data on their side.
Big Vik Claw offers a 7-day trial, after which an unlock code is required. The unlock code is validated by a public key embedded in the app — your trial and unlock status is computed locally. We do not track trial starts, unlock activations, or app usage.
If you enable the optional Telegram bridge, your messages are sent from your desktop to Telegram's servers to be delivered to Vik (or your configured bot). Telegram's privacy policy applies to message transport. Big Vik Claw stores the bridge configuration (bot token, chat IDs) locally and logs conversation history locally for context continuity. None of this is sent to us.
If the app crashes, details are written to a local log file in %APPDATA%\BigVik\vault\. We do not auto-upload crash reports. If you choose to share a crash log to get help, that is your explicit action.
Big Vik Claw has an opt-in feature to sync usage events to your 1UP Network XP engine (stats.1upnetwork.xyz). It is off by default. Nothing is sent unless you explicitly enable it in Settings.
When enabled, BVC generates an anonymous install UUID (stored locally as xp-sync.json), fetches a JWT tied to that UUID, and sends only the events you've agreed to send. Event types include: app install, daily open, chat message sent, tool invocation, OAuth connector connected, brand card created, scheduled post created, scheduled post fired. No chat contents, no API keys, no file contents, no personally-identifying data leaves your machine — only the event name and a small metadata envelope (e.g. which tool was called).
You can disable XP sync at any time from Settings → 1UP XP Sync. On disable, no further events are sent; previously-recorded events in your xp_ledger remain unless you request deletion via email.
Big Vik Claw is not directed at children under 13 and we do not knowingly collect data from anyone regardless of age (because we do not collect data at all).
If the policy changes, the new version will be posted here with a new effective date. Since we do not collect personal data, there is no data to migrate or notify you about — the update only affects future behavior of the app.
Questions, concerns, or bug reports: officialfizznet@gmail.com