This policy explains what HiveCompute collects, how data is used, how long it is retained, and the deletion choices available during the beta period. It is a practical draft and still needs lawyer review.
HiveCompute collects account details you provide, API keys and partner configuration, submitted audio references, generated transcripts, billing records, support correspondence, and diagnostic events such as worker heartbeats, abuse detections, and manager sign-in activity.
We use this information to operate the coordinator, dispatch jobs, validate worker quality, prevent abuse, bill for usage, pay workers, and improve the product. We do not sell personal data.
Audio is split into short fragments and dispatched to workers. Workers receive the minimum data needed to transcribe a fragment. The current pilot is not designed for HIPAA-regulated or highly restricted audio.
Job inputs, transcripts, and operational metadata are retained only while needed for product operation, recovery, billing, and auditability. Backup media may retain copies for disaster recovery until they age out under the active retention window.
Subject to applicable law, you may request access to, correction of, or deletion of personal data that HiveCompute controls. EEA and UK users may also request restriction, objection, or portability where those rights apply.
HiveCompute generally processes data to perform a contract, operate legitimate business interests such as security and fraud prevention, and comply with legal obligations. Cross-border transfers may occur where the service or support providers operate.
We use HTTPS in transit, access controls for the hosted coordinator, manager authentication with passkeys, logging, and operational safeguards. No security program is perfect, and beta systems change frequently.
HiveCompute may update this draft as the product and legal review progress. Material changes will be reflected on this page before broad public launch.