JarvisApp information

Privacy policy

This policy explains how the private Jarvis app handles data from connected Google accounts. Alexander Brown KC operates Jarvis and is its sole authorised user.

What Jarvis accesses and why

Storage and access

Jarvis keeps encrypted Google authorisation records on its server to maintain connections across sessions. Retrieved source records are held in the open app session for display. Some app features retain separate owner-only state across sessions, such as encrypted review fingerprints.

Google provides the connected services. OpenAI Sites and its hosting infrastructure run the private app and process data needed to provide it. Access to retrieved records in Jarvis requires the owner’s sign-in. The public information pages contain no connected Google records.

Jarvis uses Google data for the features described above. If the owner chooses to copy a prepared prompt or open a source link in another service, that service handles the information the owner chooses to provide to it.

Disconnecting and getting in touch

The owner can disconnect a service from Connections in Jarvis. Google permissions can also be withdrawn from the Google Account connections page. To ask about this policy or request deletion of data held by Jarvis, use the support contact shown on the Jarvis Google authorisation screen.