Saikyo Connect Privacy Policy
Last updated: 9 October 2026
This Policy explains how Saikyo Limited, Hong Kong (“Saikyo”, “we”, “us”) handles personal data when you use Saikyo Connect services operated by Saikyo Limited, including the management console, hardware connectivity, application (the “App”) and related account, device and network access services. Read it with our Terms of Service.
For Services operated by Saikyo Limited, Saikyo Limited handles data to provide and secure the service. Your organisation also determines membership, access permissions and network policies, and may control data processed on its behalf. If you connect to an independently operated panel, subscription or network, its operator handles the data it receives under its own privacy notice. Data handling by third-party services is governed by their operators’ privacy notices.
1. Data used to provide the Services
The information processed depends on your account, platform, enabled features and network configuration:
| Category | Information and purpose |
|---|---|
| Account and organisation | Account identifiers, email or profile information supplied by you or your identity provider, organisation and group membership, roles and entitlements. Used to sign you in and determine authorised access. |
| Registered devices | Device name, platform, persistent device identifiers or fingerprints, registered public keys, registration and last-seen information, and revocation status. Used to bind access to a device, enforce limits and withdraw access. |
| Connections and usage | Network and node identifiers, connection status, assigned tunnel addresses, current device leases, upload/download byte counts and timestamps. Used to operate connections, show usage, enforce service limits and diagnose faults. |
| Service access and security | Source IP addresses, request and sign-in information, endpoint discovery records, and administrator actions. Used to locate suitable endpoints, authenticate requests, investigate abuse and maintain audit records. |
| Support and purchases | Messages, attachments and logs you send us; order, entitlement and payment-status information when the relevant provider offers purchases. Used to answer requests and manage the purchased service. Payment providers handle payment details under their own notices. |
For managed hardware, we also process device serial numbers, firmware and configuration versions, WAN IP addresses, online status, and link and device-health metrics for activation, configuration delivery, remote management and troubleshooting. The latest local-network lease snapshot reported by a device can include client IP addresses, MAC addresses, hostnames and lease expiry times. Organisation administrators and platform operators with the relevant permissions can view this information.
Account identifiers, device registration and valid credentials are necessary for authenticated access. If you do not provide required information or permissions, the corresponding feature may not work.
2. Network traffic, DNS and connection logs
When a tunnel is active, the App, connected hardware and selected network endpoints process the traffic routed through them, including IP addresses and DNS requests where configured. Routing covers selected destinations or all device traffic according to the configuration. Your organisation’s policies and the configuration determine the path and DNS service used.
The Services record traffic statistics and, when connection logging is enabled on a node, connection information. Connection records can include timestamps, protocol, source and destination IP addresses and ports, destination domain, and the associated organisation, user, credential and device identifiers. Traffic statistics are recorded separately; disabling connection logging does not stop traffic statistics.
The connection-log feature records connection metadata. Its records exclude message bodies and full packet payloads. Network forwarding still requires processing traffic in transit. Unencrypted traffic may be visible at an exit or destination network; use HTTPS or other application-level encryption for sensitive communications. Tunnel encryption does not make you anonymous to the service operator or destination.
Authorised organisation administrators can view their organisation’s usage and connection records. Platform personnel with the relevant audit permissions can access records needed to operate and investigate the service. Ask your administrator about the logging and routing settings of the network you use.
3. App diagnostics and analytics
The App supports Sentry for crash and performance diagnostics and PostHog for product usage analytics, when configured and enabled. Information can include App version and build, platform, release environment, installation/start/foreground events, connection-status changes, error messages, stack traces and performance or interaction diagnostics.
When analytics is enabled, PostHog uses an installation identifier; App-start events also include the persistent tunnel device identifier when the App can read it. Records containing the tunnel device identifier can be linked to a registered device. Diagnostic requests also expose connection information such as an IP address to their receiving service. The App applies filtering to Sentry events and diagnostic logs to reduce credentials and personal information, but error messages and user-supplied material can still contain sensitive details.
In the standard user-choice configuration, analytics is off until you enable it. You can change the analytics setting during onboarding or in Settings. Organisation-specific builds may enforce analytics on or off; the App displays the managed setting and does not offer a user override in that mode. Contact your administrator about its policy. Turning off optional analytics stops future optional collection; it does not disable essential account, device, usage or security processing, or erase records already received.
We use these diagnostics to assess reliability and improve the App. We do not use them for advertising.
4. Local storage and device permissions
The App stores preferences, account/session information, subscription and routing configuration, persistent device identity and tunnel key material on your device. Some session data is stored in application preferences or local files. Operating-system keychain protection is not applied to all locally stored credentials. Protect your device, backups and exported configuration.
The App can create local diagnostic and connection logs. Logs may include destinations, configuration details and errors. Exporting or sharing them sends the selected material to the recipient you choose. Filtered logs can still contain sensitive information. Review the content before sharing.
VPN/network-extension permissions and, on some desktop systems, privileged networking services are used to establish tunnels and configure routing or DNS. Camera or file access, where requested for scanning or importing configuration, is used for that action. Notification permission supports status notices. You can manage permissions through your operating system, although withdrawing a required permission may disable a feature.
The account portal uses cookies needed for sign-in sessions and request security. External identity providers and app stores may use their own cookies and storage under their own notices.
5. Recipients and international processing
Data is provided to the parties needed for the relevant function:
- Your organisation and its authorised administrators, for account, device and network management.
- Identity providers such as Logto, for authentication and organisation permissions.
- Hosting, database, network endpoint, DNS and service-discovery providers, for operating the Services.
- Sentry and PostHog or their configured hosting providers, when diagnostics and analytics are enabled.
- Payment, app-store and update distribution providers, when you use those functions.
- Support recipients you choose when sharing material, and professional advisers or authorities where necessary for legal obligations or disputes.
We do not sell personal data. We may disclose relevant data where legally required or reasonably necessary to protect users, investigate abuse or establish and defend legal claims. If a business transfer affects your data, we will require its handling to remain subject to applicable protections and notify you where required.
Saikyo is based in Hong Kong. Your selected endpoints, organisation deployment and service providers may process data in other countries, whose privacy laws may differ. We use access restrictions and applicable contractual safeguards for service-provider processing. Storage and processing locations depend on the selected endpoints, organisation deployment and service providers. Contact us or your administrator for details of your deployment.
6. Retention and deletion
The current Saikyo Connect backend uses the following retention arrangements:
- Node connection logs have a 180-day retention policy when logging is enabled.
- Endpoint discovery disclosure records have a 90-day retention policy.
- Historical managed-hardware metric reports have a 30-day retention policy. The latest device status and local-network lease snapshot are stored separately in the device record and are not covered by that historical-metric period; lease details are excluded from historical metric reports.
- Current tunnel leases hold only the current connection state.
- Account/device records (including the latest hardware state), accumulated traffic statistics and administrative audit trails do not have an automatic age-based expiry in the current system. They can remain after sign-out or device revocation. Deletion or anonymisation requires a separate process, subject to service, security and legal needs.
Time-based cleanup operates on database partitions. Actual deletion time depends on partition boundaries and when cleanup jobs run. Backups and records preserved for legal obligations or disputes may remain longer. Local logs rotate by file size, so their retention duration varies with the volume of logs generated. Local preferences and configuration remain until removed; operating-system backups may keep copies.
For support material and diagnostic-provider records, retention depends on the support case and configured provider policies. Contact us for the applicable period. We review retention needs and delete or anonymise data when it is no longer necessary, subject to applicable obligations. A request to delete your account does not automatically erase every audit, usage or third-party record.
7. Your choices and requests
You can disconnect a tunnel, manage supported App settings, change analytics preferences in the user-choice configuration (organisation-managed builds follow the organisation setting), and revoke registered devices through device management. Signing out, revoking a device or uninstalling the App does not delete your server-side account or cancel a subscription.
To request access, correction, account closure or deletion of personal data held by Saikyo, email [email protected] with the subject “Saikyo Connect privacy request”. Identify the account and organisation concerned and describe your request. Do not send passwords, tokens or private keys. We may verify your identity and authority before acting, and will explain any information we must retain or request we cannot fulfil under applicable law.
If your organisation or an independent provider controls the account or records, contact that administrator or provider; we can help identify the appropriate contact. Additional rights, such as objection, restriction or portability, apply where required by the law relevant to you. You may also complain to the relevant privacy authority, including the Hong Kong Privacy Commissioner for Personal Data.
8. Security, children and updates
The Services use authentication, device-bound access, tenant access controls and encrypted connections where supported to protect data. No system or transmission is completely secure. Tell us promptly if you suspect a compromised account or exposed credentials.
The Services are intended for business and organisational customers and their authorised members. The Services are not directed at children. If you believe a child has provided personal data without the necessary authority or consent, contact us so we can investigate and take appropriate action.
We will update this Policy when data practices change, publish the revised date here, and provide notice of material changes through the App, portal or another appropriate channel. We will obtain any further consent required by applicable law.
9. Contact
For privacy questions or requests, contact [email protected].
Saikyo Limited, Flat/Rm B, 16/F, Billion Plaza II, 10 Cheung Yue Street, Lai Chi Kok, Kowloon, Hong Kong.