Skip to content
ScreenWing
TermsBack to website
Legal

Privacy Policy

Effective date: 7 August 2026

On this pageOverviewInformation processedWebsite analyticsHow we use itSharingRetentionSecurityYour rightsContact

1. Overview

This Privacy Policy explains how ScreenWing handles information through its desktop software, mobile companion apps, entitlement service, website, and support channels. ScreenWing is designed so display contents travel between your devices and are not received by that service.

2. Information we process

Subscription and activation data

We process an application-scoped hash derived from the desktop operating system’s machine identifier, the platform type, activation and entitlement status, relevant dates, the store product, Apple receipt and transaction references, or hashed Google Play purchase proofs needed to verify the subscription. A random application-account token links a verified store transaction to a ScreenWing account and one-time desktop code. The raw operating-system identifier is not sent to the entitlement service. Activation secrets and signed entitlements are stored locally on each registered desktop device.

ScreenWing account and sessions

When you request a passwordless sign-in in the iPadOS app, Android app, or membership website, the service temporarily processes the email address to deliver a six-digit code through our email provider. ScreenWing stores an application-specific keyed hash of the normalized email address, not the plaintext address, in its membership database. The service also stores a random account ID, a random store-account token, and only cryptographic hashes of API session tokens. The raw mobile session token is protected by iOS Keychain or Android Keystore on that device.

A successful website email verification places the raw session token only in a Secure, HTTP-only, same-site browser cookie. Alternatively, opening Membership Account from ScreenWing Desktop creates a short-lived one-time sign-in link and a temporary browser session. Only cryptographic hashes of these tokens are stored server-side. The account page receives limited membership dates, plan status, registered desktop platforms, tablet usage history, and store-management links. It does not receive a desktop activation secret, raw machine identifier, store transaction reference, or payment credentials.

Membership usage history and concurrency

We assign a random, pseudonymous ScreenWing member ID to a verified store membership. While a tablet is actually connected as a display, the desktop sends an authenticated active-state update approximately every 30 seconds and one closing update when the session ends. A short-lived server lease linked to that member ID prevents more than one simultaneous display stream. For the free trial, the service also records the account’s trial date, seconds used, and short-lived active lease so the shared trial of 30 minutes per day, up to 210 minutes per week and 900 minutes per month and one-stream limit apply across the account’s registered devices. We retain the registered desktop operating-system category; the tablet-reported name and app platform; a membership-scoped tablet reference derived by the service; connection category; session timestamps, active duration, and update count; and only the country and region code inferred by our infrastructure at the time of the request. This lets the member distinguish tablets and view their own recent activity, and lets the private operator console provide account support and service totals.

ScreenWing does not retain a tablet hardware serial number, UDID, Android ID, GPS or precise location, city, historical IP addresses, screen content, or keyboard, pointer, and touch content in membership usage history. The tablet-reported name may be a model label or a name you assigned on the device. Display frames and input continue to travel only over the local or USB connection between the member’s devices.

Payment information

The Apple App Store or Google Play processes your store account, payment method, billing details, tax, fraud-prevention data, and receipts under its own privacy policy. ScreenWing receives a signed App Store transaction or a Google Play purchase token for server verification, then retains only the limited references, hashes, and subscription status needed to operate the membership. ScreenWing does not receive or store your full card number, CVV, store password, or payment credentials.

Local connection data

The apps use local-network details such as device name, IP address, resolution, and connection state to discover and connect your devices. Screen frames and input events travel directly between your desktop and your mobile device over your local or USB network for the display session; they are not sent to or routed through our entitlement service. ScreenWing account sign-in is used to prove and activate membership across platforms; it does not route or receive the display stream.

Diagnostics, website, and support

Local logs may include technical status, errors, network addresses, and device characteristics; they stay on your device unless you choose to share them with support. The entitlement service may process the network address of an incoming request for rate limiting and abuse prevention. We process information you voluntarily provide in a support request. The apps and website do not contain third-party analytics or behavioral-advertising SDKs.

Website analytics

The website uses a first-party measurement endpoint to count page views and limited actions such as opening a download, membership account, store-billing page, or support link. The browser sends only the page path without query parameters or fragments, the referring website’s host, a fixed action category, and a random identifier kept for the current browser-tab session. The service hashes that random value before storage. It does not store the raw session value, raw IP address, full user-agent string, account or email identity, store identifiers, form contents, or the text you enter.

