Vibe Coder Android
Sia Makerlab 제품 포트폴리오 통합 페이지에서 제공하는 개인정보처리방침입니다.
Last Updated: May 25, 2026
Effective Date: May 25, 2026
Revision: 1.2
| Version | Date | Changes |
|---|---|---|
| 1.2 | May 25, 2026 | Re-aligned the policy with the project's README.md, which scopes the Android app as a single-user LAN console for vibe-coder-server (login, prompt send, log streaming, APK download, install-screen open). Removed CHANGELOG-derived disclosures that the README itself does not document: optional TOTP 2FA, voice-to-text input (RECORD_AUDIO), background notification polling (POST_NOTIFICATIONS, ACCESS_NETWORK_STATE for the poller), the notification deep-link intent filter (app://vibecoder/<path>), and the in-app Admin screen for server user mutation. The permission list now mirrors the README's stated capabilities (LAN networking and APK install). |
| 1.1 | May 25, 2026 | Reflected 2026-05 repo split and DataStore token storage; added TOTP / voice / notification polling / deep-link / Admin disclosures. (Superseded by v1.2.) |
| 1.0 | May 18, 2026 | Initial release. |
This Privacy Policy describes how Sia Makerlab ("we," "us," or "our") collects, uses, and shares information in connection with your use of the Vibe Coder Android mobile application and the companion Vibe Coder Server software (collectively, the "Service").
Vibe Coder Android is a remote-console developer tool. The Android app signs in to a Vibe Coder Server that the user runs on their own PC inside their own local area network. All project source code, prompts, build artifacts, Git history, and uploaded files remain on the user's own PC at all times. We do not host, receive, or have access to any of that data.
As of v0.4.x (May 2026), the Android client (vibe-coder-android) and the server (vibe-coder-server) are distributed as two separate Git repositories, kept wire-compatible through a shared :shared JVM module that defines DTOs, API paths, and WebSocket frames. The two components communicate exclusively over your own local area network.
By downloading, installing, or using the Service, you agree to the collection and use of information in accordance with this Privacy Policy. If you do not agree with this Privacy Policy, please do not use the Service.
The Service does not require you to create an account with Sia Makerlab. On the Connect screen the Android app asks for four values, all of which are used only against your own server:
http://<PC IP>:17880)http://<PC IP>:17880/admin) and stored only on your own PCWe do not collect:
The Android app stores the following data locally on your device only:
| Data Type | Stored | Location | Transmitted | Purpose |
|---|---|---|---|---|
| Server URL | Yes | Device only | Only to your own server | Remembers your Vibe Coder Server LAN address |
| Username and device label | Yes | Device only | Only to your own server | Pre-fills the Connect screen and identifies the device on the server |
| Bearer session token | Yes | Device only (Jetpack DataStore) | Only to your own server | Authenticates you to your own Vibe Coder Server |
| Last-selected project ID and UI preferences | Yes | Device only | Only to your own server (project ID) | Restores the last project on app launch; theme/display settings |
This data is stored exclusively on your device using Android Jetpack DataStore. As documented in the project README, Vibe Coder Android is a single-user LAN tool; the bearer token is intentionally not wrapped in the Android Keystore so that the same token may be presented as either an Authorization: Bearer header or a vibe_session cookie. Treat any device that has signed in as a trusted device, and sign out (or clear app data) before handing the device to anyone else. We do not have access to this data, and it is never transmitted to our servers.
Passwords are sent only to your own Vibe Coder Server during the login exchange and are not retained on the Android device after a session token has been issued.
The Vibe Coder Server, which you run on your own PC, stores the following data locally. This data never leaves your PC unless you choose to transmit it:
| Data Type | Stored | Location | Transmitted | Purpose |
|---|---|---|---|---|
| User accounts (username, password hash) | Yes | Your PC only | No | Authenticate sign-in requests from the Android app |
| Session records (token hashes, device labels) | Yes | Your PC only (hash-only) | No | Authenticate incoming API and WebSocket requests |
| Registered project paths | Yes | Your PC only | No | Locate Android projects on your filesystem |
| Build artifacts (APK files) | Yes | Your PC only | Streamed only to your signed-in Android device on download | APK installation on the phone |
| Claude / Gradle / Git logs | Yes | Your PC only | Streamed only to your signed-in Android device | Live log viewing on the phone |
Passwords are stored as cryptographic hashes only; the plaintext password is never recoverable from the server database. Session tokens are likewise stored as hashes only.
Traffic between the Android app and the Vibe Coder Server occurs entirely over your own local area network. The Service does not route any of this traffic through Sia Makerlab's servers, and we cannot observe or log it.
The console WebSocket performs authentication by sending {"type":"auth","token":"..."} as the first frame after connect; the token is never placed in the connection URL.
In line with the capabilities documented in the project README (LAN networking to the companion server, APK download, and opening the system install screen), the Android app's manifest declares:
Required to communicate with your Vibe Coder Server over LAN.
Required to open the system "Install unknown app" screen for the debug APK that you yourself built and downloaded. The Service does not silently install anything.
The app reads its own downloaded APK file from app-private storage in order to launch the install intent. It does not read other apps' files, photos, or documents.
The Android app does not collect microphone audio, camera images, contacts, or precise location at the policy level documented here. If a future build introduces an additional Android permission, this policy will be updated to reflect it before that build is released.
We explicitly do not collect:
All locally stored data is used solely to:
The Service does not integrate any analytics SDK, advertising SDK, crash-reporting SDK, or telemetry pipeline. We receive no usage data from the Service.
We do not sell, trade, or rent your personal information to third parties. We do not have access to your project data, prompts, or build artifacts in the first place.
The Android app does not integrate any third-party analytics, advertising, or telemetry SDKs. The Vibe Coder Server invokes third-party command-line tools (claude, git, gradle / gradlew) that you have installed on your own PC. These tools are governed by their respective licenses and privacy policies:
When you send a Claude prompt through Vibe Coder Android, your prompt and any relevant file context are transmitted by the Claude CLI installed on your own PC directly to Anthropic, under your own Anthropic account. Sia Makerlab is not in that data path.
We may disclose information we hold (which is essentially limited to Google Play developer-account contact data and store metadata) if required to do so by law or in response to valid requests by public authorities.
Data stored locally on your device remains until you:
Data stored locally on your PC by the Vibe Coder Server remains until you delete the server's data directory, revoke a signed-in device, delete the user account from the admin console, or uninstall the server.
You have the right to:
Under GDPR and applicable laws, you have additional rights including the right to access, rectification, erasure, restrict processing, data portability, object, and withdraw consent. Because we do not host, receive, or process the project data that flows through the Service, these rights are exercised by you directly against your own PC's filesystem and database.
California residents have the right to know, access, delete, and opt out of the sale of personal information. We do not sell personal information as defined by the CCPA/CPRA.
We implement appropriate technical and organizational measures in the Service's design to protect your data:
Authorization: Bearer header or a vibe_session cookie by the server, simplifying the LAN client without expanding the trust surfaceNetwork transport between the Android app and the Vibe Coder Server occurs on your own LAN; security on that network segment (Wi-Fi password, isolation from untrusted devices) is the user's responsibility. As noted in §2.2.1, the Android session token is stored in Jetpack DataStore without Keystore wrapping — appropriate for a single-user LAN tool, but treat your device accordingly.
The Service is a developer tool intended for software developers. It is not directed to children under 13 (or under 16 in the EEA). We do not knowingly collect any personal information from children.
We do not transfer your project data internationally because we do not receive it. Any international transfer that occurs (for example, when the Claude CLI on your PC transmits a prompt to Anthropic) is governed by the respective third party's privacy policy.
The App may contain links to third-party websites or services (for example, Anthropic, Gradle, or Git documentation). We are not responsible for the privacy practices of these third parties.
We may update this Privacy Policy from time to time. We will notify you of any changes by updating the "Last Updated" date and displaying a notice within the App for material changes.
We are not responsible for the data collection, use, or security practices of third-party services invoked by the Vibe Coder Server, including the Anthropic Claude CLI, Git, and Gradle.
We are not responsible for the security configuration of the local area network on which you run the Vibe Coder Server. Running the server on an untrusted or publicly-exposed network is strongly discouraged.
We are not responsible for any loss of data stored locally on your device or on your PC.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, WE SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES RESULTING FROM YOUR USE OF THE SERVICE.
This Privacy Policy shall be governed by the laws of the Republic of Korea. For EU users, it shall be interpreted in accordance with applicable EU law including the GDPR.
Sia Makerlab
For GDPR-related inquiries from EEA residents, please include "GDPR Request" in the subject line.
| Data Type | Collected by Us | Stored | Shared | Purpose |
|---|---|---|---|---|
| Server URL / Username / Session token | No | Android device only (DataStore) | Only to your own server | Sign in to your PC server |
| Password | No | Not retained on the Android device after sign-in | Only to your own server | One-shot login exchange |
| Project source / prompts / build artifacts | No | Your PC only | Not by us | Local development |
| Claude / Gradle / Git logs | No | Your PC, streamed to your phone | Not by us | Live log viewing |
| Personal info | No | N/A | No | N/A |
| Location | No | N/A | No | N/A |
| Camera / Microphone | No | N/A | No | N/A |
| Analytics / Telemetry | No | N/A | No | N/A |
| Advertising ID | No | N/A | No | N/A |
This Privacy Policy is available in English. If translated versions are provided, the English version shall prevail in case of any discrepancy.