Privacy Policy

PowerMesh operates a Distributed Mobile Computing (DMC) network. This Privacy Policy describes exactly what we collect from contributor devices, what we explicitly never collect, and the technical safeguards that enforce that boundary.

1. Data We Collect

To route tasks, verify computation, and calculate payouts, the PowerMesh client logs the following narrow categories of telemetry while you are an active contributor:

• Device hardware model. CPU architecture, SoC identifier, total RAM, and GPU availability. Used to match your device to compatible micro-tasks.
• Completed computing metrics. Verified FLOPS, task-completion latency, error rates, and per-task checksums. Used for Proof of Computation verification and payout calculation.
• Network bandwidth. Aggregate bytes uploaded and downloaded per session, plus connection type (Wi-Fi vs. cellular). Used for cluster routing and quality-of-service.

2. Data We Explicitly Exclude

PowerMesh is engineered around a strict data-minimization contract. The client runs inside a hardened sandbox and is structurally prohibited from reading any of the following:

• Personal media files (photos, videos, audio recordings).
• Contacts, call logs, SMS or messaging databases.
• Personal documents, downloads, or file-system contents.
• Authentication tokens, passwords, or credential stores.
• Browser history, cookies, or in-app activity.

3. How Data Is Protected

Every micro-task package delivered to your device is wrapped in end-to-end task package encryption. The encryption envelope is sealed by the Fragmentation Engine and can only be opened inside the PowerMesh sandbox for the duration of a single compute cycle. The sandbox has no shared file-system mounts, no IPC channels to other apps, and no network egress beyond the encrypted result-return endpoint.

Telemetry in transit between your device and PowerMesh infrastructure is always TLS 1.3. At rest, telemetry is sharded across region-pinned storage buckets and encrypted with AES-256 keys managed in an external KMS.

4. How We Use Collected Data

• Match your device to compatible enterprise compute tasks.
• Verify Proof of Computation and calculate Verified FLOPS payouts.
• Aggregate anonymous cluster health metrics for routing.
• Detect fraud, emulation farming, and terms violations.

5. Data Retention

Raw per-task telemetry is retained for 90 days for audit and dispute resolution, then permanently deleted. Aggregated, anonymized throughput metrics may be retained indefinitely for capacity planning. Payout ledgers are retained for 7 years to comply with financial record-keeping obligations.

6. Your Rights

You may request export or deletion of all telemetry tied to your account at any time from the in-app Privacy Center, or by emailing privacy@powermesh.example. Deletion requests complete within 30 days and cascade to all region-pinned storage buckets.

7. Changes to This Policy

Material changes to this Privacy Policy are announced at least 30 days before they take effect via in-app notification and email. Continued contribution after the effective date constitutes acceptance.

Questions? Contact the PowerMesh privacy team at privacy@powermesh.example.