Your Google identity
openid, email
Read once, when you connect, to record which Google account you connected (its account ID and email address). Jarvis uses that email address to address your primary calendar.
Private beta - invited test users only
Your private scheduling assistant.
OneTimeLogin Jarvis finds a time that works and puts the meeting on your Google Calendar. You decide who Jarvis may schedule with, on which days, for how long and how often. Jarvis checks when you are free and adds the meetings you approved. It does nothing else with your calendar.
How it works
-
Step 1
Sign in and connect
Sign in with your OneTimeLogin account and a second factor, then connect Google Calendar. Google shows you its own consent screen; Jarvis never sees your Google password.
-
Step 2
Set the rules
Pair with people you trust and give Jarvis a scheduling permission: allowed weekdays and hours, maximum meeting length, a daily limit and an expiry date. You can require your approval for each meeting.
-
Step 3
Jarvis books it
Jarvis offers only times when your calendar is free, and when a time is agreed it adds one private event to your Google Calendar and checks that it was created.
Why Jarvis asks for Google Calendar access
Jarvis requests exactly four permissions, in three groups. Each group has a single job:
Calendar events
https://www.googleapis.com/auth/calendar.events
Used to add the meeting you approved to your calendar as one private event (with a Google Meet link only if you ask for one), and to read back that same event to confirm it was created. Jarvis does not list, search, change or delete your other events, and it sends no invitations.
Free/busy times
https://www.googleapis.com/auth/calendar.freebusy
Used to ask Google whether a proposed time is free, just before Jarvis offers it and again before it books it. Google answers with busy time ranges only, never event titles, attendees or details. Jarvis uses the answer to decide yes or no and does not store your busy times.
No AI reads your calendar. No Google user data is sent to Claude, Gemini or any other AI or machine-learning model, and none is used to train one.
You stay in control
- Disconnect in the console: open the Jarvis console, go to Connections and choose "Revoke connection". Jarvis stops using it at once, overwrites its stored Google token with a revocation marker and asks Google to revoke the token.
- Or revoke at Google: remove "OneTimeLogin Jarvis" at myaccount.google.com/permissions.
- Ask us to delete your data: email sanjay.sachi@gmail.com.
Policies and contact
OneTimeLogin Jarvis's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Support, privacy and developer contact: sanjay.sachi@gmail.com