Jarvis household applications
Privacy policy
Last updated: October 12, 2026
This policy explains how Jarvis Home Display and Jarvis Receipt Intake, privately operated household applications, handle information. My Jarvis Homebase provides information about these applications.
Family photos on Homebase
The Photos box loads an image from the private Family album through the sign-in-protected home display. Photo files and album paths remain on the protected display origin; they are not included in public website files or sent to the homepage through browser messages. Cloudflare provides access protection and network delivery.
Weather on Homebase
The Weather box uses Open-Meteo for the household’s Mackenbach forecast in Fahrenheit. Forecast requests include the configured location coordinates and pass directly from the protected weather view to Open-Meteo, which receives technical request information such as the viewer’s IP address. The homepage receives only a readiness message; forecast records remain in the protected view. No device geolocation is requested.
Google Calendar information
With the account holder’s permission, the app reads the list of calendars available to that account and events from calendars selected for display. It stores calendar identifiers, names, colors, access roles, and time zones to support selection and synchronization. It reads event titles, start and end dates or times, and cancellation status to build the display.
The app requests read-only calendar-list and calendar-event permissions. It does not create, edit, or delete Google Calendar events. The current connector does not request event descriptions, locations, or attendee lists.
How information is used and shared
Calendar information is used only to synchronize and show the selected calendars on the household dashboard. Event titles, dates, times, and calendar names can be seen by people who can view the physical display or access its private network address. Homebase also shows today’s events in a sign-in-protected calendar widget loaded from the home server.
Google Calendar data is not sold, used for advertising, used to train AI models, or transferred to data brokers. Calendar data and authorization tokens are not included in the public website files. Protected calendar views are delivered from the home server through Cloudflare, which provides access protection and network delivery. Google authorization tokens stay on the home server. The connector communicates with Google to authorize access and retrieve calendar information.
Jarvis Home Display’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Storage and retention
Authorization tokens and calendar settings are stored on the private home server in files with restricted permissions, outside the website’s publicly served directory. A separate display file holds event information for the current and following calendar months. Successful synchronizations replace this file. If synchronization fails, the last successful information may remain visible.
Tokens and settings remain until removed by the operator. Revoking Google access stops future authorized retrieval but does not automatically erase an existing local display file. Copies in any operator-managed backups must be removed separately.
Your choices and deletion
The account holder can change which calendars are displayed or revoke access through Google Account connections. To request removal of locally stored credentials, calendar settings, and cached events, contact bradley.r.watkins@gmail.com. The operator can stop synchronization and remove those files. This does not delete the original events from Google Calendar.
Jarvis Receipt Intake: Gmail access
With the account holder’s consent, Jarvis Receipt Intake uses read-only Gmail access to the dedicated household receipt mailbox. It reads account identity to confirm the correct mailbox, and retrieves inbox message identifiers, dates, headers, message bodies and supported attachments. Gmail’s read-only permission can technically access more mailbox content; the current collector uses the configured inbox and start-date boundary. It does not connect to personal mailboxes.
Original email messages and selected text, HTML, PDF and image assets are stored privately on the household server. Messages from approved senders may supply receipt assets for processing. Sender filtering does not prevent other inbox messages from being retained locally. HTML is treated as data; the collector does not execute it or follow embedded receipt links and tracking images.
Receipt processing and sharing
Approved receipt content may be sent to OpenAI through its API to extract purchase information such as merchant, date, items and totals. This can include personal information present in the selected receipt text, document or image. OpenAI processes that content under its applicable API terms and data-handling policies. Extracted purchase records support household receipt review, finance reporting and pantry features. Records requiring review are held for household decisions.
Google receives authentication and Gmail API requests. Cloudflare hosts this information website and provides authenticated remote access to household applications; receipt content viewed or uploaded remotely passes through that gateway. Receipt originals, email archives and OAuth credentials are not published as website assets. Household data is not sold or used for advertising or transferred to data brokers. Access to household records is limited through the configured application and network controls.
Receipt storage, retention and your choices
OAuth credentials, original messages, receipt assets, purchase records and audit history are retained on the household server and in protected backups. The current workflow requests read-only Gmail access and has automatic Gmail cleanup disabled: it does not send messages, mark them read, move them to Trash or permanently delete them. Locally retained originals and records have no automatic deletion schedule.
The account holder can revoke Gmail access through Google Account connections. Revocation stops future authorized retrieval but does not remove existing local records, provider-retained copies or backups. To request access, correction or deletion of local receipt information and credentials, contact bradley.r.watkins@gmail.com. The operator will review and perform the requested local removal, including applicable retained backup copies. Deleting a local copy does not delete the original email from Gmail.
Jarvis Receipt Intake’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Public website visitors
This website contains no sign-in forms, advertising scripts, or application analytics. The site code does not set cookies. If you reorder the homepage apps, your chosen order is stored in this browser’s local storage. It contains app identifiers only, stays on this browser, and is not sent to the server. You can restore the original order from the homepage controls. Clearing this site’s browser data removes the saved preference. Cloudflare provides hosting and may process technical request information, such as IP addresses and browser details, to deliver and protect the site under its privacy policy. If you email the operator, your message and email address are used to respond to your request.
Changes and contact
This policy will be updated when the app’s data practices change, including before adding integrations that process additional information. Privacy questions can be sent to bradley.r.watkins@gmail.com.