A1Run

A1Run Privacy Notice

Effective date

Effective November 6, 2026. This notice describes A1Run and its related account, command, fleet and agent services.

Scope and contact

Apogee1 LLC provides A1Run and the related console at https://a1-run.cloud.run/. This notice describes local tools, optional account features, command synchronization, remote jobs, fleet controls and MCP connections. For questions or privacy requests, email contact@apogee1.net. The Apogee1 website privacy policy also describes website and business-contact practices.

Information kept on your device

Local settings, command history, files, recordings and tool results may remain on your device unless you use a cloud feature, share or export them, or run a command that sends data elsewhere. Uninstalling the app does not automatically delete cloud records or copies you exported. Your commands and integrations determine what information they access and send.

Account information

When you sign in with Google, Firebase Authentication processes your account identifier and authentication information. A1Run also stores available name, email address and profile-photo URL in its Firebase database to identify your account and display your profile. Signing in is optional for local tools, but required for account-based features.

Device registration and messaging

For signed-in devices, we store an Android device identifier, push-messaging token, manufacturer and model, Android and app versions, available tools, enabled and agent-ready flags, and last-seen timestamp. We use these to identify your devices, show available commands and deliver remote-job notifications. Firebase Cloud Messaging also uses a Firebase installation identifier and technical SDK information to provide messaging, which can be processed before sign-in. Google Firebase services and the hosting service may process IP addresses, service activity and technical security information needed to operate the service.

Commands, profiles and results

Signed-in features store saved commands and descriptions, account-linked app profiles and variables, and remote-job or fleet-run records. These records can include command text, arguments, target devices, timestamps, status and returned output. Commands can return personal information, including location, files, installed or running app information, app usage, network or device diagnostics, and other content available under the permissions you grant. Such content is transmitted to our cloud when included in a remote job or synchronized record. Do not include secrets in commands, variables or output.

MCP and third-party agents

Authorizing an MCP connection stores its name, client identifier, connection status, authorization records and token records. The connected agent can receive the tool catalog, device information and command results allowed by that connection. Your agent provider’s own terms and privacy notice apply to information it receives. Revocation stops future authorized use of that connection, but does not recall results already delivered. The separate planning tools in the web console may send prompts and context you submit to configured AI providers to generate a response.

SMS and permissions

The replacement Google Play release, version 3.10.2 and later, removes restricted SMS permissions and SMS tools. Earlier published Google Play versions may still include SMS features. Direct-install editions can continue to offer SMS tools after you grant Android permissions. SMS content can be transmitted if you explicitly run a supported remote tool or command that returns it. Location, camera, microphone, files and other Android permissions are used by the tools you choose. Optional camera and microphone streaming tools can transmit video and voice or sound recordings to a destination you choose. Granting a permission does not by itself mean that every result is uploaded.

Why we use information

We use account and device data to authenticate users, synchronize selected information, deliver notifications, execute and display requested jobs, manage authorized agents, provide support, troubleshoot failures, protect the service and meet legal obligations. We do not use A1Run data for advertising or sell it. Depending on applicable law, processing may be needed to provide the requested service, protect legitimate security and operational interests, comply with law, or act on your consent.

Who receives information

Google Firebase provides authentication, database and messaging services, and Google Cloud hosts the console and gateway. These providers process information for service delivery. Agents, destinations and recipients you choose can receive information as part of your requested actions. Marking a saved command as global makes it available to other app users, so do not publish private command text or personal information there. We may also disclose information to meet valid legal requirements, protect rights and safety, or complete a business transfer with appropriate safeguards.

Retention and deletion

Saved records and remote-job outputs do not currently have an automatic deletion schedule. A job or token’s execution expiry is not a promise that its stored record has been deleted. You can remove your personal saved commands using the app and revoke MCP connections in the console. To request account and associated cloud-data deletion, use the linked deletion page. Requests include authentication records, profile and registered devices, private saved commands and profiles, job and fleet-run records, and account-linked MCP authorization records. We may retain limited information where necessary for security, disputes or legal obligations and explain any exception when handling a request. Provider backups and logs follow their applicable retention processes.

Security and international processing

Connections to our cloud services use HTTPS, authenticated account-based access and revocable MCP connections. Some optional device tools can connect to destinations you choose using unencrypted local HTTP, RTSP, UDP or other protocols. Choose secure destinations and trusted networks, and do not send sensitive information over an unencrypted connection. These measures reduce risk but cannot guarantee security. Information may be processed in the United States and other countries where our providers operate. Applicable safeguards and legal requirements govern international transfers.

Your choices and rights

You can use local tools without signing in, manage Android permissions, sign out, remove your private saved commands, and revoke connected agents. Depending on your location, you may have rights to access, correct, export, delete, restrict or object to processing, withdraw consent, and contact a data-protection authority. Email contact@apogee1.net to make a request. We may need reasonable verification, but do not send passwords, tokens or identity documents by ordinary email. A1Run is not directed to children. If you believe a child’s information has been provided, contact us.

Changes

We identify the effective date above. Material changes will receive notice or consent where applicable law requires it. Contact us with questions about this notice or your data.

Related pages

A1Run terms · A1Run privacy · Account deletion · Email Apogee1