HTTPSGate Platform — Google User Data

Updated October 25, 2026. HTTPSGate Platform is operated under the company policies of Zahyan Technologies. The following specific provisions apply to Google sign-in and Google Calendar data and take precedence over any broader website, analytics, marketing, or product-improvement purposes described elsewhere in this policy. Those broader purposes do not authorize advertising, sale, or generalized AI model training using Google user data.

This section explains how HTTPSGate Platform handles information received through Google sign-in and Google Calendar. It applies to these integrations within our multi-tenant customer relationship management and scheduling application.

Information we receive

When you choose Google sign-in, we request your Google account identifier, verified email address, and basic profile information. We store the identifier and email to associate your identity with an existing application account and workspace. We do not request your Google password.

When you separately connect Google Calendar, we receive OAuth access credentials and information from calendar events, including event identifiers, titles, descriptions, start/end times, and meeting or conference links. Calendar responses may contain other event details; our current synchronization stores the fields needed for meeting display, conflict checking, and synchronization. We also store the connected account email and connection/synchronization settings.

These integrations do not request access to Gmail messages, Google Drive documents, or Google Photos. Connecting Google Calendar is separate from signing in with Google.

Why we use this information

We use Google sign-in information to authenticate you and associate your account with its authorized workspace. We use Calendar information to display synchronized meetings, check scheduling conflicts, synchronize user-requested meetings, and create calendar events with Google Meet links. Workspace administrators control the workspace integration and its local meeting copies.

We do not sell Google user data, use it for advertising or retargeting, disclose it to data brokers, or use it to determine creditworthiness. We do not use Google user data for unrelated product development or generalized model training.

AI and Limited Use

We prohibit using raw, aggregated, anonymized, or derived Google Workspace user data to create, train, improve, or fine-tune generalized or foundational AI/ML models. We do not authorize third-party providers to use Google user data for those purposes.

The platform's configured third-party AI provider is Mistral's API. Its account is currently on the Free tier; provider training opt-out has not been verified. AI processing is therefore blocked in workspaces containing Google-connected identities or synchronized Google Calendar data. Google sign-in and Calendar functionality remain available. Google-tagged meeting records are also excluded from server-built AI context. We will not enable a Google-data AI workflow unless its processing arrangement and controls have been verified and appropriate disclosures provided.

A configured local-model address does not establish that a model is operating offline. We do not represent the Mistral cloud API as a self-hosted service.

HTTPSGate Platform's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Access and sharing

Google processes requests necessary to provide the integrations you authorize. Within the application, information is associated with the authorized workspace. We restrict administrative and support access to what is necessary to operate the requested service, investigate security incidents, comply with law, or assist you with your authorization. We do not permit staff to access Google data for unrelated purposes.

We use infrastructure providers to operate the application and its storage. We do not give those providers permission to use Google data for advertising or generalized AI model training. Workspace administrators and other workspace members may see meeting information according to the application's permissions and workspace configuration.

Protection

We use HTTPS for application and Google API communications, authenticated application access, workspace scoping, and restricted administrative access. Calendar credentials are omitted from customer-facing configuration responses. We do not publish credentials in demonstration videos or public documentation.

This policy does not claim a security certification or an unverified storage-encryption guarantee. No internet service can guarantee absolute security.

Retention

• Sign-in identity: retained while the associated account exists and needs Google sign-in, until the identity is unlinked or a verified deletion request is completed.
• Calendar credentials: retained while the integration is connected. Disconnect removes stored access/refresh tokens from the active configuration and stops subsequent synchronization using those credentials. Removing local tokens is distinct from revoking access in your Google account.
• Local meeting copies: retained to provide workspace scheduling and CRM history until the relevant copies are deleted by an authorized administrator or a verified deletion request is completed. Disconnecting alone does not delete existing meeting copies.
• AI or other derived copies: if a verified deletion request identifies Google-derived copies retained from earlier processing, those copies must be included in the deletion review; disconnect alone does not establish that historic copies have been removed.
• Backups: restricted recovery backups may contain prior copies after removal from the active application. A deletion request is not considered complete until applicable recovery copies have been removed or the requested data has been permanently excluded from restoration. We do not treat a disconnect action as proof of backup deletion.

We retain only any minimum record required to document fulfillment of a request, investigate a security incident, or meet an applicable legal obligation. Such retention does not permit unrelated use or generalized AI model training.

Disconnect, revoke, and request deletion

You may disconnect Google Calendar under CRM → Meetings → Integrations. You may also revoke the application's access using the third-party connections controls in your Google account. Revoking access at Google does not by itself delete information already stored in the application.

To request removal of sign-in information, Calendar meeting copies, or all Google-derived data associated with your account/workspace, contact the support address shown on our Google consent screen: maulinrozia0@gmail.com. State which account/workspace and which categories you want deleted. Do not send passwords, access tokens, or verification codes. We may require confirmation that you control the account or are authorized to act for the workspace.

We will respond to and act on verified requests as follows: we will complete a verified Google-data deletion request within 30 days, including applicable active and recovery copies, and confirm completion. If a specific legal obligation prevents removal of a limited record, we will explain the exception and restrict further use to that obligation. We will not confirm completion merely because access was disconnected or tokens were removed.

Deleting local application copies does not delete the original events in your Google Calendar unless you separately choose a supported Google event-deletion action. We will explain the scope of any deletion before performing it.

Changes and contact

We will update this policy when Google-data processing changes and provide additional notice or obtain consent where required. Questions or requests may be sent to the support address above.

Related company policies: Terms and Conditions, Cookie Policy, and Corporate Social Responsibility Policy.