Groovy
Start free trial
Legal

Privacy Policy

Last updated October 23, 2026

This policy describes how Groovy handles information when you use its hosted website, desktop software, and iOS or Android app. A self-hosted Groovy deployment may be operated by your organization under its own privacy practices. If you use Groovy through a team, that team may also control the workspace content it shares with you.

Information Groovy handles

  • Account and workspace information: your email address, profile, authentication information, team memberships, settings, and license or billing records.
  • Content you use in Groovy: chats, threads, tasks, files, agent instructions, approvals, and the results of actions you request. People in a shared workspace may see content according to that workspace's access settings.
  • Connected-service information: data you choose to connect, such as Gmail messages and drafts, calendar information, or other integration results. Groovy accesses this information to provide the features you enable and the actions you request.
  • Voice and device information: microphone audio during an active Live conversation, its resulting text or session details, an optional push token for each phone, and technical information needed to deliver and troubleshoot the service.
  • Website and service activity: usage, diagnostics, security logs, and website analytics. The website uses a Datagran pixel to measure visits and product activity.

How Groovy uses information

Groovy uses this information to sign you in, keep your workspace in sync, run the features and integrations you choose, generate AI responses, deliver notifications, manage licenses and payments, provide support, and protect the service. When an AI feature needs a model provider, the relevant request and content are sent to the provider configured for that feature. Provider handling also depends on your account and the provider's terms.

Groovy asks for microphone access when you start a Live conversation and may ask for notification permission after you sign in on a phone. You can turn off phone alerts in your device settings or sign out on that phone to remove its notification registration.

AI services and your permission

AI requests may include your prompt and conversation history, attachments such as files and photos, and relevant workspace content, connected email or calendar data, and tool results needed to complete the request. This content may contain names, email addresses, and other personal information. During an active Live voice session, microphone audio and conversation text are sent to OpenAI.

Recipients depend on the model and feature you choose. Their published policies are linked below. Datagran features require a Datagran account.

Unnamed custom model providers cannot be configured in the iOS app. Connected tools can send data to services you ask them to use. Review those destinations before approving an action.

The mobile app asks for explicit permission before opening the workspace on a phone. Groovy records your choice, disclosure version, time, and a random identifier for that installation, separately for each account. You can request account deletion before granting permission, decline and sign out, or withdraw permission on that phone in Settings, under AI data sharing. Withdrawal closes active mobile calls and prevents new AI access from that phone until you allow it again. It does not cancel work already running on the server or other devices, disconnect integrations, or erase data previously sent to a provider. Contact us to request deletion of previously shared data. Manage server automation and connected-service permissions separately in your workspace.

Provider retention and processing depend on the service and the data controls configured for your workspace. We require service providers handling personal information on our behalf to protect it to the same or an equal standard as this policy, including safeguards for access, use, and disclosure. We do not promise that every provider has zero retention. Review your provider settings before sending sensitive content.

Chat safety and reports

You can report a message or block its sender from the message menu. Settings, Chat safety lets you unblock people. Blocking hides that person's messages, prevents direct messages and shared calls between the accounts, and suppresses their chat alerts. It does not erase messages for other workspace members or recall alerts already delivered to a device.

Reports share the reported message, its attachment details, your account identity, reason, and explanation with Groovy moderators. Reports are private to the reporter and Groovy moderators. Moderators can remove content and keep the report evidence and decision for abuse investigation and audit. Contact support to request review or deletion of that information. Chat text with detected threats or sexual exploitation is hidden behind a warning you can report. This automated check does not detect every kind of abuse or inspect media.

Google-connected data

If you connect a Google account, Groovy uses the authorized Google data for the user-facing mail, calendar, and other connected features you enable. For example, it may read new Inbox messages to show them in Groovy, prepare a draft you can review, or alert you to a new message. Groovy does not use Google Workspace data to serve ads or train generalized AI models. Groovy's use of information received from Google Workspace APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

When information is shared

Groovy uses service providers to host and operate the product, including Vercel and Supabase; Stripe for payments when applicable; and the model or integration providers needed for features you choose. Groovy may send information to another service when you explicitly connect it or ask an agent to act there. We may also disclose information when required by law or to protect the service and its users.

Mobile alerts are routed through Expo and the Apple or Google push services. The push payload contains a title, an opaque delivery identifier, and a short preview of chat, email, or task content. Previews may appear on your lock screen, depending on your phone settings. Full content is fetched after you open the alert while signed in. You can hide notification previews or disable alerts in your phone settings.

Retention, security, and your choices

Groovy keeps account information and workspace content while needed to provide the service. Some records may be retained longer for security, billing, dispute resolution, or legal obligations. We use access controls and encryption in transit, and protect stored connection secrets. No service can guarantee absolute security.

You can disconnect optional integrations and change notification preferences in Groovy. To request account and data deletion, follow the steps on our account deletion page. To ask about access, correction, export, or other questions about your personal information, contact theshopcbg@gmail.com. We may need to verify that the request comes from the account owner. We will explain if a legal obligation requires us to retain specific records.

Changes and contact

We may update this policy as Groovy changes. The date above identifies the latest version. Questions about this policy can be sent to theshopcbg@gmail.com. You can also visit the support page.