When a Google Analytics 4 measurement ID is configured, the same preference and browser privacy signals also control a Google tag. That tag may send page path, approximate location derived by Google, device class, and limited action names to Google so the operator can view Search and Analytics reports. Advertising signals and ads personalization are disabled. Search query, impression, and click counts shown in the private operations console come from Google Search Console’s site-owner API, not from the public website.

Our infrastructure categorizes the browser, operating-system family, and device class, and may provide an approximate country, region, and city for the request. These coarse fields and the hashed session value are available only in the authenticated operator console, are used for aggregate product and reliability analysis, and are not used for advertising or cross-site tracking.

Checking your anonymous analytics preference…

Disabling stops future website events on this browser. ScreenWing also honors Global Privacy Control and browser Do Not Track signals.

3. Why we use information

We use information to provide and secure ScreenWing, verify subscriptions, show members their own account and usage history, provide aggregate and member-level operational support, prevent payment and activation abuse, connect devices, diagnose failures, meet accounting or legal requirements, and improve reliability. Depending on your location, the legal basis may be performance of a contract, legitimate security and support interests, consent where required, or compliance with law.

4. Sharing and service providers

We share information only when necessary with payment and distribution providers such as Apple and Google; infrastructure providers such as Cloudflare; professional advisers; or authorities when legally required. Apple and Google independently process store account, payment, tax, and fraud-prevention information under their policies.

We do not sell personal information or share it for cross-context behavioral advertising.

5. Retention

Anonymous website analytics events are retained for no more than 90 days. The opt-out preference cookie is retained for up to one year unless you re-enable analytics or clear browser data. Expired one-time activation, email verification, and account sign-in challenges are removed or made unusable after their short validity period. Mobile API and browser sessions expire automatically and their hashed records are periodically removed. While an account remains open, its keyed email hash, random account ID, verified transaction references, purchase-proof hashes, registered activation state, subscription status, pseudonymous member ID, tablet-reported labels, and membership usage history are kept as needed to provide the membership and for security and support.

When you delete a ScreenWing account, we remove its keyed email identity, account and session records, registered-device links, concurrency leases, tablet labels, and membership usage history. Linked desktop activations are revoked and detached from the deleted identity. We may retain limited store transaction or purchase-proof evidence without the deleted account identity when necessary for fraud prevention, accounting, refunds, disputes, restoration, or another legal obligation. Local settings and logs remain on your device until you remove them or uninstall ScreenWing. Apple and Google retain their own payment and receipt records under their policies and applicable law.

6. Security

We use passwordless email verification, keyed email hashing, hashed server-side session tokens, iOS Keychain and Android Keystore protection, signed App Store transactions, Android Publisher purchase verification and acknowledgement, authenticated store notifications, purchase-proof hashing, signed device-bound entitlements, restricted local credential files, authenticated subscription and concurrency requests, secure HTTP-only browser cookies, and HTTPS for the entitlement service. Commercial streaming requires a short-lived online concurrency lease so a second session using the same membership is rejected. Restricted USB networking is recommended. Optional Wi-Fi/LAN mode is unencrypted, must be enabled explicitly, and should be used only on a trusted private network. No system can be guaranteed perfectly secure.

7. Your choices and rights

You can permanently delete your ScreenWing account from the signed-in Membership screen in the iPadOS or Android app. You can also use our account-deletion page, verify the same passwordless email, and choose “Delete ScreenWing Account.” Deletion is processed immediately by the ScreenWing service. It does not cancel an Apple App Store or Google Play subscription, so you must separately cancel renewal through the store account used for purchase.

You can change the store payment method through the applicable store, remove local application data, and limit local-network access through operating-system settings. Depending on your location, you may also have rights to access, correct, delete, restrict, or receive a copy of personal data, and to object or complain to a data-protection authority. Some identity-detached transaction, security, dispute, or legal records may need to be retained as described above.

Children and international processing

ScreenWing is not directed to children under 13, or a higher minimum age required locally. Service providers may process information in countries other than yours under their applicable transfer safeguards.

8. Contact and updates

Seller: KEREGE YAZILIM BİLİŞİM TEKNOLOJİLERİ A.Ş.

Business address: Çalca OSB Mahallesi, 1. Cadde No: 1, 30 Ağustos Organize Sanayi Bölgesi, KÜTAHYA, Kütahya Merkez, 43100, Türkiye

Tax office / ID: Çinili Vergi Dairesi · 5441565128

D-U-N-S: 520144330

Phone: +905333798110

Support: oo25101981@gmail.com

Support center: /support

Use the Support Center for privacy requests, technical support, or activation restoration. Never send activation secrets or payment details. We will post changes to this Policy here and update the effective date.

© ScreenWing.Terms · Refund policy