ACE Cloud Legal · Draft
DRAFT — for Armored Gate / counsel review and approval before use. Not legal advice.
This draft is grounded in a direct audit of the ACE-Cloud codebase (Android appcom.armoredgate.cloud, the Go control-plane API, and the database schema) performed
2026-07-09. Where the draft states a data practice, it reflects what the code actually
does as of that audit. Entity (Armored Gate LLC) and governing law (United States,
State of Oklahoma) are confirmed final by Karl. Hosting URLs and remaining items are
marked [CONFIRM] and must be settled by Karl / counsel before publication.
Effective date: [CONFIRM — publication date] Last updated: [CONFIRM] Applies to: the ACE Micro Cloud Android application (Google Play package com.armoredgate.cloud, "ACE Micro Cloud" / "Be the Data Center") and the ACE Cloud control-plane service it connects to.
ACE Micro Cloud is operated by Armored Gate, LLC ("Armored Gate," "we," "us"), the data controller for the personal data described in this policy.
The ACE Micro Cloud IP (ACE engine, Visual Transport) is owned by PARCS; Armored Gate distributes and operates the ACE Cloud service, and Armored Gate, LLC is the operator of the app and controller of your data.
ACE Micro Cloud is a device-contribution app. When you enroll, your Android device runs background compute or bandwidth workloads on behalf of ACE Cloud customers, using spare capacity (primarily while charging and idle). In return you may be paid (via Stripe Connect) or you may contribute to a community pool (non-monetary).
Because your device does real work for others, this policy is deliberately specific about the small, technical set of data we collect and the large set of data we never touch.
The app is engineered so that it cannot access, and does not collect, share, or transmit:
ANDROID_ID, Build.FINGERPRINT, oradvertising ID — the app identifies your device by a random identifier it generates on first launch** (see §4.1), not by any hardware identifier.
The app declares no permission that would allow any of the above (see §12 and permissions-and-disclosures.md).
All collection below is for the operation of the contribution service. We do not use any of it for advertising, and we do not sell it.
stored in the app's private storage (SharedPreferences, key ace_cloud_device).
ANDROID_ID, the hardware serial, IMEI, or Build.FINGERPRINT. Clearing the app's data or uninstalling generates a new one.
scheduled to it and earnings attributed to it.
device's device_fingerprint / id.
Audit note for counsel (README decision): An older internal build path and the
server schema use the field namedevice_fingerprint. In the current shipping Android
client this value is a random per-install UUID, not a composite hardware
fingerprint. No code in either Android app readsANDROID_ID,Build.FINGERPRINT,Build.SERIAL, or a CPU serial. If any future build introduces hardware-backed
attestation (a "separate feature" noted in the code), this policy and the Data Safety
form must be updated before that build ships.
Collected once at enrollment ("qualification") and when specs change, to decide whether your device is eligible and which workload tier it can run:
your SSID, not your carrier, not any network content
Reported periodically while the service runs, so the resource governor can protect your device and so contribution can be measured and paid:
charging status, battery temperature, thermal state
These are resource statistics about your own device. They do not include the identity, content, or purpose of any workload (see §8, invisibility).
notifications. Provided by you.
device.
(Supabase auth.users). Authentication tokens (bearer + refresh) are issued to the app and stored in the app's private storage.
organization pool, we record that association and, where applicable, your recorded consent to share device status with that organization.
fcm_token) and sent to Google (Firebase) todeliver messages. See §7 (third parties).
ACE Cloud message broker for real-time control (workload dispatch, governor directives).
and your earnings and payout records (amounts in cents, currency, period, status, Stripe transfer IDs).
documents, SSN/TIN, or other KYC details. Those are collected and held by Stripe through Stripe's own hosted onboarding flow, under Stripe's privacy policy. We never see or store them.
to issue tax forms (e.g. 1099-K). See contributor-agreement.md.
device's requests, for workload routing/compliance.
retained (last_geo_country), and only when the geo-resolver is enabled. The code comment and the resolver's default (no-op) behavior confirm the IP is used transiently and discarded.
(§4.3)
meet legal obligations
We do not use your data for advertising or profiling, and we do not sell it.
For users to whom GDPR/UK-GDPR applies, our bases are: performance of a contract (operating the contribution service you enrolled in), legitimate interests (security, fraud prevention, service integrity), consent (optional items such as cellular use and organization data-sharing, which you can withdraw), and legal obligation (tax/payment records). ACE Micro Cloud is a US service; see §11.
We share the minimum necessary with service providers acting on our behalf:
| Recipient | Data | Purpose |
|---|---|---|
| Google (Firebase Cloud Messaging) | FCM token; message payloads (operational) | Push delivery |
| Stripe (Stripe Connect Express) | Email, country, payout amounts; you provide KYC/bank data directly to Stripe | Identity verification & payouts |
| Supabase / our hosting | All control-plane data described above | Database & auth hosting |
| Organization / sponsor (only if you join their pool) | Your device status/compliance signals, per your recorded consent | Pool administration |
We do not share workload-identity data with contributors, and we do not share your data with advertisers or data brokers. We may disclose data if required by law or to protect rights, safety, and the integrity of the service.
By design, when your device runs a workload you see only resource statistics about your own device (CPU, RAM, battery, bandwidth, earnings). You do not see, and the app does not expose to you, the identity, owner, domain, content, or purpose of the workloads your device runs. This protects both the workload customer's confidentiality and keeps you out of any custody of others' data.
service operation and contribution verification, then aged out.
active and, after deletion, only as required for financial, tax, and anti-fraud obligations (payout/tax records may be retained for the legally required period even after account deletion).
account-data-deletion.md and §10. What is deleted vs. lawfully retained is described there.
retention exceptions in §9). Contact privacy@armoredgate.com or use the in-app account controls.
with an organization). Withdrawing consent for organization sharing is available in-app.
including the right to lodge a complaint with a supervisory authority.
We do not discriminate against you for exercising these rights.
ACE Micro Cloud is operated from the United States and data is processed there and by the processors in §7. If you use the app from outside the US, you consent to processing in the US. [CONFIRM whether the app is offered outside the US; if so, add transfer-mechanism language.]
The app requests only: foreground service (to keep the contribution service running visibly with a persistent notification), notifications (POST_NOTIFICATIONS), internet / network-state (to communicate and read Wi-Fi-vs-cellular type), and — in builds that enforce workload network policy — VPN service (to confine workload traffic only, with a separate on-screen consent). No location, camera, microphone, contacts, storage-media, SMS, or phone permission is requested. Full detail: permissions-and-disclosures.md.
ACE Micro Cloud is not directed to children and is intended for users 18 and older (you must be able to enter a contributor agreement and, for payouts, satisfy Stripe's age and identity requirements). We do not knowingly collect data from children. If you believe a child has used the app, contact privacy@armoredgate.com and we will delete the data.
Data in transit is encrypted (HTTPS/TLS; the app disables cleartext traffic). Control-plane data is stored in access-controlled, least-privilege databases. Signing/attestation is used to ensure only authorized, signed workloads run on your device. No system is perfectly secure, but we design for least-collection and least-exposure.
We will post changes here and update the "Last updated" date. Material changes affecting how we use your data will be surfaced in-app.
Questions or requests: privacy@armoredgate.com (also reachable via legal@ / security@armoredgate.com). Postal: [CONFIRM].