Effective date: October 16, 2026.
Website analytics update: October 27, 2026.
Who operates Conloq
Conloq is a product of Tenexeon, operated by Gordon Olson as an individual. In this policy, “Conloq,” “we,” and “us” refer to that operator and the Conloq service. Contact the Conloq Team at support@tenexeon.com for questions about this policy or privacy requests.
This policy covers the Conloq website, applications, connected mail and calendar features, Do AI, and Conloq’s Room and agent connection features. It explains the information these features use, who receives it, and the controls available to you. Google, Microsoft, other connected services, other Room participants, and independently operated agents also have their own practices. Authorizing access through Conloq does not make those independent services part of Conloq.
Account and application information
When you sign in and use Conloq, we process your account identifier, email address and verification status, workspace and membership information, display names, preferences, and access permissions. Authentication services process the credentials and verification information you provide to sign in. Conloq also processes session credentials and, when you choose to remain signed in, a saved session that can renew your access.
We process the content you create or submit, including drafts, recipients, attachments, calendar changes, workspace instructions, agent configuration, and support requests. Commands and action receipts record information such as the actor, affected resource, requested operation, authorization decision, status, and time. These records help enforce permissions, reconcile interrupted operations, and show what happened.
Connections to the service produce technical information such as request and connection identifiers, network addresses, device or browser information, timestamps, failures, and operational measurements. We use this information to operate the service, investigate faults, prevent unauthorized access and abuse, and maintain security. Do not include passwords or provider authorization tokens in support messages, Room chat, or agent instructions.
Connected email and calendars
You decide whether to connect supported Google or Microsoft accounts. Conloq directs you to the provider’s sign-in and permission page. Mail and Calendar have separate authorization steps, so connecting mail does not by itself authorize Calendar access. Apple connections are coming soon and are not currently offered.
For connected mail, Conloq processes the account identity and email address, folders and labels, message identifiers and headers, message content, recipient information, and attachments. We use these to synchronize, display, search and organize mail, prepare drafts, and send messages through your connected provider when you request a send action. Organization and send actions can affect your provider’s mailbox; changes to a Conloq view or stored copy are not always the same as deleting provider-side mail.
For connected calendars, Conloq processes your calendar list and identifiers, your selected calendars, event details, and synchronization information. Event details can include titles, descriptions, times, locations, recurrence, organizer and attendee information. We use these to display and synchronize selected events and carry out the event creation, edits or deletion you request. A provider-side event change is separate from removing a Conloq copy.
Conloq stores synchronized mail, attachment and event copies in the workspace where you connected the account. These copies support reading, search, synchronization and authorized productivity assistance. They are not erased merely because synchronization stops or provider authorization is removed.
We store authorization tokens on the server so your connection can continue without a new provider sign-in for every operation. Token storage uses encryption with a workspace-specific encryption context. An authorized agent calls Conloq tools; it is not given your Google or Microsoft refresh token. Provider client secrets and refresh tokens are not included in Room invitation instructions.
Your provider’s consent page identifies the permissions requested. A connection you save in Conloq is reused by the app, built-in Do AI and Conloq MCP agents you authorize. You do not need a second Google or Microsoft connection solely because an agent performs an authorized Conloq action. Provider authorization and the permissions you grant an agent inside Conloq remain separate controls.
Do AI and outside agents
The current built-in Do AI runtime performs model inference locally in your browser or supported device runtime. It may use content selected from the account and workspace that you allow it to access to understand your request, produce a response or draft, and choose a Conloq tool. Local inference does not make a resulting tool operation local: synchronizing mail, sending a message, changing an event, or using a Room can still involve Conloq and the relevant service providers.
Outside agents can connect through authorized Conloq MCP or HTTP interfaces. Their access is controlled by their Conloq identity, the workspace and resources you permit, and the available action permissions. An invitation to a Room does not grant mailbox or calendar access. Granting access to synchronized copies is meaningful even after the original provider connection is disconnected, because those copies may still exist in Conloq.
When you authorize an outside agent to read content, the agent operator receives the tool results or Room information that its permissions allow. The operator may process those results in its own computer, virtual machine, agent software or model service. Its model provider is an additional recipient selected by that operator, rather than the local Do runtime. An agent may also send content to an external service as part of an action you request.
Review the agent’s identity, requested access and data practices before granting access. Limit access to the work you intend and remove it when no longer needed. Revoking Conloq access stops future authorized access; it cannot recall a result already delivered to another participant, agent or service. Conloq does not represent that every outside model has the same retention terms or that every outside operator has a no-training agreement.
Rooms, live speech and screen sharing
Rooms process Room and meeting identifiers, invitations, participant identities and display names, presence, permissions, and connection status. When you use a microphone or camera, or share a screen, the media you publish is delivered to the participants and agents permitted to receive it. Room chat messages are likewise delivered to their permitted audience. A display, application window or browser tab you share can contain email, calendar information, notifications and other personal information visible on that surface.
If Room speech assistance is enabled and permitted, Conloq’s speech service can process your audio to produce live recognized text, deliver that text to admitted agents, and synthesize spoken replies. An agent using its own audio capabilities may instead receive the audio allowed by its Room permissions and process it through its own runtime or provider. Turning on agent speech therefore involves processing even in a meeting that is not being recorded.
The private, unrecorded live-voice path uses short-lived audio and caption buffers to deliver the conversation. It does not automatically save that live audio or create a retained transcript. Its performance measurements record operational timings rather than audio or transcript text. This description concerns Conloq’s live-voice path; it does not prevent recipients from retaining information they receive or describe the separate saved-transcript features below.
Screen sharing remains visible while the authorized share is active. Agents can publish selected screen frames or share a browser, application or full display through their companion or computer runtime. Conloq’s frame-publishing path holds the current image for delivery while sharing; it is separate from a saved recording. Stop sharing to stop future screen delivery. Muting your microphone controls your microphone, not an agent’s independent screen share or replies.
Saved recordings and transcripts
Conloq also supports a separate recorded-workspace meeting mode. Recording requires a recording request and acceptance from the current participants covered by that meeting’s consent controls. The recording worker checks those consents before starting and again during its operation. The app’s recording status distinguishes a requested, active or processing recording from an unrecorded meeting.
A saved recording may contain participants’ audio, video and shared screen content. The recording service creates the media artifact and Conloq stores the artifact and associated metadata for authorized workspace access. Recording consent and status records are also stored.
Saved transcript features can store recognized or imported text, speaker and meeting references, segment timing, source information and related metadata in the workspace. Explicit transcript creation or import is separate from the transient caption delivery used for live agent speech. A “private, unrecorded” live call should not be understood as a promise that no participant or separately authorized transcript feature can ever save text.
Authorized recording or transcript deletion controls remove the affected Conloq artifact through their respective operation paths. Ending a meeting, muting, disconnecting a participant, or removing a provider authorization does not by itself delete a saved artifact. The retention and request choices below also apply to stored recordings and transcripts.
Who receives information
Conloq uses service providers for application infrastructure, sign-in, connected mail and calendars, meetings, voice processing and billing when available.
Providers receive the information needed for the function they perform. For example, speech recognition processes audio, synthesis processes the text to be spoken, and a connected mail provider processes the messages and mailbox operations you request. The local Do model is distinct from these services. Outside agents and their selected model or computer providers receive information as described in the agent section.
Workspace members, Room participants, message recipients, event invitees and agents may receive information when you share it or authorize an operation that supplies it to them. Their ability to retain or use received information can extend beyond their subsequent access to Conloq. Support communications are received by the Conloq operator and the email services used to handle them.
Information is processed on your device and in the infrastructure used by Conloq and these recipients, which may be in a different country from yours. The application database is hosted on infrastructure in the United States. Other processing locations depend on the service and recipient used. We do not promise that all information stays in one region or that every provider retains it for the same period.
Google data and Limited Use
Conloq’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. We use Google-derived information for the disclosed, user-facing mail, calendar and authorized productivity features. We do not sell this information or use it for advertising, credit decisions, or training or improving general-purpose AI models.
Transfers and human access are limited to permitted purposes under that policy, including the required user consent. Providers and agents receiving Google-derived information through Conloq must observe the applicable restrictions. Support access to specific Google-derived content requires the permission or other permitted circumstance required by the policy. Consent to a Conloq account connection or Room is not blanket permission for unrelated use of your Google information. The additional Google Workspace user data and developer policy also governs applicable Workspace data.
Storage, retention and deletion requests
We retain synchronized copies and user-created workspace content to provide the functions described here. Current attachment handling is configured to retain copies rather than delete them on a routine age-based schedule. Stored recordings and transcripts are separate from transient live buffers. Retention does not constitute a guarantee of permanent archival storage or recovery of every item that existed at your provider.
Disconnecting a mailbox in Conloq stops synchronization and sending while leaving its saved provider authorization available for reconnection. Removing authorization in Conloq removes its locally stored token material and disables associated mailboxes or calendars. You can separately remove Conloq’s access in your Google or Microsoft account settings. These controls do not delete previously synchronized copies, do not erase information already delivered to an outside agent, and do not delete mail or events at your provider.
Disconnecting a connection, signing out or clearing a device cache does not delete your server-held account or stored content. Use the privacy controls available in your shared Tenexeon account, or contact us to request deletion. Available controls can differ by account and product; a request is not complete until its scope and result have been confirmed.
To request access to your information or deletion, contact support@tenexeon.com. Identify the affected Conloq account and whether you want to remove one connected account’s Conloq copies, clear Conloq data while retaining your account, or delete your full Conloq account. These are different request scopes. Do not send a password or provider token. We may need to verify your identity and authority and clarify content shared with other workspace members before processing the request.
Deletion of active content and the treatment of backup, security and operation records are different parts of a request. Some records may need to remain for security, unresolved operations or applicable legal requirements. Information already sent to recipients or independently operated agents is outside Conloq’s direct deletion controls. We will describe the scope and any applicable limitations when responding to a request rather than treating disconnecting OAuth as completed erasure. This policy does not promise a numerical deletion deadline or universal immediate removal from every backup and recipient.
Depending on the law that applies to you, you may have rights to request access, correction, deletion or a copy of your personal information, to object to or restrict certain processing, or to withdraw consent. Use the same contact address for these requests. Withdrawing authorization stops the relevant future access; it does not reverse an operation already performed.
Optional website analytics and your choices
The public Conloq marketing website offers optional Google Analytics 4 measurement when the website property is configured. We do not load its tag or send optional analytics before you affirmatively allow analytics. Rejecting or dismissing the choice keeps it off and does not prevent you from using the site or creating an account. A Global Privacy Control or Do Not Track browser signal also keeps optional website analytics off. Advertising pixels, advertising personalization and session replay are not enabled by this website setup.
When permitted, website measurement covers public page names, approved campaign labels and clicks on account-creation links. Join clicks are not completed accounts. After consent, Google also records standard session, first-visit and engagement events. This website does not send email or Room content, names, email addresses, account IDs, raw query strings, invitation tokens or arbitrary campaign text to website analytics. Google receives connection information needed to process an analytics request, including the network address, and can derive general device and geographic information. See Google’s explanation of partner-site information.
The website remembers your privacy choice in first-party browser storage for up to 180 days. If you consent, Google Analytics cookies are configured for a 30-day lifetime, and approved campaign labels can be kept in tab-scoped session storage. Website fonts are served from this website, without a Google Fonts request. Technical hosting and security records are separate from optional analytics.
Use Privacy and analytics choices, available from the website footer and privacy control, to change your choice, stop future collection, or clear accessible analytics cookies and campaign storage from this browser. Clearing browser analytics data does not delete your Conloq account, application data, or information already held by Google. Prepare a historical analytics deletion request before clearing if you want to retain your browser’s analytics reference for that request.
For historical website analytics access or deletion, use the request controls or contact support@tenexeon.com. The team may need your analytics reference and verification of the request. A prepared or emailed request is not confirmation of provider-side deletion; we must process it through the provider’s tools and confirm the result and any limits. Google’s aggregated reports are separate from user-level deletion. The website does not promise that clearing cookies erases historical analytics or that consented metrics represent every visitor.
Cookies, device caches and security
Conloq uses browser or device storage for application preferences, local account caches and the state needed to display and synchronize workspace data. The browser cache uses account-specific browser storage; supported native applications use their device cache facilities. A local cache can contain personal workspace information. Your browser, device controls and Conloq’s available cache controls affect that storage. Clearing a device cache is separate from deleting server-side content or provider-side information.
When “Keep me signed in” is available and selected, Conloq uses a session cookie and an encrypted server-held refresh credential. A session cookie is separate from the provider mail and calendar grants. Signing out ends application access and initiates account-local cleanup, but it should not be treated as a deletion request for your Conloq account or stored workspace content.
Conloq uses authorization controls, encrypted connections and protected credential storage. Workspace and agent permissions constrain access to resources and actions. Attachment safety processing can inspect uploaded or synchronized files, hold them for scanning, and record safety status and metadata before permitted use. Security and operation records can outlast a particular active session. No security measure makes every device, recipient or service immune from unauthorized access; protect your devices and review the access you grant.
Changes and contact
We may update this policy when features or information handling change. The published policy will show its effective date. Where a change requires additional disclosure or consent, we will provide that before the changed processing rather than relying only on an updated policy page.
For privacy questions and requests, contact the Conloq Team at support@tenexeon.com.