LEGAL · PRIVACY

Privacy Policy for OneAppDock

Effective Date: September 17, 2026 · Last Updated: September 17, 2026
Application: OneAppDock (Windows 11/10 & Android 11–17)
Developer: Yeasin Arafat Sadiq (www.sadiqtbh.info)
Website: www.oneappdock.com
License: Open Source under the MIT License

1. Overview & Core Philosophy

OneAppDock is built on a fundamental principle: your data belongs exclusively to you, and your privacy is non-negotiable.

OneAppDock is a multi-account command dock and productivity browser for desktop and mobile devices. It enables users to run isolated sessions for services such as WhatsApp, Gmail, Facebook, Messenger, Telegram, ChatGPT, Claude, and more, with optional per-tab proxy routing.

Unlike conventional browsers and commercial account managers:

  • Zero Cloud Telemetry: We do not collect, track, or upload your browsing history, clicks, search queries, or visited URLs.
  • Zero Remote Analytics: We do not include third-party tracking scripts, advertising trackers, or analytics SDKs (no Google Analytics, no Firebase Analytics, no AdMob, no tracking pixels).
  • Local-Only Processing: All session credentials, proxy configurations, workspaces, and cached files reside strictly on your physical device.
  • Zero Proprietary Proxy Relays: OneAppDock never routes your traffic through proprietary developer servers. When you assign a proxy to a tab, your device connects directly to your chosen proxy provider.

2. Information We Do NOT Collect

OneAppDock does not collect, store, transmit, or monetize any of the following:

  • Personal Information: We do not require or collect your name, email address, phone number, physical address, or billing details.
  • Account Credentials & Passwords: Logins, passwords, authentication cookies, tokens, and two-factor verification codes entered into embedded web services are processed directly by the respective service's encrypted HTTPS connection and are never accessible to, recorded by, or transmitted to OneAppDock.
  • Browsing & Search History: We do not track, log, or store URLs you visit, web pages you view, bookmarks, search history, or media you access.
  • Message Content & Keystrokes: All messaging, chat logs, draft messages, and file transfers take place strictly inside the isolated web engine between you and the destination service.
  • Proxy Credentials & Traffic: Proxy hostnames, ports, usernames, and passwords you configure are stored locally on your device. We never intercept, inspect, copy, or log your proxy traffic.

3. Data Stored Locally on Your Device

To provide multi-account isolation and application functionality, OneAppDock stores the following information locally on your device only:

  • Partitioned Web Sessions (Cookies & Local Storage): Windows: stored in your local user profile directory under %APPDATA%\OneAppDock\Partitions\. Android: stored in the app's sandboxed private internal storage under /data/data/com.example.oneappdock/app_webview/. Each account runs inside an isolated partition (persist:account_<id>), ensuring that cookies and session data never leak between tabs.
  • Tab & Account Metadata: Account names (e.g., "Personal", "Work"), custom URLs, service icons, badge counts, and display ordering.
  • Per-Tab Proxy Configurations: Protocol selection (http, https, socks5), host IP/domain, port, and optional authentication credentials. These are saved in your local settings store and used exclusively to establish network sockets initiated by that specific tab.
  • App Preferences: Theme (dark/light), auto-launch settings, dock style, hardware acceleration preferences, and desktop user-agent toggles.

None of this information is ever uploaded to our servers or accessible by third parties.

4. Device Permissions & Justification

OneAppDock requests only the minimum device permissions required for features you explicitly use:

Windows Version:

  • Network / Internet Access: Required to load web content and route traffic through user-configured proxies.
  • File System (Downloads / Local Storage): Required to save user-initiated file downloads and persist session data.
  • Local Loopback (127.0.0.1): Used by the internal zero-dependency SOCKS5 bridge to provide authenticated SOCKS5 proxy support without exposing data to the external network.

Android Version:

  • INTERNET & ACCESS_NETWORK_STATE: Required to load web content and check network availability.
  • CAMERA (Optional runtime permission): Requested only if you scan a QR code inside a web tab (e.g., WhatsApp Web QR code pairing) or use web video calls.
  • RECORD_AUDIO & MODIFY_AUDIO_SETTINGS (Optional runtime permission): Requested only if you record a voice note or participate in a voice/video call within a web service (e.g., WhatsApp, Messenger).
  • POST_NOTIFICATIONS (Android 13+): Requested to display notification badges and incoming message alerts from your active tabs.

You have full control over these permissions in your operating system settings and can grant or revoke them at any time.

5. Third-Party Websites & Embedded Services

When you use OneAppDock to access third-party web services (including but not limited to WhatsApp, Gmail, Outlook, Facebook, Messenger, Telegram, ChatGPT, Claude, and Binance):

  • Those services operate inside isolated web containers governed by their own terms of service and privacy policies.
  • OneAppDock does not control and is not responsible for the privacy practices, tracking cookies, or data collection policies of third-party platforms.
  • We strongly encourage you to review the privacy policies of any third-party services you access through OneAppDock.

6. Real-Time Proxy Validation Check

OneAppDock includes a Real-Time Proxy Validation feature:

  • When you click "Run Real-Time Proxy Validation Check" or "Test Connection", a direct TCP/TLS probe is initiated from your device to the proxy address you provided.
  • To verify that the proxy has successfully established an outgoing internet tunnel and to measure ping latency, a lightweight request is sent to api.ipify.org solely to identify your public exit IP.
  • No personal identifiers, cookies, or account details are included in validation requests.
  • The resulting IP address and latency are displayed exclusively in your local UI and are never stored or transmitted externally.

7. User Rights & Data Deletion

Because all data is stored locally, you have complete authority over your data retention:

  • Clear Specific Tab Session: In OneAppDock, right-click (or long-press on Android) any account and select Clear Session Data. All stored cookies, cache, local storage, and login sessions for that specific tab are immediately purged from your disk.
  • Delete an Account / Tab: Deleting an account removes its configuration, proxy settings, and session partition permanently.
  • Complete Data Removal: Windows: uninstall OneAppDock and delete %APPDATA%\OneAppDock. Android: uninstalling the app or tapping "Clear Storage / Clear Data" in Android Settings > Apps > OneAppDock permanently deletes all cached sessions, cookies, and preferences.

8. Children's Privacy (COPPA Compliance)

OneAppDock is a general productivity tool and does not knowingly collect or solicit personal information from children under the age of 13. Because OneAppDock does not collect personal information from any user, it does not process or share data relating to children.

9. Security Safeguards

Digitally Signed Releases: Windows installers are Authenticode-signed with code-signing certificates (http://timestamp.digicert.com). Android APKs are digitally signed with APK Signature Scheme v3.

Process & Context Isolation: Electron renderers operate with contextIsolation: true, nodeIntegration: false, and strict IPC boundaries. Android WebViews run in private app sandboxes with separated cookie managers and storage domains.

10. Open Source Transparency

OneAppDock is open source software released under the MIT License. Any developer, security auditor, or user can independently inspect the source code to confirm our zero-telemetry architecture.

11. Developer Contact Information

For questions, feedback, or inquiries regarding this Privacy Policy, please contact the developer: