Privacy Policy

Last updated: November 9, 2026

This policy explains how Screen2Screen handles information when you use the Screen2Screen Android app, the technician web interface, the organization administration interface, and related services (together, the “Service”). Screen2Screen provides tools for an organization’s authorized technicians to support its invited Android users. The organization decides who may access its workspace and is responsible for its own use of the Service.

Service provider: Ridgewell Digital LLC operates Screen2Screen. “Screen2Screen,” “we,” and “us” refer to Ridgewell Digital LLC.

Information we process

• Account and identity information: email address, display name, account identifier, sign-in provider, and authentication/session security information. Sign in with Google is available. We do not receive your Google account password.
• Organization and access information: organization name and identifier, membership and role (such as owner, administrator, technician, or Android end user), invitation status, and seat or plan limits.
• Support session information: session and room identifiers, session state, requesting user and assigned technician identifiers, and timestamps for requests, connection, expiration, and ending a session. This supports session coordination, security, and the organization’s connection history.
• Android device information during a support session: manufacturer and model, CPU usage (device-wide when available, otherwise Screen2Screen app usage), total and available memory, total and available storage, battery level/charging status/temperature, device language, Bluetooth on/off status, connection type, Wi-Fi signal strength when available, network interface name and hardware address when Android exposes them, and current IPv4/IPv6 addresses. These details are sent periodically while a session is active and are displayed to the assigned technician. Screen2Screen does not collect IMEI or automatically read stored Wi-Fi passwords, network names, or access-point addresses. Optional user-authorized file access and technician-entered Wi-Fi configuration are described separately below.
• Installed app information during a support session: names, package identifiers, and version numbers of user-installed apps with a launcher icon. This inventory is sent to the assigned technician during the approved session to help identify and troubleshoot the organization’s workflow apps. It is not included in connection history or retained by Screen2Screen after the live session.
• Screen content: when the Android user approves Android’s screen-capture prompt, the app streams the device screen live to the assigned technician. Screen2Screen does not intentionally record the screen stream. Screen content may include information visible in other apps, so users should close or hide sensitive information before sharing.
• Optional interaction settings: View Only shares the approved screen. View and Point adds a visual marker when Pointer control and Android’s display permission are enabled. View and Touch uses Android’s Accessibility service to perform supported actions from the assigned technician during an active session, including gestures, navigation, and text entry. Touch control uses Android’s AccessibilityService API. Android grants that service access to the active app’s screen/window content and on-screen controls. Screen2Screen uses the window structure to locate a focused editable field and apply text from the assigned technician. Sent text replaces that field’s contents. Our code does not read or send its existing text or record accessibility events. Touch commands require the app’s separate disclosure consent, its Touch control setting, Android’s service permission and an approved active session. The user can disable these optional controls. Always On registers a device as available for technician invitations and reports readiness/check-in information; the user approves Android screen sharing before a session’s screen becomes visible.
• Optional file access and transfer: during an approved support session, the assigned technician can browse names, file sizes, and folder structure within a folder selected by the Android user, including its subfolders, and upload or download individual files up to 20 MB. The folder authorization is stored locally for that Screen2Screen account on that device and applies across the account’s organizations. The user can change or revoke it in Settings. File contents travel over the session connection; Screen2Screen does not add them to connection history or a central file archive. Downloaded files are held in the technician browser’s memory until saved or cleared. Uploaded and saved/downloaded copies can remain on the recipient’s device after the session. A local record of an unfinished upload helps the app attempt to remove partial files after an interruption. Android protects other apps’ private data and system folders.
• Optional Wi-Fi requests: a technician can send a network name, security type, password, and hidden-network flag for the user to review and approve through Android. Credentials are held for the in-memory request and Android confirmation, not placed in notifications, ordinary device telemetry, connection history, or diagnostic logs. Android manages a network once the user approves saving it. Request status is shared with the technician. This does not retrieve saved network passwords.
• App action requests: technicians can request that the user open or install a supported app, or uninstall an eligible user app. Requests use package identifiers and app labels; removal requires Android confirmation. Pending requests and their notifications clear when the support session ends.
• Always On check-ins: opted-in registrations report device identity and account/organization association, last check-in, app and Android versions, battery, and invitation receipt/approval state for the Ready-device list. Availability checks do not themselves stream the screen.
• Product support requests: when an admin or technician submits the Support form, the issue text, signed-in email, role, organization name and identifier, and a support reference are sent to the configured support email destination for follow-up. Do not include passwords, authenticator secrets, or payment-card details in the issue.
• Website and service diagnostics: our public marketing website uses an analytics service that may use cookies or similar technologies and process browser, device, usage, and approximate location information. Service providers may also process technical logs, such as IP address, device/browser information, and request timestamps, to operate and secure the Service.

How we use information

We use information to authenticate users, verify organization membership and roles, manage invitations and seat limits, create and coordinate support sessions, deliver the user-approved screen stream, show session-related device details and installed user-app information to the assigned technician, carry out authorized app actions, folder browsing, file transfers, and user-reviewed Wi-Fi requests, maintain connection history and Ready-device registrations, protect the Service, troubleshoot failures, and respond to privacy or support requests. We do not use Android screen content or device telemetry for advertising.

When information is shared

• With the organization: organization owners and administrators can manage members and view organization records. The current assigned technician can see the live screen, device and app details, and authorized shared-folder information during an approved session. File transfers disclose the selected file contents to the recipient. Other organization users do not receive the live session by default.
• With service providers: third-party providers help us operate account authentication, hosting, database storage, cloud processing, real-time screen-sharing connections, analytics, and subscription billing. They process information as needed to provide these services under their own terms and privacy notices.
• For legal and security reasons: we may disclose information where required by law or where reasonably necessary to protect users, organizations, or the Service.

We do not sell personal information. Paid subscriptions may be purchased through a third-party payment provider on the web. Payment-card details are handled by that provider; Screen2Screen receives information needed to manage the organization’s subscription and plan status. The Android app does not collect payment-card details.

Account deletion and retention

We retain account and organization records while they are needed to provide the Service and maintain organization access. Support-session history is typically purged after 365 days. Expired support requests are marked expired; that status change is separate from deletion. Organization owners can request member or organization-data removal, and individuals can submit a privacy request using the contact below. We will review and handle requests subject to the organization’s role, applicable law, and limited records needed for security or legal obligations.

To request deletion of your Screen2Screen account and associated personal data, email support@screen2screen.net with “Account deletion” in the subject. Include the sign-in email address and, if known, the organization name. We will verify the request and remove the account data we control, subject to information we must retain for legal, security, or fraud-prevention reasons. An organization administrator can remove your organization membership, but that alone does not delete your Screen2Screen account or all associated data. For access or correction requests, use the same contact address.

Security

We use access controls and service-provider security features to protect information. No internet transmission or storage system can be guaranteed completely secure. Users should end screen sharing when support is complete and avoid sharing sensitive screen content unless needed.

Children

The Service is designed for organizations and their invited users, not for children to use independently. An organization that invites users is responsible for ensuring its use is appropriate for those users and complies with applicable requirements.

Changes to this policy

We may update this policy as the Service changes. We will post the updated version on this page and revise the “Last updated” date. Material changes may also be communicated through the Service or to organization administrators.

Contact

For privacy questions or requests, contact the Screen2Screen operator:

• Legal developer/company name: Ridgewell Digital LLC
• Privacy email: support@screen2screen.net
• Mailing address: 404 SW 37th Ter, Cape Coral, FL 33914