Effective Date: November 02, 2026
This document provides an overview of the security architecture, governance framework, and operational safeguards for the Synergy SKY CONNECT service. Building on Synergy SKY’s commitment to digital trust, the following sections outline how various components and features of CONNECT handles data, manages access, and enforces compliance measures while maintaining confidentiality, integrity, and availability of its services.
The scope of this document is the CONNECT service and its associated components when delivered as a cloud solution. Where possible and where certain security related topics are depending on features, these are described independently, for instance regarding user-facing webpages and calendar integration (via Microsoft Graph API and Azure Applications). Where relevant, the document references Synergy SKY’s Information Security Management System (ISMS) which is certified to ISO/IEC 27001. This whitepaper does not address third-party services outside of the direct operational requirements for CONNECT.
The Click to JOIN and Join by ID components are also available in a Hybrid deployment, where they run on infrastructure owned and controlled by the customer. This is described in the section CONNECT – Hybrid Deployment. Unless stated otherwise, the rest of this document describes the cloud deployment.
CONNECT – Click to JOIN follows these primary steps:
CONNECT – JOIN by ID follows these primary steps:
CONNECT – Scan to JOIN / GO follows these primary steps:
The CONNECT platform consists of the following main services or features.
Data retention and protection measures within CONNECT ensure that user information is managed responsibly and securely at every stage of its lifecycle. By employing stringent cryptographic methods, enforcing defined retention periods, and adhering to ISO 27001 requirements, the service protects sensitive data from unauthorized access and fosters confidence in its security posture.
Encryption is employed both in transit and at rest, allowing data transmissions (e.g., QR link, OAuth tokens, meeting hyperlink) to remain secure throughout the user’s interaction with the CONNECT platform, as well as for all API integrations the CONNECT platform has with other third-party services. By leveraging TLS protocols and industry-standard cryptographic algorithms, Synergy SKY maintains confidentiality and integrity of information as it moves between devices and services. Data at rest, including any stored logs or retained meeting details, is likewise protected using encryption mechanisms that align with recognized international standards.
For every meeting that is provisioned, and that is classified as a supported meeting by CONNECT, a gateway is made available to handle incoming video calls to this meeting. The information stored in this process of provisioning a gateway is:
This metadata is stored in an encrypted database, using AES-256. And all data in transit to and from the database is encrypted using TLS 1.2/1.3
Meeting metadata is retained for 30 days after end of scheduled meeting time or end of last usage of the meeting, before automatic deletion. Call logs are retained for 14 days before automatic deletion.
Room calendars are parsed within a window set from now 180 days into the future. During this process required metadata is gathered and processed, and is retained by Click to JOIN until the end of the scheduled meeting time. When a meeting is provisioned, the details needed to connect a video system (meeting type, meeting ID, password, joining link, and meeting start time and duration) are passed to the CONNECT Gateway. The Gateway retains these details for a maximum of 30 days after the end of the meeting or for a maximum of 30 days after the last usage of the meeting. This window balances the need for the meeting to be accessible even after its scheduled end, and the need for it to be made inaccessible if not used regularly. Also, 30 days is a reasonable time window to accommodate customer support and ensure a robust audit trail in the event of service inquiries or incident analysis.
CONNECT Easy-Join integrates Microsoft Graph or Google API as its primary interface for accessing user and organizational data within Microsoft 365. This integration enables secure, programmatic access to services such as Outlook or Google calendars, user profiles, and directory information through a unified API. Access to Graph endpoints is governed by the delegated and application permissions as set in the table below. Access to Google Workspace is governed by the OAuth scopes as set in the table below. Both these methods ensure tight coupling between identity verification and data access. The service adheres to Microsoft Graph’s or Google's permission scopes and employs granular access control to request only the minimum necessary privileges, minimizing exposure risk. To maintain operational integrity, all API calls are authenticated using OAuth tokens that are subject to the default token lifecycle policies as defined by Microsoft 365 or Google, ensuring that data access is both secure and auditable
|
Microsoft 365 Permission |
Description |
|
Calendars.ReadWrite (Application) |
Read and write calendars in all mailboxes |
|
Mail.Send (Application) |
Send mail as any user |
|
User.Read.All (Application) |
Read all users' full profiles |
|
Place.Read.All (Application) - Optional |
Allows the app to read company places (conference rooms and room lists) for calendar events and other applications, without a signed-in user. |
|
Google API Scope |
Description |
|
/auth/admin.directory.resource.calendar.readonly |
View calendar resources on your domain. |
|
/auth/calendar |
See, edit, share, and permanently delete all the calendars you can access using Google Calendar. |
|
/auth/gmail.send |
Send email on your behalf. |
|
/auth/calendar.events |
View and edit events on all your calendars. |
This section describes the journey of data within CONNECT Click to JOIN, beginning with calendar processing and ending with the conclusion of a video meeting. By examining each stage of this flow, we highlight how data is processed, transmitted, stored, and ultimately retired in accordance with security best practices and Synergy SKY’s ISO 27001-aligned policies. These are described in the following sections:
Calendar processing is continuously done according to the access and permission rights as defined above in the IAM section. CONNECT Click to JOIN is at most processing meetings that are 180 days into the future. For every meeting that is processed, and that is classified as a supported meeting by CONNECT Click to JOIN, the following information is stored:
This metadata is stored in an encrypted database, using AES-256. And all data in transit to and from the database is encrypted using TLS 1.2/1.3. All communications between calendar services like Microsoft Graph and CONNECT Easy-Join are encrypted using TLS 1.2/1.3.
In the cloud deployment, meeting metadata held by Click to JOIN is removed at the end of the scheduled meeting time. In the Hybrid deployment it is archived, as described in CONNECT – Hybrid Deployment. Meeting details held by the CONNECT Gateway are retained for 30 days after end of scheduled meeting time or end of last usage of the meeting, before automatic deletion. Call logs are retained for 14 days before automatic deletion.
User calendars are parsed with a window set to 2 hours into the past and 24 hours into the future. During this process the gathered Meeting metadata consists of meeting Joining link, its associated Meeting ID and Password. No user data is collected by the JOIN by ID component. This metadata is retained by Join by ID until the end of the scheduled meeting time. The CONNECT Gateway, which handles the incoming video call, retains the meeting details for a maximum of 30 days after the end of the meeting or for a maximum of 30 days after the last usage of the meeting. This window balances the need for the meeting to be accessible even after its scheduled end, and the need for it to be made inaccessible if not used regularly. Also, 30 days is a reasonable time window to accommodate customer support and ensure a robust audit trail in the event of service inquiries or incident analysis.
CONNECT JOIN by ID integrates Microsoft Graph as its primary interface for accessing user and organizational data within Microsoft 365. This integration enables secure, programmatic access to services such as Outlook calendars, user profiles, and directory information through a unified API. Access to Graph endpoints is governed by the delegated and application permissions as set in table below, ensuring tight coupling between identity verification and data access. The service adheres to Microsoft Graph’s permission scopes and employs granular access control to request only the minimum necessary privileges, minimizing exposure risk. To maintain operational integrity, all Graph API calls are authenticated using OAuth tokens that are subject to the default token lifecycle policies as defined by Microsoft 365, ensuring that data access is both secure and auditable
|
Permission |
Description |
|
Calendars.Read (Application) |
Read user calendars |
|
GroupMember.Read.All (Application) |
Ability to read Entra groups and who is within each group |
|
User.ReadBasic.All (Application) |
Ability to read Principal name for members of an Entra group |
|
User.Read (Delegated) |
Sign in and read user profile |
This section describes the journey of data within CONNECT JOIN by ID, beginning with calendar processing and ending with the conclusion of a video meeting. By examining each stage of this flow, we highlight how data is processed, transmitted, stored, and ultimately retired in accordance with security best practices and Synergy SKY’s ISO 27001-aligned policies.
Calendar processing is continuously done according to the access and permission rights as defined above in the IAM section. CONNECT JOIN by ID is at most processing meetings that are 24 hours into the future. For every meeting that is processed, and that is classified as a supported meeting by CONNECT, a gateway is provisioned ready to handle incoming video calls to this meeting. The information stored in this process of provisioning a gateway is:
This metadata is stored in an encrypted database, using AES-256. And all data in transit to and from the database is encrypted using TLS 1.2/1.3
In the cloud deployment, meeting metadata held by Join by ID is removed at the end of the scheduled meeting time. In the Hybrid deployment it is archived, as described in CONNECT – Hybrid Deployment. Meeting details held by the CONNECT Gateway are retained for 30 days after end of scheduled meeting time or end of last usage of the meeting, before automatic deletion. Call logs are retained for 14 days before automatic deletion.
User metadata consists of a hashed version of the user’s email address, which is retained for a maximum of 30 days. This window balances support needs with the principle of minimal retention, reducing the risk of unnecessary data exposure. Similarly, meeting credentials and other connection details—such as meeting passwords and IDs—are maintained by CONNECT for 30 days to accommodate customer support and ensure a robust audit trail in the event of service inquiries or incident analysis.
CONNECT Scan to JOIN employs a robust identity and access management model by leveraging Microsoft Entra as its authentication backbone and by enforcing best practices for token handling. The service requires admin approval of user consent to delegated permissions, ensuring that individuals specifically agree to share their calendar data. If enterprise policies demand additional restrictions, administrators can set consent requirements that align with organizational risk thresholds and governance standards. Within the CONNECT Scan to JOIN environment, OAuth tokens, refresh tokens, and related credentials are managed under strict lifecycle rules. These tokens expire at intervals defined by Microsoft Entra configurations, forcing re-authentication and thus reducing the risk of perpetually valid sessions.
|
Permission |
Description |
|
Calendars.Read (Delegated) |
Read user calendars |
|
User.Read (Delegated) |
Sign in and read user profile |
This section describes the journey of data within CONNECT Scan to JOIN, beginning with QR code creation and ending with the conclusion of a video meeting. By examining each stage of this flow, we highlight how data is generated, transmitted, stored, and ultimately retired in accordance with security best practices and Synergy SKY’s ISO 27001-aligned policies. These are described in the following sections:
At the initiation of a call, CONNECT creates a unique QR code that it displays on the video system’s screen. This code is valid only for the current session and is designed to become invalid once scanned, thereby eliminating opportunities for malicious reuse. Because it appears on a physically restricted screen, the QR code remains visible only to authorized individuals within the meeting room, and only until scanned. In addition, the QR code is delivered via an encrypted video stream, preventing external interception. This transmission method enhances security by ensuring that no static QR codes are exposed, reducing the risk of social engineering attacks.
After scanning the QR code, the user is directed to the CONNECT Scan to JOIN webpage, which integrates with Microsoft Entra for identity verification. Single Sign-On and Multi-Factor-Authentication is handled as per the company's Microsoft Entra configuration. When authentication is successful, the various access and refresh tokens are issued by Microsoft Entra and cached within the CONNECT Scan to JOIN environment. These tokens adhere to the configured token lifetimes as set by the Microsoft Entra policies within the organization, promoting secure session management and minimizing the possibility of unauthorized reuse.
https://learn.microsoft.com/en-us/entra/identity-platform/refresh-tokens
CONNECT Scan to JOIN uses an Azure Application (CONNECT GO), which requires user consent, to access calendar data securely via Microsoft Graph API. The Azure Application consent process is governed by enterprise settings in Microsoft Azure, which an Azure administrator can configure in three different ways:
The CONNECT GO Azure Application can also be deployed by utilizing Admin consent. This will let users log in without individually consenting on their first time.
https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/grant-admin-consent?pivots=portal
The Azure Application ‘CONNECT GO’ is published and verified by ‘Synergy SKY AS’.
The CONNECT GO application utilizes "Calendars.Read" and "User.Read" delegated permissions to populate the user's calendar on their device. This calendar data is held in memory only during the user’s session. It is only a hash of the user’s email address that is stored, subject to CONNECT’s retention policy of 30 days.
The hash of the user’s email address is stored in an encrypted database, using AES-256. And all data in transit between CONNECT, Microsoft 365 and our encrypted database is encrypted using TLS 1.2/1.3 to ensure confidentiality and integrity of the information.
Access requests, usage and statistics are available through native Microsoft Entra logging, providing an audit trail for compliance and security monitoring purposes. These audit materials help detect potential data exfiltration attempts and unauthorized access.
https://learn.microsoft.com/en-us/entra/identity/monitoring-health/concept-audit-logs
Once a user chooses a specific meeting, CONNECT GO transmits the necessary information—such as the meeting ID and password—to CONNECT over an encrypted channel. The following metadata is stored in CONNECT when joining a meeting:
This metadata is stored in an encrypted database, using AES-256. And all data in transit to and from the database is encrypted using TLS 1.2/1.3
At the end of a meeting, the session is closed, purging all unused calendar information from the service. The selected meeting metadata is retained for 30 days before automatic deletion. Logs are retained for 14 days before automatic deletion. Any unselected meeting information is ephemeral.
In CONNECT meetings a mobile phone can be used to interact with the meeting. By scanning a QR code presented on the video system’s monitors, the user’s device gets access to a CONNECT web-page, enabling features such as layout adjustments and participant engagement (e.g., raising hands or sending emojis). These commands traverse secure channels. Interaction information is retained for up to 30 days, aligning with operational requirements for auditing, incident troubleshooting, and customer support.
In a Hybrid deployment, the CONNECT – Click to JOIN and CONNECT – JOIN by ID components run on infrastructure that is owned and controlled by the customer, rather than within Synergy SKY's cloud environment. The underlying application logic is the same as described in the CONNECT – Click to JOIN and CONNECT – JOIN by ID sections above, with only minor technical adjustments made to support customer-hosted operation. The core difference is where these two features run and where their data is stored: on a server the customer owns and controls, instead of within Synergy SKY's cloud. This section documents where the Hybrid model differs from the cloud deployment as a result; where a topic is not addressed below, the corresponding cloud section applies unchanged.
Hybrid deployment is available for Click to JOIN and JOIN by ID only. CONNECT – Scan to JOIN / GO, CONNECT TrueView Engage, and the core CONNECT Gateway service continue to operate exclusively as a Synergy SKY-hosted cloud service. The CONNECT Gateway is the service that receives the video system’s call and connects it to the meeting, so a customer-hosted feature still depends on it.
Moving Click to JOIN and Join by ID onto customer-owned infrastructure shifts a defined set of operational responsibilities from Synergy SKY to the customer. The table below outlines this division.
|
Responsibility |
Cloud |
Hybrid |
|
Application software development and release (incl. security fixes) |
Synergy SKY |
Synergy SKY |
|
Application upgrades (performing the update) |
Synergy SKY |
Customer (customer-initiated) |
|
Hosting infrastructure and OS |
Synergy SKY |
Customer |
|
Network security and firewalling |
Synergy SKY |
Customer |
|
Physical security of the host |
Synergy SKY |
Customer |
|
OS and platform patching |
Synergy SKY |
Customer |
|
Backup and disaster recovery |
Synergy SKY |
Customer |
|
Storage of feature data (calendar-derived metadata) |
Synergy SKY Cloud |
Customer environment |
|
Storage of meeting connection details (CONNECT Gateway) |
Synergy SKY Cloud |
Synergy SKY Cloud |
|
API access registration and permissions (Microsoft Entra / Google) |
Customer |
Customer |
|
API credentials (client secret or certificate): created by |
Customer |
Customer |
|
API credentials: held by the running feature in |
Synergy SKY Cloud |
Customer environment |
Synergy SKY remains responsible for the security of the application code itself, including the secure software development practices applied to it under Synergy SKY’s ISO 27001-aligned ISMS, and for the CONNECT Gateway service. The customer is responsible for securing the environment in which the Click to JOIN and JOIN by ID software runs.
In the Hybrid model, data is held in two places.
Feature data (customer environment). The metadata that Click to JOIN and JOIN by ID gather while processing calendars, as described in the data flow sections of those features above, is stored in a database located within the customer’s own environment instead of Synergy SKY’s cloud database. This includes calendar-derived information such as organizer and invitee names and email addresses, room and resource addresses, and the meeting subject, as well as the meeting details held by the feature. At the end of the scheduled meeting time this data is archived within the same database, as described in Data Retention.
Meeting connection details (CONNECT Gateway, Synergy SKY cloud). For a video system to dial into a meeting, the customer-hosted feature passes the details required to connect to the CONNECT Gateway: meeting type, meeting ID, meeting password, meeting joining link, and meeting start time and duration. These details leave the customer’s environment and are stored and retained by the Gateway as described in the CONNECT - Interoperability section above. Calendar-derived personal data such as organizer and invitee details is not part of this set.
The CONNECT software uses TLS 1.2/1.3 for data in transit. Encryption of the feature data at rest is determined by the customer and depends on how the customer configures the database and the hosting environment. Because the customer controls the hosting environment, the customer is responsible for ensuring the underlying infrastructure (disk encryption, key management, network segmentation) protects the data in line with their own policies.
Retention of feature data differs from the cloud deployment. In the cloud deployment, feature data is removed at the end of the scheduled meeting time. In the Hybrid deployment, at the end of the scheduled meeting time, all feature data gathered for the meeting is archived: it is moved to a separate table in the same database in the customer’s environment. Archived data is kept until the customer purges it. There is no automatic expiry.
Meeting connection details held by the CONNECT Gateway are not affected by the Hybrid deployment. They are retained for 30 days after the end of the scheduled meeting time or the end of last usage of the meeting, and call logs for 14 days, before automatic deletion.
The archive is under the customer’s control. The customer can purge archived data at any time by removing the archived records from the database, and is responsible for deciding how long it is kept in line with their own data governance policies, and for any backups of it. Synergy SKY recommends that customers define a purge schedule that matches their data retention policy.
The identity and access model for Click to JOIN and Join by ID is the same in the Hybrid and cloud deployments. In both, the customer registers API access in their own Microsoft Entra tenant or Google Workspace environment (referred to as an "app registration" in Microsoft Entra), and grants the permissions and scopes listed in the Microsoft Graph and Google API tables in the CONNECT – Click to JOIN and CONNECT – Join by ID sections above. The customer retains full control over this registration, including the ability to review, restrict, or revoke access at any time. Token issuance, lifetime, and expiration continue to be governed by the customer's own Microsoft Entra or Google Workspace policies.
What differs is where the feature itself runs, and therefore where the credentials used to call these APIs are held and used. In both models, the API credentials (client secret or certificate) are created by the customer and configured into the CONNECT feature. The feature itself holds them and uses them to call the customer's calendar APIs:
As a result, in a Hybrid deployment, API credentials and the calendar data retrieved with them remain within infrastructure the customer owns and controls. The customer is responsible for protecting these credentials on the host, including secure storage, access restrictions, and rotation in line with their own policies.
The customer-hosted Click to JOIN and JOIN by ID components continue to interoperate with the Synergy SKY-hosted CONNECT Gateway to complete meeting connections for video systems. The customer-hosted server initiates all connections to Synergy SKY and to cloud services. It calls the CONNECT Gateway APIs in the Synergy SKY cloud to deliver the meeting connection details listed above, calls the Microsoft Graph or Google APIs to read calendars, as in the cloud deployment, and, where applicable, calls the Webex APIs. No inbound connections from Synergy SKY into the customer’s environment are required. Where Google Calendar change notifications are used, Google sends notifications to an HTTPS endpoint on the customer-hosted server, so customers using Google Calendar must allow inbound HTTPS traffic from Google to that endpoint. All connections are secured using TLS 1.2/1.3. Customers should ensure their firewall configuration permits the traffic described above.
Synergy SKY continues to develop, test, and provide new releases of the Click to JOIN and Join by ID software, including security fixes. In the Hybrid model, the upgrade process is initiated and carried out by the customer on their hosted instance, within a timeframe the customer determines. Synergy SKY will communicate the severity and urgency of security-relevant releases to the customer, but does not apply them, since the customer controls the runtime environment. Customers who defer updates should be aware this can result in version drift between their instance and the current cloud release, and should weigh this against their own patch management policies.
Synergy SKY’s ISO 27001-aligned ISMS covers the design, development, and operation of the CONNECT software, including the Hybrid-deployable components, and the operation of the CONNECT Gateway service. It does not extend to the customer’s own hosting infrastructure, network, or physical environment in a Hybrid deployment, nor to the data held there, including archived feature data. That portion of the security posture falls under the customer’s own security and compliance program. Customers should factor this boundary into their own risk assessments and audits.
Synergy SKY’s governance, risk management, and compliance activities are anchored by a formal Information Security Management System (ISMS) that underpins CONNECT. These activities encompass a range of policies, frameworks, and processes designed to safeguard data confidentiality, integrity, and availability at every stage of its use.
Monitoring of the CONNECT platform involves comprehensive logging, penetration testing, and vulnerability scans conducted on a regular basis (by a third-party organization) to validate ongoing security measures. System logs capture vital events, including user authentication sessions, calendar queries, and administrative updates, providing the foundation for both real-time alerts and post-event forensic analysis. Where potential weaknesses emerge, Synergy SKY’s internal processes ensure rapid remediation by tracking vulnerabilities through documented workflows that allocate clear responsibilities. In keeping with ISO 27001 principles, the organization also conducts scheduled internal audits and management reviews, which inform a cycle of continuous improvement. These audits validate that security controls remain effective over time and that newly discovered best practices are systematically integrated, thereby preserving a robust and resilient security posture.
The security of CONNECT is underpinned by well-defined architecture, thorough data lifecycle management, and robust governance processes. By integrating Microsoft Entra for identity and access control, encrypting data at rest and in transit, and maintaining strict retention policies, Synergy SKY fulfills stringent security and compliance standards. Ongoing risk assessments, vulnerability management, and adherence to ISO 27001 principles reinforce this posture, providing both users and administrators with confidence in the platform’s integrity and resilience.
By enforcing strong encryption standards and ISO 27001-aligned policies, Synergy SKY delivers a secure and compliant collaboration experience for enterprise customers .
|
Security Feature |
Implementation |
|
Authentication |
N/A |
|
Encryption (in transit) |
TLS 1.2 / 1.3 |
|
Encryption (at rest) |
AES 256 |
|
Session security |
TLS 1.2 / 1.3 |
|
Meeting metadata retention |
30 days after end of scheduled meeting time or last usage of meeting |
|
ISO 27001 compliance |
Identity Access Management, Encryption, Secure API Calls, and Data Retention Policies |
|
Security Feature |
Cloud |
Hybrid |
|
Authentication |
Microsoft Entra / Google Cloud IAM |
Microsoft Entra / Google Cloud IAM |
|
Encryption (in transit) |
TLS 1.2 / 1.3 |
TLS 1.2 / 1.3 |
|
Encryption (at rest) |
AES 256 |
Determined by the customer |
|
Session security |
Unique, OAuth token expiration |
Unique, OAuth token expiration |
|
Meeting metadata retention |
Until end of scheduled meeting time |
Archived at the end of the scheduled meeting time, kept in the customer's database until purged by the customer |
|
Software updates |
Applied by Synergy SKY |
Released by Synergy SKY, applied by the customer |
|
ISO 27001 compliance |
Identity Access Management, Encryption, Secure API Calls, and Data Retention Policies |
Applies to the software and the Gateway. The customer's hosting environment is outside the certification scope |
|
Security Feature |
Cloud |
Hybrid |
|
Authentication |
Microsoft Entra |
Microsoft Entra |
|
Encryption (in transit) |
TLS 1.2 / 1.3 |
TLS 1.2 / 1.3 |
|
Encryption (at rest) |
AES 256 |
Determined by the customer |
|
Session security |
Unique, OAuth token expiration |
Unique, OAuth token expiration |
|
Meeting metadata retention |
Until end of scheduled meeting time |
Archived at the end of the scheduled meeting time, kept in the customer's database until purged by the customer |
|
Software updates |
Applied by Synergy SKY |
Released by Synergy SKY, applied by the customer |
|
ISO 27001 compliance |
Identity Access Management, Encryption, Secure API Calls, and Data Retention Policies |
Applies to the software and the Gateway. The customer's hosting environment is outside the certification scope |
|
Security Feature |
Implementation |
|
Authentication |
Microsoft Entra |
|
Encryption (in transit) |
TLS 1.2 / 1.3 |
|
Encryption (at rest) |
AES 256 |
|
Session security |
Unique, expiring QR codes and OAuth token expiration |
|
Meeting metadata retention |
No storage |
|
ISO 27001 compliance |
Identity Access Management, Encryption, Secure API Calls, and Data Retention Policies |