Dualscan™ Share Suite privacy policy

Effective: October 28, 2026. Applies to the 1.3.2 Chrome extension and desktop suite.

Dualscan Share processes directories you choose and transfers files directly between those directories and the Git or AWS destination/source you authorize. There are no ads, analytics, telemetry services, publisher-operated transfer servers or automatic report uploads.

Selected files and metadata

Directory access is limited to user-selected File System Access handles. Repository downloads read pinned GitHub metadata, manifests, tracked paths and file bytes. Destination entries and existing bytes are read to detect collisions and verify content. Missing files are created only after review and consent; different existing files block writes. Read-only USB discovery does not modify the selected drive.

Discovery reads nested package paths, file sizes and modification times, Smart Switch backup information, marker hashes and optional local manifests. It can display a device description and relative snapshot identifier. It reads binary AndroidManifest.xml metadata to identify APK packages and build versions, and computes APK SHA-256 when release expectations are available. Current OEM expectations are requested from the fixed official GitHub repository at a resolved commit. Local inventory contents are not sent with that request. Encrypted Smart Switch payloads and opaque AppList/launcher data are not decrypted. Publisher APK signatures and encrypted app versions are not authenticated.

USB-to-Git publication sends the selected source contents and relative paths, commit information and necessary connection information directly to GitHub, GitLab.com or Bitbucket Cloud, after destination review and consent. Provider-designated Git LFS storage can receive binary objects and its supplied action credentials. S3 publication sends the verified complete dataset and protected project descriptor into a new random public dataset folder. Every object must pass anonymous read-back. All payload files are public; protect personal SSS additions with Smart Switch password or Samsung Account encryption before upload. The application preserves opaque bytes and cannot certify Samsung encryption. The publisher receives no copy and does not provision or change public access on the bucket. Providers receive normal network information, including the connecting IP address, and govern their services under their own policies.

Optional repository artwork at assets/dualscan-usb-c.png is fetched from the pinned source and checked before display. Otherwise the application displays its bundled image. The suite does not inspect unrelated tabs, browsing history, contacts or unselected filesystem locations. Repository scripts and instructions are never executed.

Credentials and host access

Git access tokens and manually entered AWS access-key/secret/session-token values remain in the open page's memory. They are cleared on disconnect or closing/reloading the workspace. AWS signing uses only the selected regional S3 endpoint. Git account authentication is confined to the selected provider API and validated LFS negotiation endpoint. Account tokens are not attached to arbitrary signed-storage hosts. No shared publisher OAuth secret, AWS account-login service or upload relay is bundled.

The extension requests exact HTTPS host grants for reviewed additional storage origins. Desktop host grants are approved in a native dialog and expire when the app exits. Its native HTTPS bridge rejects redirects and local/private network destinations, validates TLS, and exposes no general filesystem API to the renderer.

Credentials, signed action URLs/headers and filesystem handles are excluded from exported project files and evidence reports. Do not deliberately place secrets in filenames, project titles or source file contents if you intend to publish those files to a public repository.

Project files and local retention

A user-exported .dualscan project contains source locators, pinned Git or S3 identities, relative file paths, sizes and hashes, the core OEM specification and the full official original reference when applicable. File contents remain at the selected remote source. New exports use binary TypelockerProject2 AES-256-GCM protection with a shared app key. This prevents plain-text viewing, but the key can be recovered from the app. Use an optional user passphrase for confidential metadata. Legacy codec1 files remain readable. Manifest protection does not encrypt public S3 payloads. Optional passphrase encryption protects the project metadata using authenticated AES-256-GCM; the passphrase is not included in the file and there is no publisher recovery service. The TCU1:U compatible source locator is a URL encoding, not the full project-file codec.

The application can retain a transfer checkpoint, source plan, verification metadata and the selected destination handle in local IndexedDB. Explicit original-image baselines/references can retain relative protected paths, sizes, hashes and launcher observations. These contain no credentials. Chrome manages extension storage and directory permission; the desktop application uses a separate per-user profile. Retaining a handle does not bypass the platform's permission checks. Desktop portable binaries do not carry local checkpoints to another computer automatically.

Read-only connected-drive inventories and source handles remain in the page session. Project manifests and reports are downloaded only on explicit request or after an authorized backup completes. The desktop application's OS-open import reads only an explicitly opened regular .dualscan file, with a 32 MiB limit and changed-file/symlink checks; a renderer cannot submit an arbitrary native path. Exports use the platform's save workflow.

Use the checkpoint-clear and original-baseline controls to remove those local records. Uninstalling the Chrome extension removes its browser-managed extension storage; desktop app profile data may remain until removed through the operating system. Clearing local records does not delete transferred files, exported projects/reports, remote Git objects/branches or S3 objects. Cancelled publications can leave partial new remote data and AWS charges; remove or retain them through your provider account as appropriate.

User control and disclosures

You choose source/destination directories, repository or bucket, optional credentials, project passphrase and whether to export reports. Directory selection and remote publication/restore authorization are separate steps. Downloads support pause/resume where available; current operations can be cancelled. No failed or interrupted operation is labelled verified completion.

Information is used only to provide the requested transfers, discovery and integrity checks. The publisher does not sell it, use it for advertising, transfer it to data brokers, or use it for creditworthiness/lending decisions. A release that changes these practices must update this policy and the corresponding Store disclosures.

Downloads and support: Dualscan OS Share Suite. Product page: dualscan.cloud/share. For account-specific privacy requests, use the publisher contact shown on the Chrome Web Store listing.

Support and privacy contact

For support, privacy questions, or deletion requests concerning support correspondence, contact sa.cs2cd@gmail.com. Do not send access tokens, passwords, recovery phrases or private drive contents. If you contact support, the publisher receives the email address, message and attachments you choose to send and uses them to respond. Support correspondence may be retained as needed to resolve the request or satisfy applicable obligations; you can request its deletion at the same address.

Public help pages

Opening the instruction manual, privacy policy or other external help links visits the selected public website. These pages are hosted on GitHub Pages; GitHub processes normal connection information, including IP addresses, under its privacy statement. These help pages add no analytics, advertising trackers or account-registration form. Updates to this policy appear at the published policy URL with a revised effective date.