Privacy Policy

Gemisis Canada operates the Gemisis service. This policy explains how we handle information on gemisis.ca and in Gemisis services, including account connections on app.gemisis.ca. The integration-specific sections below describe their data handling. Product descriptions on this website do not expand the permissions you grant to an integration.

For privacy questions, requests about your information, or support, use our Contact page. Tell us that your inquiry concerns privacy and the relevant service. Do not include passwords, access tokens, or sensitive message content in an initial inquiry.

Google, Microsoft, your organization, and independent services you choose to use have their own privacy responsibilities. Other Gemisis integrations may provide additional notices for their specific permissions and data handling.

When you contact us or request a call, we process the information you provide, such as your name, email address, organization, role, scheduling details, and inquiry. We use it to respond, arrange the requested conversation, and manage that relationship. Please share only what is needed for your inquiry.

Our website and delivery providers process technical information such as IP addresses, browser and device information, requested pages, timestamps, and diagnostic events to deliver and protect the website. Website analytics help us understand visits and page usage. These technical records are different from the content of your Teams messages.

Browser storage may support essential site or sign-in functions. Our booking form sends your name, email address, optional message, selected time, and time zone directly to Gemisis. Authorized Gemisis personnel review the request and arrange any meeting details. Booking requests do not automatically send invitations or emails. You can manage browser storage through your browser settings; blocking it can affect some features.

When you connect Google, we process your Google account identifier, email address, display name, granted permissions, connection status and timestamps, and the link to your Gemisis account. Google handles your Google password; Gemisis does not receive it. Authorization credentials maintain the connection. Stored server refresh credentials are encrypted, and short-lived access credentials are used for the authorized operation.

Gmail checks use email metadata, including sender addresses and names, sender and reply-to headers, authentication results, receipt times, and message references. The add-on uses Google's temporary current-message permission to check the email you open. Mailbox metadata synchronization stores selected header observations and a keyed message fingerprint. These features do not request email bodies or attachments and cannot send, modify, or delete your emails using their requested permissions.

Google Meet checks use the current meeting reference, Google's participant identifiers and display names, and current participation information. We check that the connected Google account is present in that meeting. Google does not disclose every participant's email address. Where a Google participant identifier matches a current Gemisis connection or applicable organization registration, an authorized participant can see the associated registered email, connection date, and account-match result. We do not infer email addresses from display names. Meeting rosters are processed for the current check rather than stored as attendance history. We do not request Meet audio, video, recordings, transcripts, captions, or chat content.

We use Google data to provide these visible account-connection and communication checks, manage authorization, and protect and troubleshoot the service. Public-source domain research is a separate result: it does not prove a mailbox, employment, organizational authority, or the origin of a particular communication. Support reports may contain the affected connected account, platform, error code, and safe diagnostic context; backend failures for eligible signed-in connected accounts may also be reported automatically to authorized Gemisis support personnel. Reports must not include provider credentials or email bodies.

Gemisis's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google user data, use it for advertising, use it to train general-purpose AI models, or use it to determine creditworthiness. Human access is limited to your affirmative permission for specific data, necessary security investigations, legal requirements, or permitted aggregated internal operations. Transfers are limited to providing the consented visible features, security purposes, legal requirements, or a qualifying business transfer with the consent Google requires.

Google connection records remain while needed to operate and protect the connection. Gmail synchronization removes observations older than 90 days when its cleanup runs; this is not a guarantee of erasure at the exact deadline. Disconnecting Gmail removes its active connection and associated mailbox metadata through the disconnect workflow. Disconnecting Meet clears its stored refresh credential and marks that connection revoked; non-secret connection and audit records may remain for operational or security purposes. Technical logs, support records, backups, and Google's own records have separate lifecycles. Use our Contact page to request deletion or ask which records remain. You can also remove consent through your Google Account connections. Removing Google app access may affect more than one Google integration.

When you connect a Microsoft work or school account, we store its Microsoft tenant and account identifiers, display name, email or sign-in address, connection timestamps, and the identifier of your Gemisis account. The connection is matched by Microsoft account identifiers, rather than by a typed email address alone.

Microsoft supplies authorization tokens so we can maintain the connection and check whether access remains valid. Refresh credentials are encrypted before storage. Short-lived access tokens are processed for the requested operation. Your Microsoft password is entered with Microsoft and is not received by this integration.

A selected-message check uses sender and viewer identifiers, a display name, and message and conversation references. Microsoft may include a message body or attachment fields in the activity delivered to the integration. Gemisis discards those fields when it creates the check context; it does not save message bodies or attachments as part of the check.

Meeting checks use meeting references, participant identifiers and display names, conversation membership, and current participation information supplied by Microsoft. The integration does not request mailbox contents, recordings, transcripts, audio, or video. Rosters and presence responses are processed for the requested check rather than saved as an attendance history.

