Privacy notice

Version 2026-09-08 · JARVIS Business · Noah Friel, United Kingdom

Questions, complaints and deletion requests: shop.flyingelite@gmail.com.

JARVIS is a local, single-user content-production application, not a publicly hosted multi-user service. It uses YouTube API Services. See the Google Privacy Policy.

What is collected and why

With Google OAuth permission, JARVIS accesses channel identity/statistics, video IDs, publication dates, duration and privacy status, and channel-owned analytics: views, engaged views, watch time, average view duration/percentage, likes and subscribers gained. These support your dashboard and experimental hook selection. Upload permission is requested separately. Approved video files, titles, descriptions and audience/disclosure choices are sent to YouTube. Revenue is not retrieved. JARVIS never requests your Google password.

Local storage and external providers

OAuth tokens, reports, snapshots, upload receipts, production jobs, learning profiles, scripts, generated media and cost records are saved on your Mac. Tokens use restricted filesystem permissions, not application-level encryption. Protect your Mac and backups. Script queues use browser local storage. A short-lived HttpOnly SameSite cookie binds OAuth to your browser. Privacy acceptance is stored locally with its version and time.

Perplexity receives research inputs, public trend leads and writing instructions. OpenAI receives inputs for script generation, narration, audio transcription and assistant conversation, depending on the feature used. Browser speech recognition may send audio to the browser provider while you enable listening. Microphone use is optional and can be disabled in browser settings. Do not submit secrets or unnecessary personal information. JARVIS has no advertising integration.

YouTube data and learning

Analytics collection attempts run approximately every six hours while the server is running, the loop is enabled and this notice is accepted. Recommendations are an independent, observational JARVIS heuristic, not YouTube-provided recommendations, causal proof or foundation-model training. Copies of learning evidence may be saved with production jobs and upload receipts.

Delete local YouTube data

Use Delete local YouTube data in the application footer and confirm the phrase shown. It removes OAuth tokens, cached reports/snapshots, upload receipts, loop state and saved production learning profiles. It refuses to run during production or YouTube operations. If an error is shown, deletion has not been confirmed; retry when idle or contact the operator.

Original scripts, generated audio/video and cost records are retained. Deleting receipts removes the associated duplicate-upload protection. This action does not delete anything on YouTube, and cannot erase copies you exported or backed up outside the application. Manage those separately.

The separate Disconnect locally control removes local credentials and cached reports/snapshots but retains upload history. For comprehensive local YouTube cleanup use the deletion control instead. Revoke the Google grant at Google account permissions; local deletion and Google revocation are distinct actions.

Retention and revocation

After this notice is accepted, JARVIS applies a conservative 29-day expiry to the local YouTube connection and associated reports, receipts and production learning profiles. The timer is not extended by refreshing analytics. Expiry removes those local records and requires reconnection. Original scripts, media and cost records are not removed. Receipt-based duplicate protection is lost when receipts expire, so check YouTube Studio before re-uploading an older production.

A Google refresh-token response of invalid_grant triggers the same cleanup after the current YouTube operation finishes. Temporary network failures do not trigger deletion. Cleanup checks run each minute and before protected application requests while JARVIS is running; active production can defer cleanup. Google grant status is checked through token refresh during API activity, normally the six-hour collection loop. If you pause the loop, detection may wait for your next Google API action.

Material changes to this notice require a new acceptance version. Contact the operator before using this prototype for other people's accounts.

JARVIS · Terms of use