Legal
Last updated 2026-09-04 · Terms · Privacy
This notice explains what legit2compute collects, what it deliberately does not keep, and who else touches your data. It applies to customers using the API and to contributors running a node. The controller's legal entity and contact details will be published here before general availability.
Account. The email address and identity provided by the sign-in service you use, your account settings, and your credit balance and ledger (purchases, spend, refunds, payouts). Payments are handled by Stripe; we receive a confirmation and a transaction reference, never your card number. API usage. For every request: the model or pipeline, token counts, latency, status, and, when a request fails, an error category. This is what your Activity page and your bill are built from. Job data. The inputs you submit to a pipeline (for example a video URL or a script) and the files produced for you are stored as job data until you delete the job; delivered files are kept for download for a limited time. Node telemetry from contributors: hostname, hardware, utilization, software version, and the network address the node connects from, used to schedule work and to pay for it.
The prompts and outputs of language-model requests are not stored, not written to logs, and not shipped to any log pipeline by the platform. The machine that answers a request processes it in memory, as any inference host must, and forgets it afterwards. On the shared tier that machine may belong to an approved contributor; on the private inference tier it is a machine we own or contract. Contributors never see which customer's work they are serving.
The websites set one session cookie so you stay signed in. There are no advertising or third-party tracking cookies.
The status page shows fleet capacity and a contributor leaderboard under pseudonymous handles. It never shows machine names, network addresses, or account identities.
Stripe (payments), Cloudflare (storage and delivery of generated files), our transactional email provider (account and billing email), and, for shared-tier work, the contributor whose hardware runs it. Each receives only what its role needs. We do not sell personal data and do not use your inputs or outputs to train models.
Billing records are kept for as long as the law requires. Usage metadata is kept to produce your statements and to operate the Service. Job data stays until you delete the job; generated files expire from delivery storage after a limited period. Account data is deleted on request, except for records we must keep.
You can export or delete your account data, correct it, or ask what we hold, by contacting us (details to be published above). Where data protection law gives you further rights, including the right to complain to a supervisory authority, they are unaffected by this notice.