1. Scope
This Privacy Policy explains how Jarvis accesses, uses, stores, and protects information when a user connects Google services such as Gmail, Calendar, Drive, Docs, Sheets, and Slides to the assistant.
2. What Jarvis is used for
Jarvis is a productivity assistant that helps users handle communication, scheduling, document work, spreadsheet operations, and presentations. Google APIs are used only to provide the features the user has requested and explicitly authorized.
3. What data may be accessed
Depending on the scopes approved by the user, Jarvis may access:
- Gmail message metadata, message content, drafts, labels, and send actions.
- Calendar lists, availability, event details, and calendar settings needed for scheduling flows.
- Drive file metadata and user-selected or user-shared files.
- Document content in Google Docs.
- Spreadsheet structure and values in Google Sheets.
- Presentation structure and slide content in Google Slides.
4. Why that data is used
Jarvis uses connected Google data only to perform user-requested assistant features, such as:
- Reading or summarizing inbox state.
- Drafting, replying to, or sending email.
- Checking free time and creating or updating events.
- Creating and editing documents, spreadsheets, and presentations.
- Working with files created by the user or shared with the connected assistant account.
5. What Jarvis does not do with Google data
- Jarvis does not sell Google user data.
- Jarvis does not use Google user data for advertising.
- Jarvis does not use Google user data for unrelated profiling.
- Jarvis does not use Google user data for unrelated model training.
- Jarvis does not ask users to type Google passwords into Jarvis-owned forms.
6. Storage and security
Jarvis stores only the delegated access and operational data needed to keep the connected features working. Access credentials and stored operational artifacts should be protected using appropriate technical measures such as encrypted storage, access control, audit logging, and least-privilege handling.
7. Sharing and disclosure
Google user data is shared only when necessary to provide the service requested by the user, comply with applicable law, or protect the service against abuse or security issues. Jarvis does not share Google user data with third parties for commercial resale.
8. User control and revocation
Users can revoke Jarvis access through Google's account permissions or through the product's account connection settings. Once access is revoked, Jarvis can no longer access new Google data through the revoked connection.
9. Retention
Connected data and derived work products are retained only for as long as needed to provide the assistant features, support the user's workflow, satisfy security requirements, or comply with legal obligations. Operators of a Jarvis deployment may define shorter retention policies.
10. Google API Services policy
Use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
11. Contact
Privacy questions, access revocation requests, and policy notices can be directed to legal@your-domain.com.