Privacy Policy

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.

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 generic alert text and an opaque delivery identifier, rather than the underlying chat, email, or task content. The app fetches the details after you open the alert while signed in.

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.