Privacy Policy

1. Scope

This policy explains how AppBridge Inc. handles information in Agentlas Mobile, the companion controller for Agentlas Desktop. It applies to the mobile app and its connections to Desktops paired by you, including the optional Agentlas Cloud relay.

2. Current product architecture

Agentlas Mobile uses your Agentlas account sign-in; it does not create a second, mobile-only account and does not run agents on your phone. After sign-in, it first tries a direct connection to an account-verified paired Desktop on the same local network or through a Tailscale connection that you configure. If direct access fails and a Cloud relay route is available, it connects through the Agentlas Cloud relay. The public Privacy and Support pages remain available without signing in.

The app contains no advertising or mobile analytics SDK. Agentlas servers may retain request paths, response status, processing time, and connection error identifiers to operate and diagnose the service.

Mobile subscriptions are purchased through Apple App Store or Google Play billing. New one-time credit-pack purchases are closed; past purchases remain available in payment history and for refund support. The app sends store transaction proof and the signed-in account binding to the Agentlas billing verifier; payment credentials stay with the store, entitlements are applied only after verification, and Mobile never opens Paddle or another web checkout.

3. Information stored on the phone

The app stores language and onboarding preferences on your phone. For each paired Desktop, it stores the Desktop and device identifiers, connection endpoint, certificate verification material, and a revocable device credential in the operating system's secure storage.

The Agentlas account session and pending sign-in state are stored in the operating system's secure storage. Raw OAuth proofs are not shown to paired Desktops, and account sign-out clears the local account session after device authority is revoked or queued for revocation.

These records remain until you disconnect the Desktop, clear the app's data, or remove the app.

4. Information shown from Desktop

After pairing, the app can display information reported by Desktop, including agent and group names, Desktop names and connection status, chat text, run status, approval requests, automation status and history, artifacts, and LLM subscription usage windows.

This information moves between your phone and paired Desktop, directly or through the Agentlas Cloud relay when that route is used, to provide the features you request. The relay forwards connection traffic and handles route identifiers; the current app does not send this content for analytics or advertising.

If you attach photos to a chat or send messages, titles, and control choices, the app sends them to your paired Desktop, which can retain the conversation, attachments, and action history. A Cloud relay route, when used, forwards that traffic while handling connection identifiers.

5. Device permissions

Camera access is used only to scan the one-time pairing QR shown by Agentlas Desktop. The app does not save a photo of the QR. Local-network access is used to find and connect to your Desktop. Notification permission is used for optional Agentlas notifications that you select.

Voice input is optional. When you use it, the operating system's speech recognition service may process your voice, including on remote servers. The recognized text is sent to Desktop only when you choose to submit it. You can use text input instead.

6. How information is used

Information processed by the app is used to establish and secure Desktop connections, show Desktop state, send commands that you request, return approval decisions, and remember app preferences.

7. Sharing and tracking

The current app does not sell personal information, share personal information for cross-context behavioral advertising, serve ads, or track you across apps and websites. It contains no third-party advertising or mobile analytics SDK.

Agent work started through Mobile may use services configured separately on Agentlas Desktop. Those services and credentials remain under Desktop control and are governed by their own terms and privacy policies.

8. Retention, deletion, and credential revocation

When you disconnect a Desktop in Mobile, the app asks that online Desktop to revoke the phone credential and removes the local connection record after Desktop confirms revocation. You can also revoke a paired phone from Agentlas Desktop under Settings → Agentlas Mobile connection.

Removing the app or clearing its data removes locally stored preferences and connection records from the phone. Content retained by Desktop must be managed on that Desktop or in the service that created it.

9. Security

Non-loopback Desktop connections use encrypted WSS and certificate verification. The one-time pairing QR expires after two minutes and does not include a long-lived device key or Desktop secret. No network or storage system can be guaranteed to be completely secure.

10. Children

Agentlas Mobile is not directed to children under 13, and AppBridge Inc. does not knowingly collect personal information from children under 13 through the mobile app.

11. Changes

We may update this policy when the product or applicable requirements change. The updated date will appear at the top of this page.

12. Contact

For privacy questions, deletion assistance, or credential-revocation help, email appbridge@appbridge.co.kr.