Google Calendar data

If you connect Google Calendar, Opser accesses your connected account identifier, calendar names and settings needed for synchronization, and events on calendars you select. Event data can include titles, descriptions, locations, start and end times, time zones, organizer and attendee details, response status, and meeting links. We store synchronized calendar and event records in your workspace to display your schedule and keep it up to date.

We use this information to display calendars, check scheduling conflicts, and carry out calendar actions such as creating, updating, or deleting events. Changes made through Opser can update Google Calendar and notify event attendees. Authorized AI actions can use the same Calendar features. Access remains subject to your Google permissions and workspace access controls.

The Calendar integration requests access to view your calendar list and view and edit events. It does not request the broader permission to manage Google calendar sharing or permanently delete entire Google calendars.

AI features and service providers

Before a mobile AI request or voice use on the web, Opser asks for permission if your account has not accepted the current AI disclosure. This covers sharing the relevant messages, files, voice audio, transcripts, conversation context and tool results with the services described in the consent notice. You can decline and continue using non-AI workspace features, or withdraw permission in Settings → Profile. Withdrawal requires another review before your next mobile AI request or web voice use; it also ends a voice call on the current screen. Web text chats and scheduled agent work continue. Withdrawal cannot recall information already sent, and authorized colleagues can still use shared workspace records. New recipients require an updated consent request.

When an AI assistant performs a task involving your Calendar, relevant event information may be included in the conversation and tool results sent to the selected model provider. For example, rescheduling a meeting can involve sending its title, time, and other returned details to that provider. This processing can occur even though the model does not connect directly to Google. Conversation history containing Calendar information may also be processed in later turns, including when you switch models.

Depending on the model and connections enabled in your workspace, AI processing may involve OpenAI, Anthropic, Google, xAI, or models accessed through OpenRouter. OpenRouter routes requests to model hosting providers; the recipient can vary by model and routing settings. Your selected provider processes prompts, relevant conversation context, and tool results to generate a response or carry out the requested task.

Mem0 processes information used for AI memory. Requested image or other media generation can use fal.ai. Dictation asks for AI sharing permission once per account and disclosure version. Each microphone press starts a visible recording; Opser sends audio to OpenAI through its server when you stop, or automatically after five minutes. Discarding a recording does not upload it. Integrations can send data to the services you connect when you authorize an action.

Live voice streams your microphone audio to OpenAI after you choose to start a call. Relevant chat context and agent results help it respond. Opser stores the conversation transcript in your chat, not a recording of the call. Ending a call stops microphone capture; withdrawing AI permission also ends live voice. Private voice transcripts are included in account deletion. Shared chat history remains with the workspace.

For requests routed through Opser’s managed OpenRouter account, we disable providers that train on request data and explicitly exclude DeepSeek as a hosting provider. DeepSeek models remain available through independent hosting providers, with routing restricted to endpoints classified by OpenRouter as supporting zero data retention. These restrictions concern the processing of requests; using a DeepSeek model does not mean sending data to DeepSeek’s own API.

We do not use Google user data, including derived or summarized data, to create, train, or improve generalized AI or machine learning models. We do not authorize service providers to use that data for generalized model training. Processing a request is separate from training a model; this policy does not promise that every service provider offers zero data retention.

Data protection and security

We protect personal information and sensitive connected-service data through technical and organizational controls:

• HTTPS encrypts traffic between your browser and Opser and the requests our Calendar integration makes to Composio and Google.
• Google authorization uses OAuth. You sign in with Google; Opser does not ask for or store your Google password. Composio manages OAuth access and refresh tokens server-side and encrypts those credentials at rest. The Calendar app stores a connection identifier rather than the OAuth tokens.
• Authentication, workspace roles, and record-level permission checks control access to stored Calendar data and actions. Separate business databases and private database networking help isolate workspace data and limit direct database access.
• Operational logging and backups support investigation and recovery. Human access to Google user data is limited to specific access you consent to, security investigations, or legal obligations permitted by Google's policies.

No method of transmission or storage is completely secure. If you have a security concern, contact [email protected].

Retention, disconnection, and deletion

You can delete your account in Settings → Profile → Delete account on the web or in the mobile app. Confirm with your current password or an email code. Access is revoked when the request is accepted; a private status link shows when cleanup finishes and continues working after sign-out. Cleanup normally takes minutes and retries automatically if a service is unavailable. See our account deletion guide.

Deletion removes your profile identifiers, sign-in methods, personal agent, private conversations and files, private memories, personal integration connections and private support records from active systems. It applies to the selected workspace; accounts in other workspaces are separate. Shared chats, apps and business records remain with an anonymous author reference. A required handover preserves administration and shared-agent ownership for colleagues. If you are the last member, shared agents are paused and the workspace subscription is cancelled; the workspace’s shared business data is not automatically destroyed.

Required billing records, minimal deletion records and information needed to meet legal obligations may be retained. Backup copies expire under the applicable retention schedule rather than being individually edited. Service providers may retain information under their own applicable terms and legal obligations. Deletion does not erase records already delivered to external services or content your organization must retain as shared business records.

We retain information as needed to provide the features you use, maintain your workspace, protect the service, and meet legal obligations. Synchronized Calendar records are maintained while the connection is active. Conversations and other workspace records have a separate lifecycle from the connected account.

You can disconnect Google Calendar in the Calendar app's connected-calendar settings. This stops synchronization for that connection and removes its synchronized calendars and events from the Calendar app. Disconnecting does not delete the original calendars or events in Google Calendar. You can also revoke Opser's Google access through your Google Account connections. Revoking access at Google alone does not delete information already stored in Opser.

Disconnecting Calendar does not automatically erase event information already included in chats, other workspace records, or service-provider logs. To request deletion of this information or your account data, contact [email protected] and identify the workspace and connected account involved. We may verify your identity and authority to make the request. Information subject to a legal or security retention obligation may be retained for that purpose, and backup copies may remain until those backups expire. Service-provider copies are subject to their applicable retention terms and deletion processes.

Google API Limited Use

Opser's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace API User Data and Developer Policy. These commitments apply to raw Google user data and data derived from it. They take precedence over any more general description of information use elsewhere in this policy.