New Product

ViTiny_USB_Microscope Privacy Policy

ViTiny USB Microscope Privacy Policy (Android, Windows and Linux)

Effective date: August 17, 2026
Last updated: August 17, 2026

This Privacy Policy applies to the **ViTiny USB Microscope** software provided by **Microlinks Technology Co.** for Android, Windows, and Linux (collectively, the “Software”). An edition may also be identified within the Software as **ViTiny UM**, where “UM” means “USB Microscope.” The covered editions use the ViTiny product name and logo, but features, permissions, storage locations, and third-party components may vary by operating system and version. The platform-specific sections below form part of this Policy and control if they differ from the general sections.

## 1. Summary

The Software is designed primarily to operate a compatible ViTiny USB microscope and process microscope content locally on the user’s device or computer. Microlinks does not operate an application backend that receives microscope images, videos, recognized text, barcode results, measurements, automatic-measurement results, or image-processing results from the currently covered editions.

The currently covered editions do not provide a Microlinks user account, in-product advertising, or in-app payment function. Microlinks does not sell personal data obtained through the Software.

The Android edition includes bundled Google ML Kit components for optical character recognition (OCR) and barcode recognition. The Android-specific Google ML Kit disclosure in Section 5 does not automatically apply to the Windows or Linux editions.

## 2. Information processed locally

Depending on the edition, connected hardware, and features you use, the Software may process the following information locally:

- live or captured microscope images and video;
- image-processing and analysis results, including color, grayscale, edge, focus, field, denoise, HDR, and extended-depth-of-field results;
- OCR text and QR code or barcode results, where the edition provides those functions;
- manual measurements, automatic measurements, drawings, annotations, calibration data, and related settings;
- locally created VIX cases, diagnostic files, and exported reports;
- USB camera and compatible microscope-controller information needed to identify or operate the connected hardware; and
- operating-system, camera-format, resolution, focus, illumination, and other technical settings needed to provide, troubleshoot, or export a function.

These operations are primarily performed on the device or computer. The Software does not upload this microscope content to a Microlinks-operated application server unless a future feature clearly informs you otherwise and this Policy is updated before that feature is released.

## 3. Files you choose to save or export

Images, video, OCR text, measurement data, calibration data, VIX cases, diagnostic files, and reports are written when you use a corresponding save, record, export, diagnostic, or case-creation function. Files remain on the device or computer, or in a local, removable, network, or cloud-synchronized storage location that you select or configure through the operating system.

You control these files. You may view or delete them with the Software, the operating system, or a file manager, subject to operating-system and storage-provider rules. Uninstalling the Software may not delete files previously exported outside the Software’s private storage. Files placed in a synchronized folder may also be copied by the synchronization provider.

If you choose to open, copy, back up, or share a file through another application, cloud-storage provider, device-backup service, email service, browser, network location, or website, that third party handles the data under its own terms and privacy policy. Microlinks does not control those third-party services.

Diagnostic files or exported reports may contain technical information about the connected microscope, camera format, software version, operating system, and settings. Review files before sharing them, especially when they may contain an image, annotation, file name, hardware identifier, device information, or user-entered text.

## 4. Information Microlinks does not collect through an application backend

For the currently covered editions, ViTiny USB Microscope does not provide:

- a Microlinks user-registration or sign-in system;
- advertising or advertising identifiers used by Microlinks;
- a Microlinks-operated cloud upload, synchronization, or behavioral-analytics service for microscope content;
- in-app purchases, payment processing, banking, or other financial functions; or
- sale of personal data by Microlinks.

Operating-system vendors, hardware drivers, application stores, distribution services, security software, update tools, browsers, or services that you independently choose may process their own technical data under their respective policies. Such third-party processing is not the same as collection by a Microlinks application backend.

## 5. Platform-specific practices

### 5.1 Android edition

The Android edition processes microscope workflows locally on the Android device. It may request Android permissions or approvals needed for a selected feature, including USB-device permission, camera access, and access to user-selected files or media. A compatible ViTiny microscope may expose both a UVC camera and a controller through USB, so Android may display more than one USB permission request.

The Android edition uses bundled, on-device Google ML Kit libraries for OCR and QR code or barcode recognition. According to Google’s Android ML Kit data-disclosure information, ML Kit may transmit limited information such as:

- application and device information;
- a per-install identifier; and
- performance, diagnostic, error, or usage telemetry associated with the ML Kit libraries.

Google states that the bundled on-device APIs do **not** send the input images, recognized text, or recognized barcode contents to Google. Google handles information it receives under its own terms and privacy policies. Users may review Google’s current ML Kit terms and Android data-disclosure information.

Files saved to Android shared or user-selected storage may remain after the Android application is uninstalled. The Android application’s Google Play Data safety declaration describes the Android package only; it does not describe the Windows or Linux editions and must remain consistent with this Android subsection.

