Privacy Policy

We collect account and profile details, organization membership, connected repository metadata, instructions and files you provide, agent conversations, security and audit records, usage data, and billing information needed to provide the service.

When you deliberately connect a third-party service, we also receive information from that service. Depending on the connection, this may include Google account identity, Gmail message metadata and selected message content, selected Drive file metadata and content, calendar or analytics data, Microsoft data, GitHub data, or other information you authorize. This information can be sensitive because its contents are chosen by you or other people who communicate with you.

Google sign-in is separate from Google Workspace integrations. Sign-in uses only basic identity scopes. CodePress-managed Google Workspace data access is currently disabled while we complete our compliance and security remediation.

Before Workspace access is made available, it will require a separate disclosure and affirmative consent for the exact capability and scopes shown on screen. The service will fetch raw Gmail or Drive content only for the requested action, process it in a trusted backend boundary, and give agents only a bounded, screened extraction with provenance. High-risk content will be withheld for a person to open directly in Google.

The launch design does not retain raw Google content in chat transcripts, logs, analytics, event history, or agent-provider recordings. It permits a derived assistant summary to be retained only with consent and requires deletion when the associated chat or Google data is deleted. Legacy Google content is being remediated before Workspace access can be re-enabled.

CodePress's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google-classified requests will be routed only to processor configurations approved for that purpose. We do not use Google user data for advertising or to train general-purpose AI models. Workspace access will not be enabled until required processor, retention, deletion, and revocation controls have been validated.

See the Google data controls page for categories, controls, deletion, and incident handling.

We use information to provide requested product functions, operate and secure accounts, maintain auditability, communicate with you, support users, prevent abuse, comply with law, and improve the service using appropriately de-identified operational information.

We disclose information to infrastructure, authentication, payment, communications, observability, and AI service providers only as needed to perform those functions under applicable contractual and security controls. We may also disclose information when required by law or to address a documented security or legal emergency. Human access to Google user data requires case-specific user consent or a documented security or legal exception.

Retention depends on the data and service configuration. You can delete chats, disconnect integrations, or request account deletion. The Google Workspace relaunch is also conditioned on dedicated consent withdrawal, provider revocation, and Google-data deletion controls. Security and compliance audit records may retain identifiers, timestamps, and outcomes, but must not retain Google content.

We use technical and organizational safeguards appropriate to the service, including access control, encryption, monitoring, and vulnerability management. No system is completely secure. If an incident affects your data, we will investigate and provide notices required by law and applicable provider obligations.

Depending on where you live, you may request access, correction, deletion, portability, restriction, or objection. Contact privacy@codepress.dev. We may update this policy as the service or law changes and will post the new effective date here.