Privacy Policy for NewCovenant Rigs

Effective Date: October 22, 2026
Location: Farmersville, Texas, United States
Applies to: the JARVIS desktop assistant and related automation tools

NewCovenant Rigs ("we," "us," or "our") respects your privacy and is committed to protecting your personal data. This Privacy Policy explains how we collect, use, and safeguard information when you use our desktop applications and automation tools (collectively, the "Services"). The apparel and hardware storefront at https://newcovenantrigs.com is covered by its own privacy policy.

1. What the application is

JARVIS is a Windows desktop application operated by NewCovenantRigs LLC. It runs locally on the operator's own workstation and connects to one Google account — the operator's — to triage that mailbox, draft replies for a human to approve, and summarize that calendar. There is no public sign-up, no hosted multi-tenant service, and no account system of our own. A description of what it does is on the overview page.

2. Information We Collect

We collect minimal information necessary to provide and secure our Services:

Account & Contact Information: Email addresses provided directly by users or through developer consent interfaces.
Google User Data: When authorized via OAuth, our applications access Google Workspace services (such as Gmail API data) exclusively to deliver inbox triage, calendar management, and assistant automation features.

Exactly which Google data is accessed, and why

Scope	What the app reads or writes	Why it is needed
`gmail.readonly`	Message senders, subjects, labels and — for messages the triage rules flag as needing attention — message bodies	To sort incoming mail into what needs a reply, what is informational, and what looks suspicious
`gmail.modify`	Applies and removes labels on messages already in the mailbox	To file mail once it has been triaged, so the same message is not re-triaged daily
`gmail.compose`	Creates draft messages	To write draft replies. Drafts are never sent automatically; a human approves each one
`gmail.labels`	Reads and creates labels	To maintain the labels triage files mail under
`calendar.readonly`	Event titles, times and attendees for the current day	To summarize the day in a morning brief
`userinfo.email`, `userinfo.profile`	The signed-in address and display name	To confirm which account is connected

The application does not delete mail, does not send mail, does not modify calendar events, and does not read any Google account other than the one that granted consent.

3. How We Use Google User Data

Our use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

We do NOT sell, rent, or trade Google user data or personal data to third parties.
We do NOT use Google user data for serving advertisements or training generalized AI models.
Data accessed via APIs is used strictly to process local workspace automation and desktop assistant display requests.

No human other than the account owner reads the data. We do not use it for analytics, profiling, or any purpose unrelated to the features above.

4. Where the data goes

Mail and calendar content is handled in three places and nowhere else:

The operator's own workstation. The OAuth token and the triage output are written to the local disk of the machine the application runs on, under a credentials directory and a log directory inside the application's own folder. Nothing is uploaded to a server of ours, because we operate no server that receives this data.
The Anthropic API, which performs the language processing. Message senders, subjects, labels and the bodies of messages being triaged or drafted against are sent to Anthropic for that purpose. Anthropic processes the request and returns the result; see Anthropic's privacy policy.
A private Discord channel owned by the operator, used as the approval surface so the operator can approve a draft from a phone. Daily triage alerts carry subject lines and sender names only — message bodies stay in the local log. A draft awaiting approval does include the text of that draft, because the operator has to read it to approve it.

Google user data is not shared with any other recipient, and is never transferred to anyone for advertising, resale, or model training.

5. Storage, security, and retention

OAuth tokens are stored on the operator's workstation, in a directory outside version control, and are used only to call the Google APIs listed above. They are not transmitted anywhere else.
Triage logs — the daily summary of what needed attention — are written to the same workstation and retained until the operator deletes them.
Approval records (which drafts were approved, cancelled, or expired) are held in a local database file on that workstation. Draft text expires from the approval queue automatically, by default within hours of being raised.
Discord messages remain in the operator's private channel until deleted there.
The workstation is password-protected and the application runs under the operator's own account. Access to the Google data therefore requires access to that machine.

6. Data Protection & Texas Privacy Compliance

We comply with applicable state laws, including the Texas Data Privacy and Security Act (TDPSA). We maintain industry-standard physical, electronic, and procedural safeguards to protect personal information against unauthorized access, alteration, or disclosure.

7. Third-Party Services

Our application integrates with trusted third-party providers strictly for backend communication (such as Cloudflare and Anthropic API). These services process data in accordance with their respective security standards.

Anthropic — language processing, as described in Section 4.
Discord — delivery of approval requests to the operator.
Cloudflare — hosting for this website. These pages are static and collect nothing from visitors; no Google user data passes through them.

8. Your Rights & Data Deletion

Under Texas law, users have the right to request access to, correction of, or deletion of their personal information. To revoke Google API access at any time, visit your Google Account Security Settings. To request account or data deletion, contact us at: dominickhelton1@gmail.com.

Specifically, to end the application's access and remove what it holds:

Revoke the grant at myaccount.google.com/permissions. The stored token stops working immediately and no further data can be read.
Delete the local credentials directory and log directory on the workstation, which removes the stored token and every triage summary derived from the mailbox.
Delete the messages in the private Discord channel.
Or email the address above and we will do all three and confirm when it is done.

9. Changes to this policy

We will update the effective date at the top of this page whenever this policy changes — for example, if the application begins using a different Google scope or a new third-party processor.

10. Contact Us

If you have questions regarding this Privacy Policy, please contact:
NewCovenant Rigs
Email: dominickhelton1@gmail.com
Farmersville, TX 75442