INTERNITY LABS

Privacy POLICY of 'Win-X Launcher'

The Android app 'Win-X Launcher' does not collect any personal data. The only time we collect data is if the app encounters an exception (a crash or serious error), where we collect a limited crash report so we can diagnose and fix the problem.


This document can be printed for reference by using the print command in the settings of any browser.

Full POLICY

Contact information:
Internity Labs,
2222 152nd Ave NE, Suite 201,
Redmond WA 98052

Owner contact email: InternityLabs@outlook.com

website: https://www.internitylabs.com/

Thank you for choosing to be part of our community at Internity Labs Inc., LLC. We are committed to protecting your personal information and your right to privacy by very simple approach: 'Not collecting it at all'. If you have any questions or concerns about our Android app, please contact us using above mentioned contact information. In this privacy notice, we seek to explain to you in the clearest way possible what limited crash information we collect if the app encounters an exception, how it is stored, and how it is used. If there are any terms in this privacy notice that you do not agree with, please discontinue use of our App.

Google user data

Win-X Launcher does not currently publish Google Drive connectivity. Google Drive support is planned as an optional feature so users can browse and manage their own Google Drive files from the app's unified file explorer interface. When this feature is published, we will request Google OAuth access only for user-initiated file explorer features, including the Google Docs scope ending with /auth/docs when needed for document interaction. This planned access will not be used for advertising, analytics, profiling, background indexing, or unauthorized data collection.

Dropbox user data

Win-X Launcher plans to support Dropbox connectivity as an optional feature, allowing users to browse and manage their own Dropbox files from the app's unified file explorer interface. When this feature is published, we will request Dropbox OAuth access only for user-initiated file explorer features. The following Dropbox permissions (scopes) are required:

  • files.metadata.read: Needed to display the names and size of the files.
  • files.content.read: Needed to load the thumbnails.
  • account_info.read: Needed to display the name of the logged-in user.
  • files.content.write: Needed to create folders or files when the user clicks "create new" and for file copying or moving between folders.
  • sharing.write: Used for creating sharable links (which are used for viewing the file when the user clicks on it).

This planned access will not be used for advertising, analytics, profiling, background indexing, or unauthorized data collection.


Cloud Connections

Third-party cloud accounts (pCloud, OneDrive, Dropbox - planned, Google Drive - planned)

Win-X Launcher optionally allows you to connect to your pCloud and/or Microsoft OneDrive accounts. Dropbox and Google Drive support are planned and will be optional when published. These connections are used to show your cloud files and folders in the app UI as a file browser.

Data Accessed (pCloud / OneDrive / Dropbox - planned / Google Drive - planned)

If you choose to connect an account, the app accesses only the cloud file/folder listing information needed to display the file browser UI and to perform actions you explicitly request, such as folder navigation, opening or editing Google Docs documents, file rename/move/delete, uploading files from your device, and downloading file metadata or content for local use. The app does not send your cloud files, folder names, or file contents to Internity Labs servers.

Data Usage (pCloud / OneDrive / Dropbox - planned / Google Drive - planned)

We use OAuth 2.0 to obtain authorization to access your account. OAuth tokens and related authorization information are stored only on your device using the platform's secure storage. This information is used only to keep you signed in and to access your connected cloud content within the app.

Every cloud API call (including create, modify, move, rename, and delete operations) is performed only after an explicit user action in the app. The app does not perform background indexing of your cloud account.

Data Sharing (pCloud / OneDrive / Dropbox - planned / Google Drive - planned)

We do not share your pCloud/OneDrive/Dropbox/Google Drive data with third parties. When you connect these accounts, the app communicates directly with the relevant provider services (pCloud, Microsoft OneDrive, Dropbox, and Google Drive) to authenticate and to retrieve the information needed for the file browser.

Data Storage & Protection (pCloud / OneDrive / Dropbox - planned / Google Drive - planned)

OAuth tokens and related authorization data are stored only on your device in secure storage. Internity Labs does not receive or store your OAuth tokens.

Data Retention & Deletion (pCloud / OneDrive / Dropbox - planned / Google Drive - planned)

You can disconnect your pCloud/OneDrive/Dropbox/Google Drive account(s) within the app to remove the stored OAuth tokens from your device. You can also remove all locally stored app data by clearing the app's storage from Android settings or uninstalling the app.


Crash Reports

Data Sharing (Crash report)

Crash report emails may be delivered and stored by email service providers (for example, Gmail) solely for the purpose of delivering and storing the crash report message in our support inbox.

Data Storage & Protection (Crash report)

We store crash report emails in our support mailbox and restrict access to authorized Internity Labs personnel. We use reasonable security measures to help protect this information from unauthorized access, disclosure, modification, or destruction.

Data Retention & Deletion (Crash report)

Crash reports may be retained only as long as needed to troubleshoot and fix the issue, and may be deleted afterward. You can request deletion of crash report data by emailing InternityLabs@outlook.com. If available, please include your app instance ID ("DeviceId") and the approximate date/time of the crash report so we can locate and delete the relevant message(s).

Types of data collected (Crash report)

In case of an exception during the operation of the app, the following limited crash report data may be collected and sent to Internity Labs.

• Code stack trace (exception stack trace) and related error details
• Version of Android on your device
• Device language
• Version of the Win-X Launcher app on your device
• App instance ID ("DeviceId") — a randomly generated identifier associated with this app installation

Example crash report (redacted) (Crash report)

The following is an illustrative example of what a crash report may look like. Identifiers and sensitive details (such as account identifiers, advertising IDs, file names, or full paths) are not included. The "DeviceId" shown below is a randomly generated app instance ID.

AndroidVersion: 22
DeviceLanguage: en-PH
AppVersion: 30.3
DeviceId: 12345678  (randomly generated app instance ID)
Error: System.UnauthorizedAccessException: Access denied
  at <YourAppNamespace>.<SomeMethod>(...)
  at <YourAppNamespace>.<AnotherMethod>(...)
Method of data collection (Crash report)

The app programmatically sends the crash report via email to an account associated with Internity Labs.

How we use the data (Crash report)

Crash reports are used only to identify, troubleshoot, and fix app issues. We do not sell crash report data and we do not use it for advertising, analytics, profiling, or marketing.

Where the data is stored (Crash report)

Crash reports are stored in our support mailbox. We do not maintain a separate database of user data.

How long we keep the data (Crash report)

Crash reports may be retained only as long as needed to troubleshoot and fix the issue, and may be deleted afterward.

Who can access the data (Crash report)

Crash reports may be reviewed by Internity Labs personnel as needed to diagnose and resolve the problem. We take appropriate security measures to prevent unauthorized access, disclosure, modification, or unauthorized destruction of the crash report data.

App permissions granted to it by the user

App requests permission to certain features from your mobile device, including your mobile device's bluetooth, microphone, storage, notifications, location, and other features, but we do not collect or receive this information. It is only used by the app on your device, and it does not leave your device unless a crash report is sent during an exception as described above.

Changes to this privacy policy

The Owner reserves the right to make changes to this privacy policy at any time. It is strongly recommended to check this page often, referring to the date of the last modification listed at the bottom. We have no direct means to inform the users about the privacy policy updates.


Latest update: February 20, 2026