Privacy policy

Information accessed

• Account identity: your primary Google account email and identity information returned by Google's OpenID service. The connector uses this to identify the connected account and show its email in provider settings.
• Authorization credentials: OAuth access and refresh tokens, expiration information, and the application registration that issued them. GENOME does not ask for your Google password.
• Service information: the Code Assist service project identifier, account eligibility responses, available model information, and quota or reset information when Google returns them.
• Model request content: relevant conversation history, instructions, attachments or file excerpts, tool names and schemas, tool arguments, and tool results included in a request. Google returns model output and may return usage metadata.

Google permissions and their purpose

openid and email permissions associate a connection with the Google account you choose. The connector also requests https://www.googleapis.com/auth/cloud-platform for the Code Assist service's eligibility, setup, model discovery, quota, and generation operations.

Google describes cloud-platform as permission to see, edit, configure, and delete Google Cloud data. It is broader than the operations implemented by this connector. GENOME's subscription connector does not implement a general Google Cloud administration interface or request Gmail-message or Google Drive-file scopes.

OAuth consent does not guarantee subscription access. Google's service determines whether the application and account are eligible.

How information is used and shared

The connector uses account information to maintain the connection, display the account and available quota, and send the model requests needed for the tasks you initiate. Native function calls are passed to GENOME's tool and permission workflow; tool output needed to continue the conversation may be sent back to Google.

Google account credentials are sent to Google's OAuth, identity, and supported Code Assist endpoints for those operations. The connector does not import Antigravity credentials or forward this connection through an Antigravity agent.

The GENOME Google connector does not sell Google account information or use it for advertising, and it does not independently use Google user data to train a generalized AI model. GENOME's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Google processes requests under its own applicable service terms and privacy practices. If you select another model provider or authorize a network-capable tool, that separate provider or tool may receive the information needed for its task. This policy does not mean that all desktop conversation content stays on your computer.

Storage, retention, and deletion

OAuth credentials are stored in auth.json in the data directory of the computer or server running GENOME. An imported OAuth application registration is stored separately in google-oauth-client.json. Files use restrictive permissions where supported by the host filesystem; this connector does not provide additional application-level encryption for those files.

Credentials remain until you disconnect or replace the connection on that server. Quota and account lookups can be cached in memory briefly. Conversation history, files, tool results, and model output can remain in the installation's session or project storage after disconnecting an account.

To remove the saved connection, use the provider's disconnect control in GENOME settings. To revoke Google's authorization, remove GENOME from your Google account's third-party connections. Disconnecting does not delete project files, chat history, copies in backups, or data already processed by Google; manage those separately on the relevant system.

If you use a remote GENOME server, its operator controls that server and its storage. Protect it and its backups appropriately. Do not upload credentials or private project files to this website.

Security and your control

Google requests use HTTPS. Browser sign-in uses PKCE and a random state to bind the local callback to the intended authorization attempt. GENOME rejects explicitly reduced consent that lacks the permission needed by its subscription connector.

You choose when to connect an account and can review Google's consent before approving it. Tool access follows your installation's permission configuration. Keep your operating system, server access, and account security settings protected; no system can promise absolute security.

This website

The website has no Google sign-in form, account-token storage, analytics scripts, or project-upload form in its source. Hosting and network providers may process standard request information such as IP addresses and request timestamps to operate and protect their services. The hosting provider's practices are separate; see OpenAI's privacy policy.

If you email support, your email provider and the support mailbox process the message. Send only the information needed for the question, not passwords or tokens.

Contact and changes

For questions about this policy or the GENOME Google connector, email alaa2031988@gmail.com. Material changes to these practices will be reflected in this policy and its effective date.