Privacy

Local work

Signing in to Zoltbot does not upload your local projects, conversations, files, artifacts or coding-provider credentials. Local desktop features remain available without an account.

When you use a coding provider or another connected service, the information you send to that service is also governed by its privacy policy.

Google sign-in and account information

Google sign-in supplies your Google account identifier, verified email address and profile name. Zoltbot uses these to create and identify your account and personal organization. It requests the OpenID, email and profile permissions, which do not grant access to Gmail, Google Drive or your repositories.

Zoltbot stores account records, organization membership, session identifiers and security events. Session records include the client type, device name and activity timestamps so you can recognize and revoke access. Tokens used only for Google identity sign-in are not retained by the account service. Separately connecting a Google data service uses the exchange described below.

Connected services and Google data

Connecting Gmail, Google Drive or Google Docs is optional and separate from signing in to a Zoltbot account. You authorize each connection through Google and choose which local coding-agent profiles may use it.

Gmail requests read access to search messages and read threads, including message bodies. Google Drive requests broad read access to discover and read files across your authorized Drive, rather than access limited to individually selected files. Google Docs requests Drive read access for discovery and Docs read access for document content and structure. These integrations do not request permission to send email, create drafts, edit documents, upload, share or delete files.

Service requests run from your Mac to the connected service. Google connections use the stable Gmail, Drive and Docs APIs through a local Zoltbot tool adapter. Google tokens stay in the local daemon; the coding agent receives a local connection credential. When an approved coding-agent profile uses a connection, retrieved messages, files or documents can become part of the context sent to the coding provider you selected to fulfill your request. That provider processes the context under its own terms, privacy policy and account settings. Review those settings before allowing a profile to access sensitive information.

Zoltbot does not sell Google user data, use it for advertising, or use it to train generalized AI models. Zoltbot’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Connection credentials and the hosted exchange

GitHub, Google and Slack connections use a Zoltbot-hosted OAuth exchange; you do not need a Zoltbot account for this exchange. Application secrets stay on the server. The exchange processes authorization codes and tokens to complete sign-in and refresh access. Its database holds encrypted, short-lived authorization transactions, not a long-lived table of your service access or refresh tokens.

Authorization transactions expire after ten minutes and one-time handoff codes after one minute; an hourly cleanup removes expired records. Access tokens are stored in the Mac’s operating system credential vault. Encrypted refresh credentials are held locally and expire after at most 90 days, or earlier if the provider revokes access. Credentials may be delivered to an approved local coding-agent process so it can call the service.

The exchange uses essential cookies to bind authorization to the browser that started it. It does not intentionally log service tokens, authorization codes or message and file contents. Hosting providers may process operational request metadata.

Cookies, credentials and service providers

The account service uses essential cookies for sign-in, session continuity and request protection. Desktop account credentials are kept in the operating system Keychain. They are not stored in local project data or exposed to the desktop renderer.

Google provides identity verification and Google Cloud hosts the account API. Supabase hosts the account database, and Vercel hosts this website. These providers process information needed to operate their services. Hosting systems may process request metadata such as IP addresses, timestamps and error information for service operation and security.

Online content

Where online artifact storage is enabled, uploading requires selecting and confirming the files to send. Online copies are private to the owning account unless an additional sharing feature is explicitly offered and selected. Account sign-in alone does not upload or publish an artifact.

Access, deletion and retention

You can disconnect a service in Zoltbot to remove its locally stored connection credentials and stop future use by that connection. Disconnecting does not revoke the service’s authorization or erase content already delivered to a coding provider or saved in a conversation. Revoke Google access separately in your Google Account connections; use the equivalent controls for other services. Local conversation and workspace data must be deleted separately on your Mac.

You can review sessions, revoke access, download account metadata and request account deletion from your account page. The metadata export includes artifact manifests where applicable; it is not an archive of uploaded file contents.

A deletion request revokes account sessions immediately and queues removal of account and personal cloud data. Local desktop projects remain on your computer. Database backups are retained for seven days and may temporarily contain deleted records. Security and hosting records may have separate retention periods. Contact us if you need help accessing or deleting your information.