← Back to Jarvis
PRIVACY / PUBLIC INFO

Jarvis privacy overview.

This page describes the current technical behavior of the Jarvis showcase website. It is not a substitute for professional legal advice about the operator's specific situation.
PROJECT STATUSFree Early Access — no purchases or payments are offered on this website.PUBLIC INFO UPDATEDNot set

Website analytics

The Jarvis website keeps aggregate visit statistics. The web server converts the connecting network address into a one-way SHA-256-derived visitor key before it is stored for visitor counting. Visitor keys are removed after 90 days. The public site does not intentionally use advertising pixels or marketing cookies.

Cloudflare

The public domain may be delivered through Cloudflare services such as DNS, HTTPS and Cloudflare Tunnel. Cloudflare therefore processes network and security information as part of delivering the site.

Discord bot data

When you use Jarvis inside Discord, the bot may store the information required for the feature you use, such as server configuration, tickets, command statistics, economy progress, Early Access records, giveaways, activity settings or other bot state.

AI and voice

AI or spoken-assistant features can send user-provided content to the configured AI service when those features are used. Voice conversation processing is designed to require consent where the Jarvis voice receiver is used.

Companion chat and Discord messages

Companion uses your Discord sign-in to identify your own account. Recent chat context is held in server memory for up to 15 minutes of inactivity; use “Clear chat” to clear it sooner. Extended AI sends your prompt and recent context to the configured AI provider. Basic scripted replies do not call that provider. Jarvis is an AI assistant, not a therapist or emergency service.

Private messages sent to the Jarvis Discord bot, and replies sent through it, can be stored in its inbox and read by authorised owners. Website Companion chats are separate from this Discord inbox. Never share passwords, bot tokens or private panel keys in chat.

Relationships and desktop licences

Optional virtual relationships store Discord user IDs, consent, status and dates. Proposals expire; either partner can end an accepted relationship.

Personal licences store the assigned and activating Discord account, issue/activation/reset dates, status, a verification hash of the code, a hashed device identifier and a public signing key. Raw Windows MachineGuid values and raw licence codes are not stored on the server. The app protects its private device key using Windows account encryption. Recovery requires the same Discord account and saved code, once per 24 hours.

Owners see licence records and recent use/reset/revocation history. Records are retained for licence operation and support, with a bounded audit history. Contact Jarvis Support to request review or deletion; deleting licence/account data may prevent continued access. Discord, hosting and configured AI providers also process data under their policies.

Early Access and future pricing

The app is free during Early Access. Planned prices appear on the pricing page and can change before launch; no checkout or payment collection is enabled here. Monthly features remain separate and expire independently. Keep your code safely: it is shown only when issued or replaced. Future purchase terms must preserve applicable statutory consumer rights.

Contact

Discord@jarvisbotsupport

Only public contact details that you intentionally configure are shown here. The website configurator does not ask for your home address, legal name, tax number, passwords, bot token, API keys or Cloudflare token.

Requested translations

When you request a translation, Jarvis sends the selected message text and target language to a translation service. The default route uses Google, with MyMemory as a fallback when Google is unavailable. If the owner configures a custom translation service, only that service receives translation requests. Provider availability and usage limits apply.

Personal Studio accounts

Jarvis stores your display name, unique username, login email, password hash, optional encrypted authenticator secret, hashed recovery code, sessions and up to 100 AI-preview messages with compressed image attachments on its server. Preview messages and images are not sent to an AI provider. Per-account message and image counters reset at 00:00 UTC. Google sign-in stores a verified Google identifier and email without automatically linking existing email accounts. Email addresses are currently unverified login identifiers. Keep your private recovery code: email password-reset delivery is not enabled. Old usernames remain reserved to prevent impersonation. You can clear preview messages and images in Jarvis AI and contact @jarvisbotsupport about account data. Discord permissions and owner inbox access remain separate.

Jarvis sign-ins and support

Jarvis records its own account sign-in time, provider and reported client (website, desktop or browser), plus support actions. Up to 1,000 recent events are retained on the VPS. Authorized owners can see account identifiers, linked sign-in providers and active Jarvis sessions; suspend or restore Jarvis service access; sign out Jarvis sessions; and create a 15-minute, single-use Jarvis password recovery link after verifying identity. The support panel does not expose passwords, other services’ sessions, chat contents or browsing history. Google, Discord and other services manage recovery of their own accounts. Email identifiers remain unverified unless a sign-in provider verifies them. Contact @jarvisbotsupport about your Jarvis account or records.

Community greetings and server branding

Authorized server managers can save welcome and goodbye templates, channels, optional join roles and welcome direct messages. Jarvis keeps recent delivery results without message content or member identifiers in those results. Test messages use your saved server channel and do not assign roles or send direct messages. Discord may retain messages under its own policies.

Server profile images are validated, sent to Discord for the selected server, and represented in Jarvis by the resulting avatar hash. Server settings remain subject to the permissions of the signed-in Discord account.