Privacy Policy
Last updated: 30 September 2026
This policy covers JARVIS, a private internal assistant operated by Aryan Kapoor ("we", "us") at aihum4n.com.
Who uses this application
JARVIS has a single user: its operator. It is not offered to the public, has no sign-up, and no third party holds an account. The only Google account it accesses is one the operator owns and has explicitly authorised.
What Google user data we access, and why
| Permission requested | What it allows | Why we request it |
|---|---|---|
openid |
Your Google identity | To identify which account is connected |
userinfo.email |
Your email address | To display the connected account |
userinfo.profile |
Your basic profile | To display the connected account |
gmail.readonly |
Read your Gmail | To count unread mail and summarise recent subjects in the daily briefing |
calendar.readonly |
Read your Calendar | To list the day's events in the daily briefing |
gmail.send |
Send email as you | To send an email only after the operator has reviewed and approved that specific message. Never sent automatically |
calendar.events |
Create, change and delete Calendar events | To apply a calendar change only after the operator has reviewed and approved that specific change. Never applied automatically |
We request no other Google scopes. We do not request access to Google Pay, billing, or payment data of any kind.
About the two write permissions
JARVIS can compose an email or a calendar change, but it does not decide to send one. Every outbound action is queued for the operator, shown in full, and dispatched only on an explicit human approval. Actions that fail an internal quality check are refused outright and are never queued. The operator can revoke all access at any time (see below).
How the data is used
Data read from Google is used to generate a private daily briefing for the operator — a summary of upcoming calendar events and recent mail — and to prepare draft actions for the operator's approval. It is not used for advertising, profiling, resale, or for training machine learning models.
How the data is shared
We do not sell or rent Google user data, and no third party holds an account or receives it for their own purposes.
One disclosure, stated plainly: to write the daily briefing in readable prose, the summary text — which can include calendar event titles and email subject lines — is sent to Anthropic's Claude models, either through the Claude command-line client or the Anthropic API. Anthropic processes this text solely to return the generated summary. See Anthropic's privacy policy. No other third party receives Google user data.
How the data is stored and retained
- Google data is read on demand when a briefing is generated. Raw mail and calendar data are not stored as such.
- Each generated briefing is stored, and stored indefinitely. A briefing is written to a database on infrastructure controlled by the operator so the most recent one can be re-read, and its text can include email subject lines and calendar event titles. There is no automatic expiry and no scheduled deletion. Briefings remain until the operator deletes them manually.
- Short-lived operational caches expire automatically (3 hours and 24 hours respectively).
- OAuth tokens are stored encrypted on infrastructure controlled by the operator.
Limited Use
JARVIS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Revoking access and deleting data
The operator may revoke JARVIS's access at any time at myaccount.google.com/permissions. On revocation the application can no longer read any Google data or send anything on the operator's behalf. To request deletion of stored data, contact admin@aihum4n.com.
Children
This application is not offered to the public and is not directed at children.
Changes
Material changes to this policy will be reflected in the "Last updated" date above.