TEAMX · YOUR DATA
Privacy policy
How the TeamX download website and Windows remote support app use information.
Every screen-sharing or remote-control session requires the device owner's approval. You choose the screen to share and can end the session. Information visible on that screen is shared with the person you approve.
1. Who operates TeamX
TeamX and dotteam.ai are operated by Nama Alsharq International, Oman. This notice covers the public download website and the current Windows app using TeamX's default connection service. If your organisation uses a different server or your support provider records information separately, its own privacy practices also apply.
2. Visiting the website
The download website does not require an account or ask you to enter a name, password, payment details or email address. Our hosting infrastructure receives your IP address and ordinary HTTP request information to deliver pages and downloads. Technical errors may be recorded in server logs.
The Windows app checks public update information after launch. This sends an ordinary HTTP request to dotteam.ai, including your IP address; it does not upload session content or diagnostics. Downloading and installing an update require your action. The app caches the downloaded installer locally and verifies its published size and checksum before offering installation.
The website stores your selected language in your browser's local storage. You can remove it by clearing this site's browser data. The current website has no advertising trackers, analytics integrations or third-party fonts.
3. Connecting and sharing
- Connection information: the service processes your device name and ID, a generated device key, IP address, temporary session password, connection requests and technical connection information. This enables registration, authentication, session setup and protection against repeated incorrect attempts.
- A stable device ID: your app saves a device key protected by Windows encryption. The server retains a hashed representation of that key and its assigned ID so the same device profile can reconnect with the same number.
- Approved session content: your chosen peer receives the shared screen and, if enabled, system audio. Chat messages, files you choose to send, explicitly shared clipboard text, and mouse or keyboard actions pass between session participants.
The other participant receives your device name and ID. Your device name initially comes from the Windows computer name; connection setup can also disclose network addresses to the peer. This release does not capture microphone audio.
Media and session data use encrypted WebRTC transport. Connections may be direct or pass through a TeamX relay when needed. The connection service handles setup information; the current service does not provide server-side recording of screen video, chat messages or transferred file contents. A participant can still save received files or record information independently.
Use view-only mode when control is unnecessary. Close private documents before sharing. Ending a session stops the app's active sharing; it does not remove information already received or saved by the other person.
4. Information kept on your computer
The app stores connection and language preferences, the protected device key, up to 30 recent session summaries, and up to 100 saved devices. After an ordinary outgoing session becomes ready, the app automatically saves the other device's name, ID and connection server on this computer. You can also add devices manually and edit or delete saved entries. A connection to the same ID on the same server preserves its existing name without creating another entry. The app does not automatically remove entries to make space when the list is full. Summaries can include the peer's name and ID, the server, session times, role and connection mode. Saved-device and history entries do not store session passwords. Choosing a saved device only prepares the connection form; it does not start a connection or grant permission to control the device.
For a resumable session, a reconnect credential is kept only in app memory. A separate stop-only credential is stored encrypted on this computer so that the app can finish an unacknowledged stop after restarting; this stored credential cannot resume a session and is removed after the server confirms the stop.
The app also keeps local diagnostic events, such as connection failures, session timing and performance measurements, to help investigate problems. These diagnostic records exclude session passwords, chat text, file contents and screen images, and are not automatically uploaded by this release. Exporting diagnostics creates a local report; you choose whether to send it to support.
Chat displayed in the app is cleared when the session ends. Files that you save remain in their chosen folders. Text copied to the Windows clipboard can remain there or in operating-system clipboard history after the session.
5. Providers and international connections
TeamX's current service infrastructure is hosted by Hostinger and administered using Laravel Forge. Hosting, administration and network providers may process technical information needed to operate the service. Your chosen session participant receives the content you share.
Infrastructure and the people you connect to may be outside your country. Connection information and shared content may therefore cross borders. Contact us for information about the current hosting arrangements or an organisation's particular use of TeamX.
If you email us, we receive your email address, message and any attachments through our email service. Please send only information needed to handle your request, and do not send passwords or private access keys.
6. Retention and deletion
- Active connections: temporary registration and session state are held while a connection or request is active. For an approved resumable session, the server retains connection state and hashed reconnect/stop credentials in memory while waiting for a network reconnection, until a participant stops the session or the service restarts. A disconnected app can send its pending stop when it next reaches the service. The separate stable-ID record persists and currently has no automatic expiry; you can request its deletion.
- Local app data: preferences and saved devices remain until changed or removed. Older session summaries are replaced when the 30-entry limit is reached; the app provides a history-clearing control. Removing local identity data can change your device ID.
- Local diagnostics: storage is limited to two files of up to 512 KiB each. Old files are pruned when the app starts or writes logs; exported reports are filtered to the preceding seven days. This is not a promise that every record disappears exactly seven days after creation.
- Server logs: diagnostic logs rotate according to file and storage limits. The current configuration does not impose one fixed deletion period in days across all logs.
- Support email: correspondence and attachments remain in the support mailbox unless removed; there is no published automatic deletion period. Contact us to request removal. We assess requests in light of any unresolved issue and applicable legal obligations.
Uninstalling the app does not necessarily remove its Windows profile data, files you saved, exported reports or the server's stable-ID record. Requests concerning another participant's copies should also be directed to that participant.
7. Your choices and requests
You can decline a session request, stop sharing or control, change the temporary password, clear local history and remove saved devices. Depending on applicable law, you may also request access, correction, deletion, a copy of your data, restrictions on processing, or withdraw consent where processing relies on it.
Email mibrahim@namaasharqgroup.com with a description of your request. We may need proportionate information to verify that a request relates to your device or information. Do not include a session password. Deleting the stable-ID record can prevent restoration of that number.
You may raise a concern with the data protection authority responsible for your location. In Oman, see the Ministry of Transport, Communications and Information Technology's personal data protection service.
8. Changes to this notice
We will update this page and its effective date when the described practices change. Review the notice when using a new release or changing your connection service.