Data we process
We process account identifiers, API keys in hashed form, provider hardware and health diagnostics, job metadata and results, billing records, security events, and support communications. Provider tokens remain stored on the provider computer.
Why we process it
We use this information to route and execute jobs, operate payouts, prevent abuse, diagnose failures, measure reliability, and meet legal obligations. We do not sell personal information.
Minimal website analytics
We record a small set of first-party product events to understand whether guides, downloads, and support paths work. These events may include a guide or section identifier, destination path, installer platform and release version, or the length of a failed FAQ search. We do not record the search text, workload prompts, payloads, results, credentials, or payment details in website analytics.
Independent providers
Pilot workloads run on computers controlled by independent providers. Providers can potentially observe workload inputs and outputs at the host level. Do not submit secrets, regulated data, or confidential business information during the pilot.
Retention and requests
We retain operational records only as long as needed for security, billing, dispute handling, and legal requirements. Contact support to request access, correction, or deletion where applicable.