Privacy policy

1. Who we are and what this policy covers

Hub4Screen is a screen-management and interactive signage service provided by MK-Tech-Solutions. This policy describes information handled through the Hub4Screen Android player, the management service and this website.

An organization that manages a screen chooses its content, enabled experiences and screen-monitoring settings. That organization can access information associated with its screens. Contact it about the content shown or the use of questionnaire results. You may also contact MK-Tech-Solutions using the email below.

2. Device registration and operation

The player sends an installation identifier and an Android identifier used to recognize a returning device, device model and manufacturer, Android and app versions, display dimensions and capabilities. It also sends pairing and session information, playback status, content versions and diagnostic details so we can assign content, authenticate the device, monitor operation and investigate faults or suspected cloning.

The current player does not collect an IMEI, hardware serial number or MAC address. Its application permissions do not request camera, microphone, location, contacts or SMS access. The Android recovery identifier is used for device recovery, not advertising profiling.

The service and infrastructure providers also receive IP addresses and technical request and connection information for communication, security and diagnostics. Management-account actions may record the user, email and IP address in the audit trail.

3. Screen monitoring

When enabled by the managing organization, the player uploads periodic images of content displayed within the Hub4Screen app for remote screen monitoring. This captures the app window, not the camera or other apps. Capture is paused during an active questionnaire or game. Content selected by an organization may itself contain information, so the organization must consider what it displays.

4. Questionnaires, assistance and usage analytics

Enabled questionnaires send selected answer information and assistance requests to the organization managing the screen. Usage events record questionnaire starts, answer selections, recommendations, completion or abandonment, assistance requests, catalog sessions and product opens. Events include session, experience and content identifiers, timestamps and elapsed time. These help the organization understand how its screens and content are used.

The current player questionnaire does not request a visitor name, email address or phone number. Events are associated with a screen and its organization; a random session identifier does not mean no information is collected. Pending events are stored locally and may be uploaded when connectivity returns, including after the visible player session ends.

Games with registration collect your name, phone number, optional email, policy version and privacy/participation acceptance, a separate optional marketing choice, kit and screen identifiers, participation times and game result. The phone number also enforces participation limits for that kit when enabled. Applicable privacy and participation documents are shown before submission; the player does not verify the phone by SMS. Registration details are sent to the service and are not part of the local analytics queue.

5. Accounts, website enquiries and content

The management service processes account and organization information needed for sign-in, permissions and administration, and content uploaded or configured by authorized users. Account verification and service communications may be delivered by email. Optional AI content-creation features in the management service can send submitted prompts and relevant input content to the configured AI provider; the Android player displays the content assigned to it.

If you contact us through this website, the submitted contact details and message are sent to our business inbox so we can respond. The website uses technical request information and short-lived request counters, including a hashed IP address, to limit spam and abuse. The contact endpoint does not log submitted message bodies. Hosting and security services may process request metadata for delivery and protection.

For optional analytics, cookies, maps and marketing-website enquiries, see the website privacy policy. Website measurement is separate from player usage events.

6. Who can receive information

Authorized personnel of the organization managing a screen can access its operational information and enabled interaction results. MK-Tech-Solutions and infrastructure providers process information as needed to operate, secure and support the service. The current infrastructure uses Amazon Web Services for hosting, storage, authentication and email; optional AI generation uses the configured AI provider, currently OpenAI. These providers process information for their respective service functions.

Information may also be disclosed where required by law or necessary to investigate abuse or protect the service. Google Play separately processes information about your store account and installation under Google's policies. The player does not use an advertising SDK to profile visitors. Content supplied by an organization can include advertising; this statement does not mean every screen is ad-free.

7. Security and local storage

The Play release uses HTTPS for communication with the service and stores device credentials using Android Keystore-backed encrypted storage. Local content caches support playback when offline, and a local event queue supports later analytics delivery. Access to management data is controlled by authentication, organization boundaries and assigned permissions. No security measure can guarantee complete protection.

8. Retention and deletion

In the launch release, raw usage events and questionnaire answers expire after 90 days; closed assistance requests expire 90 days after closure; raw heartbeat diagnostics expire after 14 days; and audit records expire one calendar year after creation. Open assistance requests remain available for handling, while their old linked answers still expire after 90 days. Application runtime logs are retained for 14 days. Database cleanup runs daily, so removal happens on the next cleanup run after expiry.

Game participant names, phone numbers, email addresses and marketing choices are erased at the expiry captured from the registration policy, normally 90 days, on the next daily cleanup. Game context, result and the policy-version record remain without the contact details. The latest monitoring screenshot is kept per screen. Screenshots older than seven days are no longer shown in the console. Hourly cleanup removes historical screenshot versions and expired current screenshots according to their storage upload time. Server usage events expire 90 days after receipt, and questionnaire answers expire 90 days after storage. Local queue cleanup uses a 90-day age according to the device clock; a powered-off device cleans it when execution resumes. An incorrect device clock can affect local cleanup but does not decide report dates or server retention.

Active accounts, device records and customer content are retained to provide the service until an applicable deletion request or service termination is handled. You may request deletion of your account and associated data, or particular data, using the email button on this page or the player's privacy menu, including after uninstalling and without signing in. Email from the account address if possible, identify the organization and explain what you want deleted. Do not send passwords, verification codes or device secrets.

We verify identity and authority and aim to complete a verified request within 30 days. A personal request does not authorize deletion of other users, shared content or the entire organization. Where a screen's managing organization controls the information, we coordinate with it. We confirm what was deleted and identify any information retained for a specific legal obligation or dispute, its reason and retention period.

Rotating backups may temporarily retain a copy of deleted information. Database backups are configured for 14 days; previous versions of ordinary stored files expire after 30 days, while screenshots have separate cleanup. Recorded deletions must be reapplied after a restore before access resumes. Uninstalling, unpairing or suspending an account does not delete data already sent to the service.

9. Changes and contact

We will update this page when the service or its information practices change. The date above identifies this version. For privacy questions or requests, contact MK-Tech-Solutions using the email below.