Updated 14 November 2026

Privacy

Account and payments

Google sign-in uses Firebase Authentication. We store your account ID, email, display name, usage and allowance records, registered devices, and subscription status. Razorpay handles payment credentials. We keep transaction references, amounts, and status for billing and support.

AI and automation

Jarvis sends microphone audio during an active Live session. Smart Writing can send recorded speech. Depending on what you ask, a task may also send your instruction, selected text, a screenshot, or relevant browser content.

Managed requests go through our backend to Google Vertex AI. Supported Personal API requests go directly from your device to Gemini using your key, which is encrypted locally on Windows. If you enable Personal fallback, eligible Managed failures may use your key. Google’s use of Personal API inputs depends on your Gemini plan and applicable terms. Unpaid use can allow product improvement. See the Gemini API terms.

Chrome Helper

For requested Chrome tasks, the Helper shares relevant tab details, page content, controls, or screenshots with Jarvis. Jarvis may send task content to the AI service in use. The website’s connection check receives only the Helper’s identity, version, and readiness. Extension data use follows Chrome Web Store Limited Use requirements.

Connected services

You choose which services and accounts to connect in Settings and which permissions to grant. Our backend uses Composio to manage those connections and make requests to the provider on your behalf. Google connector availability depends on verification and the environment you are using.

How we use Google connector data

Composio manages the OAuth connection credentials. Our backend receives provider results for the requested task. Relevant results may be kept in the active Jarvis session for follow-up questions and sent to the configured AI service to generate your answer, as described under AI and automation. Our backend keeps connection identifiers, account labels, connection and task status, and action records such as resource identifiers for authorization, verification, and cleanup.

We use Google connector data to provide the features you request and to secure and support those features. keyboard.wtf does not sell this data, use it for advertising, or use it to train AI models. Our use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Disconnect a service in Settings or revoke permission from your Google Account to stop future connector access. Messages, events, documents, and forms already created in your Google account remain there and can be managed in the source service.

Retention and controls

Routine logs retain usage, timing, and status. We keep prompts, message bodies, screenshots, and credentials out of those logs. We limit data use to providing, securing, and supporting the service, including billing. We use access controls and encryption in transit. You can revoke devices or request account deletion from Account.

Deletion disables account use while we verify nonrenewal and clean up account data, including enabled connections. A request can stay pending if cleanup cannot be verified. Required financial and security records may be retained under a pseudonymous account ID.

Published reviews show your rating, text, display name, and date. You can edit or delete your review.

Optional Luma voice

Luma’s caption tour works without a microphone. If you choose Voice, audio goes to Gemini in a separate session. Site voice requires sign-in and uses a short-lived token. Settings voice uses your Personal API key. Guidance uses product help and active shortcut names where applicable. We keep Luma audio and transcripts out of our storage. Stopping or hiding Luma ends its microphone session.

Contact support@keyboardwtf.com.