Mouseover Privacy Policy.

Our service

Mouseover is a beta Mac app that lets you talk to AI while you work. With your permission, it can use your microphone and screen to answer questions, summarize work, and guide you through tasks.

Google sign-in and Google user data

Beta activation uses Google OAuth sign-in. Mouseover requests only the openid, email, and profile scopes, which may include your Google account identifier, email address, name, profile image, and locale. Mouseover uses this data to authenticate you, create your Mouseover account, activate beta access, secure API calls, provide support, detect abuse, and maintain your signed-in session.

Mouseover does not request Gmail, Google Drive, Calendar, Photos, Contacts, Docs, or other Google Workspace content through Google OAuth.

Google API Limited Use

Mouseover's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Mouseover does not sell Google user data, transfer Google user data to advertising platforms, data brokers, or information resellers, use it for advertising, retargeting, credit-worthiness, lending purposes, or train generalized AI/ML models with it.

Microphone, screen, and AI processing

Microphone audio is sent during a Working Session according to the mode you choose: hands-free listening or hold to talk. Screen frames are shared as low-rate visual context only while a Working Session is on. Ending the session stops microphone and screen transmission.

This working-session data is sent to the Mouseover API and processed by Google Gemini to provide real-time assistance, visual feedback, transcripts, summaries, checklists, prompts, and other user-facing features. Supported models may use Google Search grounding when you ask for current or external facts. This data is separate from Google user data received through Google sign-in.

Session history and workflow memory

Mouseover stores readable Working Session transcripts, summaries, and workflow memory locally on this Mac so you can revisit, copy, delete, and continue work later. When you are signed in for beta access, Mouseover also syncs sanitized, bounded session history and workflow memory to your Mouseover account. These records do not store raw microphone audio or screen image/video frames.

Beta activation, usage, and diagnostics

Beta activation uses Google sign-in, your email address, and your invite code to create a signed-in session. Mouseover records sanitized beta usage and diagnostic events such as session starts and ends, token requests, Deep Thinking request counts, shortcut use, update checks, project template actions, permission status, error categories, app version, model name, and token counts. These events do not include microphone audio, screen frames, beta access codes, transcripts, or raw app session content.

Product waitlists

If you join the Windows waitlist, Mouseover stores your email, platform, language, and form source so we can notify you about Windows availability and related product updates.

How we share data

We share data only as needed to provide, secure, and improve Mouseover, such as with service providers that help us provide sign-in, account and data storage, website and API infrastructure, AI processing, product analytics, downloads, and updates. We may also share information when required by law, to protect users and the service, or as part of a business transfer.

We do not sell personal data or Google user data.

Website and app analytics, and cookies

Mouseover uses product analytics to understand page views, basic button clicks, and sanitized product events such as downloads, feedback links, project template actions, app opens, beta activation status, permission completion, and Working Session status. Product analytics does not include microphone audio, screen frames, beta access codes, transcripts, or raw app session content.

Google sign-in, account services, and analytics services may use cookies or similar technologies to maintain authentication, secure the service, remember preferences, or measure website usage.

Data protection

Mouseover uses HTTPS in transit, stores sign-in tokens in the macOS Keychain, keeps production API keys server-side, and limits session history, workflow memory, app feature data, and usage data. No online service can guarantee absolute security, but we use reasonable measures to reduce the risk of unauthorized access, loss, misuse, and disclosure.

Retention, deletion, and controls

Local session history and workflow memory remain on your Mac until you delete them in the app or remove app data. Server-side beta accounts, usage events, session history, and workflow memory are retained as needed to provide the beta, support, security, abuse prevention, analytics, and compliance. You can clear available session history in the app; contact hi@mouseover.ai to request account deletion, deletion of server-side records, or access removal.

Children

Mouseover is not intended for children under 13, and we do not knowingly collect information from children under 13.

Changes to this policy

If we change how we handle Google user data or other personal data, we will update this policy and, when required, notify users or request renewed consent before using data in a new way.

Contact

Contact hi@mouseover.ai to remove access, request deletion, get permission help, or ask a privacy question.