### 5.2 Windows edition

The Windows edition may use Windows camera, USB, device-driver, and file-system interfaces to communicate with a compatible microscope and to open or save files. Windows, an installed driver, security software, backup software, or a user-configured cloud-synchronized folder may process technical or file information under the provider’s own terms and privacy policy.

The Windows edition does not use Android permissions or Google Play services. The Google ML Kit disclosure in Section 5.1 applies only to the Android edition unless a future Windows release expressly includes that service and this Policy is updated. Files exported to a Windows folder remain until the user, Windows, or a configured storage service removes them; uninstalling the Software may not remove exported files.

### 5.3 Linux edition

The Linux edition may use Linux UVC, USB, device-access, driver, library, and file-system interfaces to communicate with a compatible microscope and to open or save files. Depending on the Linux distribution, the user or administrator may need to configure device permissions, groups, or udev rules. The Linux distribution, installed packages, backup tools, or a user-configured synchronized folder may process technical or file information under their own terms and policies.

The Linux edition does not use Android permissions or Google Play services. The Google ML Kit disclosure in Section 5.1 applies only to the Android edition unless a future Linux release expressly includes that service and this Policy is updated. Files exported to a Linux file-system location remain until the user, operating system, or configured storage service removes them; uninstalling the Software may not remove exported files.

## 6. Permissions and connected hardware

The Software requests or uses only the operating-system permissions, device access, and file access needed for the feature you choose. You may manage available permissions and device access through the applicable operating system. Denying, revoking, or not configuring required access may limit related functions.

A compatible microscope may provide a UVC camera, a separate controller, or both. The Software may read device descriptors, model information, USB vendor/product identifiers, controller state, camera capabilities, and, where necessary for device compatibility or product functions, a hardware serial identifier. This information is processed locally for connection, compatibility, operation, calibration, diagnostics, or feature access. Review any exported diagnostic file before sharing it.

## 7. Third-party components and external links

The Software may contain third-party libraries needed for camera access, image processing, recognition, or file functions. Platform-specific third-party processing is described in Section 5 where applicable.

If you open a web address from the Software, the operating system sends the address to the browser or other application you select. The browser, destination website, network provider, application store, and any related third party may process information under their own privacy policies. Microlinks is not responsible for the privacy practices of third-party websites, applications, operating systems, drivers, or services.

## 8. Retention and deletion

Microlinks does not retain microscope content on a Microlinks application server because the currently covered editions do not upload that content to such a server. Locally saved and exported files remain until you, the device or computer, or a storage service you selected removes them.

You may delete local files through the Software, operating system, or file manager where permitted. Removing the Software may delete some application-private settings or files, but may not delete exported files, removable-media copies, backups, synchronized copies, or files saved outside the application’s private storage. Those copies must be deleted through the relevant device, computer, or third-party service.

## 9. Security

We design the Software so its main microscope workflows remain local to the device or computer. However, no device, computer, storage medium, network location, or method of electronic handling is completely secure. Protect your device or computer, exported files, and any removable, network, or cloud storage you choose to use. Avoid placing confidential information in images, annotations, file names, diagnostics, or reports unless you are authorized to do so.

## 10. Children

The Software is a microscope, image-processing, and measurement tool intended for users aged 13 and older. It is not designed to create child profiles or collect children’s personal information through a Microlinks-operated application backend. A parent, guardian, school, or organization is responsible for supervising use when required by local law or policy.

## 11. International use

You may use the Software in different countries or regions. Locally stored content remains under your control, but a third-party service that you choose may process data in other jurisdictions. For the Android edition, limited telemetry processed by Google is governed by Google’s policies and applicable law. Other platform providers process their own data under their respective policies.

## 12. Changes, new versions, and additional platforms

We may update this Privacy Policy to reflect software, platform, legal, or operational changes. We will update the “Last updated” date and publish the revised policy at the official policy page. Material changes may also be described in the Software, the applicable application store, release notes, or distribution channel when appropriate.

This Policy may continue to cover later Android, Windows, or Linux releases branded ViTiny USB Microscope only while their data practices remain within the disclosures above. Before a release adds a new platform, SDK, account, cloud function, analytics service, crash-report upload, licence service, update telemetry, advertising, payment, or materially different data practice, Microlinks will review and update this Policy and any applicable store disclosure. Using the same ViTiny logo or product name alone does not make different data practices identical.

## 13. Contact us

For privacy questions or requests relating to ViTiny USB Microscope, contact:

**Microlinks Technology Co.**
Email: **mltc@vitiny.com**
Website: **https://vitiny.com/en**
Intended policy page: **https://www.vitiny.com/privacy/vitiny-usb-microscope**

2026-Aug-18