Aleph Virux, published by Aleph Void LLC ("Aleph Void," "we," "us," or "our"), does not collect, transmit, sell, or share any personal data tied to your identity. The audio from your synthesizer, your patches, and your settings stay on your device. The macOS driver and plugins perform no network requests at all. The Android build may send a limited stream of anonymous diagnostic and usage data through Firebase Analytics and Crashlytics so we can measure stability and aggregate usage — details and the Google Play Data Safety disclosure are below.
Aleph Virux exists for one purpose only.
Aleph Virux is a userspace driver and synth plugin that connects an Access Virus TI hardware synthesizer to your computer or Android device over USB.
It lets musicians play and edit a Virus TI Snow, Desktop, or Polar from a modern host — streaming the synth's audio into your DAW, sending it MIDI notes and controller messages, and editing patches from an on-screen control surface. The software does not analyze your behavior, build a profile, or perform any activity unrelated to driving the connected synthesizer.
What we collect, transmit, and store — in plain English.
No personally identifiable information. Aleph Virux does not collect your name, email, contacts, precise location, browsing history, authentication credentials, financial data, health information, or communications. The Android build collects anonymous diagnostic and aggregate usage data via Firebase — see the Google Play Data Safety section below.
Audio and MIDI never leave your device. Everything Virux exchanges with your synth travels over the USB cable between the two of you and is processed locally. The macOS build performs no network transmission. The Android build transmits anonymous crash reports and aggregate usage events to Google's Firebase servers (Analytics and Crashlytics).
On your device only: your patches and presets, plugin / app preferences, and UI settings. On macOS this lives in the app's and plugins' standard support directories; on Android it lives in scoped app storage. It is retained until you delete it or uninstall the software, at which point the operating system removes it.
We do not sell user data and we do not share user data with third parties for advertising, credit assessment, or any purpose unrelated to the software. Firebase data on the Android build is processed by Google acting as our service provider under the Firebase Data Processing and Security Terms; we do not use it for advertising and we have not enabled Google Signals or ads personalization.
Each permission Aleph Virux requests on macOS and Android, and why it is required for the software to function.
On macOS, Virux talks to the Virus over USB from userspace via IOUSBLib; on Android it uses USB Host (android.hardware.usb.host) and the standard USB_DEVICE_ATTACHED flow so the system can offer to open Virux when the synth is plugged in. This is the software's core function — without it there is no connection to your synthesizer. No USB data is ever forwarded off the device.
The Virus is a class-compliant USB audio device, and both macOS (NSMicrophoneUsageDescription / TCC) and Android (android.permission.RECORD_AUDIO) group USB audio input under the microphone permission. Virux needs it to capture the synthesizer's audio output — that is the audio you hear in your DAW. It is not used to record your built-in microphone; the signal chain is simply the audio coming back from the Virus.
Virux sends MIDI notes, controller (CC) messages, and parameter changes to the Virus over its vendor control endpoints, and relays MIDI from your DAW or controller. MIDI data is used solely to play and edit the connected synthesizer and is never transmitted off the device.
Patches, presets, and settings are written to the software's own support and configuration directories — standard application support locations on macOS and scoped app storage on Android. No cloud storage, no shared folders, no access to other apps' data. Files remain on the device until you delete them or uninstall the software.
The macOS driver, container app, and plugins perform no network requests. The Android build embeds two Google client libraries that talk to Google's servers on its behalf: Firebase Analytics (aggregate usage) and Firebase Crashlytics (crash reports), both over HTTPS. No remote configuration, A/B testing, advertising SDK, or third-party analytics is embedded.
Aleph Virux does not execute remote code. There is no dynamic module loading, no remotely hosted scripts, and no runtime evaluation of downloaded payloads. All code is bundled inside the binaries you install. The project is open source, so the full source is available for inspection.
The data the Android build of Aleph Virux collects, why, and how it is handled — mirroring the Data Safety form in the Google Play Console. This section applies to the Android build only; the macOS build collects nothing.
The Android build embeds Firebase Analytics and Firebase Crashlytics (Google LLC). The data types below are collected automatically by these SDKs. Aleph Virux does not log custom events, set user IDs, or attach user properties beyond the SDK defaults.
| Data type | Category | Purpose | Required? | Source |
|---|---|---|---|---|
| Crash logs | App info and performance | Analytics, App functionality | Required | Crashlytics |
| Diagnostics | App info and performance | Analytics, App functionality | Required | Crashlytics, Analytics |
| Other app performance data | App info and performance | Analytics | Required | Analytics |
| App interactions | App activity | Analytics | Required | Analytics (auto-collected events: first_open, session_start, screen_view, app_update) |
| Device or other IDs | Device or other IDs | Analytics | Required | Firebase Installation ID (Crashlytics), App Instance ID (Analytics) |
For clarity, the following Data Safety categories are not collected by Aleph Virux: personal info (name, email, phone, address, identifiers tied to a real person), financial info, health and fitness, messages, photos, videos, audio recordings (your synth's audio stays on your device), files and docs, calendar, contacts, web browsing history, search history, installed apps, precise location.
Our certification under the App Store Review Guidelines and Google Play Developer Program Policies.
We certify that Aleph Virux's data usage complies with the Apple App Store Review Guidelines (including the App Privacy Details requirements) and the Google Play Developer Program Policies (including the User Data policy, the SDK policy, and the Families policy). Specifically:
The data controller responsible for Aleph Virux is Aleph Void LLC. We do not operate any servers that store user data. The Android build's Firebase Analytics and Crashlytics data is processed by Google LLC on our behalf as a data processor under the Firebase Data Processing and Security Terms. Aleph Void LLC remains the publisher accountable for this policy.
Aleph Virux is a tool for musicians and producers using Access Virus TI hardware. It is not directed at children under the age of 13 (or under 16 in jurisdictions where that is the applicable age). We do not knowingly collect personal information from children. Because the software does not collect any personal information from any user, no special handling for children's data is required.
Privacy laws such as the EU General Data Protection Regulation (GDPR), the UK GDPR, and the California Consumer Privacy Act (CCPA/CPRA) grant users rights including access, correction, deletion, portability, and the right to object to processing of their personal data.
Because Aleph Virux does not collect direct identifiers (name, email, account ID, government ID, device-level advertising ID) and does not sell or share user data, the personal data we hold about you is limited to the pseudonymous Firebase identifiers and aggregate event data described in the Google Play Data Safety section above (Android build only). All patches, presets, and preferences are stored locally on your own device, and you can view, edit, or delete them from within the software, from the system file manager, or by uninstalling it. To request access, correction, export, or deletion of the Firebase data tied to your installation, email privacy@alephvoid.com; we will respond within 30 days.
We do not "sell" or "share" personal information as those terms are defined under the CCPA/CPRA.
We may update this privacy policy from time to time, for example to reflect changes to the software's functionality, requested permissions, or applicable law. When we do, we will update the "Effective date" and "Last updated" fields below and post the revised policy at this URL. For material changes, we will additionally note the change in the release notes for the corresponding version. Your continued use of the software after a revised policy takes effect constitutes acceptance of the updated policy.
Questions, concerns, or reports about this privacy policy can be sent to privacy@alephvoid.com or filed as a public issue on our GitHub issue tracker. See also our Support page.
Effective date: May 25, 2026
Last updated: May 25, 2026