Where message-origin checking is supported, Gemisis compares the received communication's metadata with a sender-side record tied to that outgoing communication. This is distinct from checking account control or associating a domain with a company. A domain association alone does not confirm that a particular message came from that company.

We use this information to connect and manage accounts, authenticate people using the integration, check Microsoft-provided communication context, evaluate the current connection, prevent unauthorized access and abuse, and handle support or privacy requests. We do not use Teams message content for advertising or to train AI models.

Connecting an account allows an eligible person checking your selected message or meeting participation to learn whether that Microsoft account has a current Gemisis connection. A result can include a limited display name, the check time, a Microsoft context result, and a Gemisis connection result. It does not reveal your authorization credentials or private connection record.

Checks require the relevant conversation access or current meeting participation. Message results appear in a private dialog rather than being posted to the entire channel. Connection status is not offered as a general public people-search directory.

A confirmed account or communication context does not establish legal identity, employment, organizational authority, or good intentions. An account with no current connection may appear as not registered; that is not a finding that the person or message is fraudulent.

• People performing authorized checks receive the limited results described above, subject to the communication-access checks.
• Google processes Google sign-in and the authorized Gmail or Meet API requests needed for the Google integrations, under its own terms and privacy policy.
• Microsoft processes the sign-in, account-details, and permitted conversation or meeting requests needed for the Teams integration, under its own applicable terms and privacy notices.
• Service providers process information needed to host and store the service, deliver website content, provide analytics and diagnostics, arrange calls, and support security and operations. Their access is related to those functions.
• Authorized Gemisis personnel may handle information when necessary to operate the service or respond to a support, security, or privacy issue.
• Legally required recipients may receive information where disclosure is required by applicable law or valid legal process.

We do not make your private connection credentials public. Following a link to another service, or using its embedded features, also brings that service's own privacy practices into scope for the information it receives.

The Google and Teams integrations' primary application database is configured in Canada. This is not a promise that every backup, technical log, support activity, or Microsoft operation takes place exclusively in Canada. Google, Microsoft, and other service providers may process information in other countries, where it can be subject to local laws.

Safeguards include encrypted network connections, encryption of stored Teams refresh credentials and temporary check contexts, server-side validation of Microsoft tokens, restricted access to connection data, expiring authentication contexts, and request limits. The Teams integration's application error logs use fixed error codes rather than intentionally logging message contents or provider tokens. Website and infrastructure diagnostics are handled separately.

No security measure eliminates all risk. A valid account may itself be compromised, and a positive check does not guarantee that a communication or transaction is safe.

We retain information for the purpose for which it was collected, including providing an active connection, responding to an inquiry, protecting the service, and meeting applicable obligations. Different records have different lifecycles:

• Teams connections: the active binding and encrypted refresh credential remain while the account is connected. Disconnecting it in Gemisis deletes that binding and credential and removes pending Teams sign-in records for the same Gemisis account. It does not disconnect Outlook or another provider.
• Sign-in attempts: authorization state is usable for ten minutes and only once. Successful or cancelled attempts are removed by the connection flow. Abandoned or unsuccessful attempts can remain until later cleanup for that account, disconnection, or account deletion; expiration is not immediate physical erasure.
• Message checks: the encrypted context is usable for five minutes, bound to the invoking Microsoft user, and not stored in the connection database. The app removes it from the page URL and holds it in memory while open.
• Meeting information: roster and presence responses are processed for the current request, rather than kept as a meeting-attendance history.
• Abuse-prevention records: short-lived request-limit records use digest-based identifiers. Expired windows are removed on a later request that runs cleanup. These identifiers are not described as anonymous.
• Inquiries, technical logs, and backups: retention depends on their operational purpose, the applicable provider, and legal or security requirements. Deleting an active connection does not promise immediate removal from every existing backup or third-party system. Contact us about the records relevant to your request and any retention that applies.

Revoking Microsoft access can make a connection require reconnection; it is separate from deleting the connection in Gemisis. You can also review or remove Microsoft app consent through Microsoft's controls, subject to your organization's policies. Neither action deletes Microsoft's own records.

You may decline to connect an account, disconnect it, review Google or Microsoft app consent, or manage browser storage. Some features cannot work without the information or permissions needed to provide them. Your organization may also restrict installation or access.

Use our Contact page to request access to, correction of, or deletion of your information, withdraw consent where applicable, or raise a privacy concern. Identify the service and account concerned without sending credentials. We may ask for proportionate information to verify your authority to make the request.

We handle requests according to applicable law and explain any lawful restriction on fulfilling them. Where applicable, you may also raise a concern with your relevant privacy regulator. Contacting us about a request does not require a paid Gemisis plan.

We update this page when our practices change and show the revision date above. Where applicable law requires additional notice or consent for a material change, that requirement applies. Questions can be raised through our Contact page.

Read our Terms of Use for the service's use and verification limitations.