Privacy Policy

Who operates Jarvis

Jarvis is the private operations workspace operated by Nate Hall for WeedEater Lawn Care. This policy covers the Jarvis application and its connected services.

Information Jarvis uses

Jarvis processes sign-in information, authorized business records, notes, tasks, and information supplied through its features. Business records may include customer contact information, property details, schedules, jobs, invoices, and payment records from connected systems. Access to each integration depends on the permissions granted to Jarvis.

Google Calendar access and use

When the account owner connects Google Calendar, Jarvis requests the calendar.readonly permission. This allows it to list calendars the Google account can access and read events. The owner selects the calendar used for event previews and live connection checks.

Event information may include titles, dates, times, and other details returned by Google Calendar. Jarvis displays calendar previews separately from Homeworks jobs. It does not create, modify, or delete Google Calendar events or convert them into billable jobs.

Storage and retention

Jarvis stores Google access and refresh tokens, authorization metadata, and the selected calendar identifier and name in its server-side Supabase database. These credentials support access without requiring a new sign-in for every read. Privileged credential access is restricted to the integration backend and authorized owner operations.

The current Calendar integration reads event previews on demand and does not save the returned event list as a separate set of business records in the database. Preview data is processed by the hosting service and displayed in the signed-in browser. Service providers may retain operational logs and backups according to their configured retention.

Service providers and sharing

Jarvis uses Vercel for application hosting and Supabase for authentication and storage. Google processes Calendar authorization and API requests. These providers process information needed to deliver their services.

Jarvis AI may process questions and relevant business context through the configured AI provider. The current Calendar integration does not feed Calendar event previews or OAuth credentials into the AI assistant; it may report connection health. Information you deliberately include in a question is processed as part of that question.

Jarvis does not sell Google user data, use it for advertising, or use it to train general-purpose AI models. Any use or transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Disconnecting and deletion requests

The owner can disconnect Google Calendar in Jarvis Settings. A successful disconnect removes the saved connection credentials and calendar selection from the active database and attempts to revoke the token with Google. Access can also be revoked directly in the Google account's third-party connections settings.

Disconnecting does not delete events in Google Calendar or business records in Homeworks or QuickBooks. Contact the operator for requests about other stored information or backup retention. Data needed for business recordkeeping may be handled separately from integration credentials.

Security and browser features

Jarvis uses authenticated workspace access, server-side integration permissions, and HTTPS connections. No system can guarantee absolute security. Sign-in uses cookies. Conversation history and preferences may be saved in the browser; the interface provides controls for supported local history. Voice features use the browser's speech service when enabled.

Questions and updates

For privacy questions or requests, contact natehall9876@gmail.com. This policy will be updated when the application's data practices change.

About Jarvis