1. Scope of this Policy
This Policy explains data handling in Lyzard Connect, on https://connect.lyzardworks.com, in the update system, connection-establishment services and voluntary support contacts.
Lyzard Works is used as the Lyzard Connect product brand. Where personal-data processing arises, the responsible party is the Lyzard Connect product rightsholder operating under the Lyzard Works brand. Privacy contact: privacy@lyzardworks.com. Legal notices: legal@lyzardworks.com.
2. Core principle
Connect is designed so that a normal session does not require an account or become a user database. Voice, video, screen content, messages and transferred-file contents are not sent to the product owner for advertising, profiling or product analytics.
Network nodes still technically process addresses and transport parameters required to deliver data and establish the connection.
3. Accounts and identity
Normal use of Connect does not require account registration. Creating or joining a room does not require a name, phone number, email address, contact list or separate profile.
This website and the prepared update system do not use a persistent user or installation ID for analytics. Staged rollout uses only a local bucket from 0 to 99, which is not a unique identifier by itself.
4. Voice, video and screen sharing
Connect does not collect or archive voice, video or screen-sharing content on product servers for later use. When the network can establish a direct route, media travels between participant devices.
Connect does not currently provide a relay route. If NAT, VPN, firewall or other network restrictions prevent a direct connection, the session or individual features may be unavailable. This statement is not a claim of end-to-end encryption unless a specific published Connect version separately states and verifies that property.
5. Chat and files
Connect does not use message text, filenames or file contents for advertising, profiling or product analytics. On a direct connection, messages and files travel between participant devices.
Connect is not designed as cloud storage for chat history or user files. Local copies, caches and received files may remain on participant devices according to app settings and user actions. If a direct connection cannot be established, transfer through Connect may be unavailable.
6. Rooms and connection establishment
To create a room and establish a connection, Connect uses a coordinator that helps participants exchange the technical data required to attempt a direct route. This may require processing network addresses and other short-lived technical information without which the devices cannot find each other.
The coordinator is not a cloud store for session content. After a direct route is established, voice, video, screen sharing, messages and files are not intended to use the coordinator as their main transport.
7. Update checks
An update check sends only what is needed to select a compatible build: current Connect version, update channel, platform, architecture and a rollout bucket from 0 to 99 when staged rollout is used.
The update API does not require a name, email, phone number, room code, session history, file contents or persistent client ID. The server side does not use these requests to build a behavioural profile.
8. Aggregate product metrics
Connect may receive only aggregate connection metrics from the coordinator: connection attempts, successful connections, connection-time distribution, reconnects and grouped failure reasons.
These metrics do not include a user name, room code, IP address as an analytics identifier, persistent device or installation ID, peer list, messages, voice, video, screen content, filenames or file contents. The metrics are intended to measure connection quality, not to build a user profile.
9. Connect website
The public website does not use advertising cookies, third-party advertising trackers or optional web analytics in its current configuration.
As with any web request, the network technically processes the IP address, requested URL, request time and browser headers needed to deliver the page. These values are not combined with app sessions for advertising profiling.
10. Cookies and local storage
Optional cookies are not currently required for normal browsing of the public website. Advertising cookies and third-party advertising identifiers are not used.
Protected operational areas such as the admin panel may use a necessary technical session for authentication and security. If optional storage or analytics requiring a prior user choice is introduced on the public website, the choice mechanism must be implemented before that feature is enabled.
11. Support and voluntarily submitted data
Connect does not require contacting support for ordinary operation. If a user voluntarily sends a message through the feedback form or by email, only the submitted data and a short-lived pseudonymous anti-abuse token used to protect the form are processed.
The web form remains unavailable until the required controller/operator details are published. When the form is enabled, separate consent is requested independently of other documents where required by applicable law.
12. Infrastructure providers
Lyzard Connect does not sell personal data or provide session content to advertising networks. Limited technical processing may be performed by infrastructure providers needed for a particular function, such as website hosting, update delivery, email infrastructure, DNS/CDN and coordinator infrastructure.
Such access must be limited to the purpose of the service. Adding an infrastructure provider does not by itself grant a right to use data for its own advertising or profiling.
13. Retention
Direct-session content is not intended for server-side storage by Connect. Temporary coordination parameters should exist only as long as needed to establish or restore a connection unless mandatory law requires specific retention.
Information voluntarily sent to support is retained only for the period needed to handle the request under the published retention rules. Website and infrastructure logs should have a limited retention period. If law specifically requires longer retention for defined data categories, the mandatory period applies only to those categories.
14. Security and limits of claims
Connect should restrict access to operational infrastructure, separate public and administrative services, verify update integrity and apply security measures appropriate to the actual product architecture.
This Policy describes the data-handling model and must not be used to promise properties that the implementation has not verified. In particular, Connect does not claim end-to-end encryption, complete anonymity or that network infrastructure can never access transient data unless those properties are separately implemented and verified.
15. Your rights and changes
If Connect actually holds personal data relating to you, you may contact privacy@lyzardworks.com and exercise rights provided by applicable law, including access, correction, deletion, restriction or termination of processing where applicable.
If Connect architecture, data fields, product statistics, infrastructure providers or storage practices materially change, this Policy must be updated before or when the new processing starts. The document version and update date are shown on this page.