Job Deployer Acceptable Use Policy

In short

This policy is part of your agreement with Distributive, or with the Licensee whose platform you use. By deploying work on the Distributive Compute Platform (DCP) you agree to it.

1. Who this applies to

• Anyone who deploys a Job on DCP ("you"), whether as an individual, an organization, or a user acting for an organization, and whether through Distributive's own Portal or a Licensee's branded platform.
• Anyone who writes or publishes a work function, module, or package intended for use in DCP Jobs, whether or not they deploy the Job that uses it. Authors and deployers are each responsible for what they contribute.
• If you use DCP under an agreement with a Licensee (for example a compute provider or broker that operates its own DCP platform), that agreement may add stricter terms. It cannot weaken this policy.

2. Your responsibilities

• Content. You are responsible for everything in your Jobs: input data, arguments, code, modules, and results. Distributive does not inspect Job content and cannot restrict it in advance.
• Where your Job runs. When you attach a Job to a Compute Group you choose which machines, and therefore which operators, execute it. The operator of a machine can technically access what runs on it. Choose Compute Groups whose operators you trust for the data involved.
• Personal, confidential, and regulated data. You decide whether a Job contains personal data (including pseudonymized data), confidential information, or data subject to sector rules. If it does, you are the party responsible under the applicable law, a data processing agreement with Distributive or your Licensee is required, and you must not route that Job to a public Compute Group. URL-bypass routing, which keeps Job content between your own systems and the Workers, is recommended for such Jobs.
• Routing mode. This policy applies identically whether Job content transits Distributive's Scheduler or stays on your own endpoints.

3. Prohibited content and activity

You may not use DCP, or help anyone else use DCP, for any of the following:

• Any activity or content that is illegal where you, the machines running your Job, or the people affected are located.
• Child sexual abuse material or any content that sexualizes minors. Zero tolerance. Distributive reports such material to the authorities as the law requires.
• Non-consensual intimate imagery, including synthetic or deepfake content depicting real people.
• Threats, incitement, or promotion of violence, terrorism, or serious harm against any person or group.
• Design, simulation, or development of weapons intended to cause mass casualties (chemical, biological, radiological, nuclear, or explosive).
• Unauthorized access, password cracking, credential stuffing, exploit development, or penetration testing against any system you do not own or have written authorization to test.
• Creating or distributing malware, including viruses, worms, ransomware, and botnet command-and-control infrastructure.
• Denial-of-service or availability attacks, including using DCP's distributed execution to direct traffic or load at any target.
• Infringing anyone's copyright, trademark, trade secret, or other rights, or circumventing technical protection measures.
• Generating or distributing spam or unsolicited bulk messages.
• Phishing, fraud, or impersonating any person or organization.
• Circumventing the safety mechanisms of a third-party AI model or service, or generating prohibited content at scale by automated means.
• Unauthorized cryptocurrency mining, or any scheme that misrepresents the nature of a Job to the people whose machines run it.

4. Protecting the machines that run your Jobs

The machines that execute your Jobs belong to other people and organizations. You may not:

• Attempt to escape the Worker sandbox or otherwise access the host machine, its storage, its network, or any data on it.
• Attempt to identify, fingerprint, track, or profile the machines or people hosting Workers, beyond what DCP's documented APIs return to you.
• Use any network access a Worker allows for any purpose other than your Job's legitimate data transfer, or use it to reach systems you are not authorized to reach.
• Submit Jobs designed to damage, degrade, or exhaust a host's hardware or resources.
• Consume Compute Group capacity in a way that degrades service for others beyond your allocation, or flood the Scheduler with Jobs that do no genuine work.

5. Accounts, keys, and credentials

• Keep your account credentials, API keys, and Compute Group keys (attachKey and attachSecret) confidential. Do not share them outside your organization, resell them, or use them to give access to anyone the Compute Group's administrator has not admitted.
• You are responsible for all activity under your account and keys.
• If you believe a key has been exposed, revoke it: delete it in the Keys tab of the Portal and issue a new one. Jobs and applications using the old key will stop working until you update them. Revoking is your decision; you are not required to report an exposed key to Distributive, but you remain responsible for activity under it until you do revoke it.
• Do not create additional accounts to evade a suspension or to circumvent a Compute Group's access controls.

6. Fair dealing with the network

• Do not manipulate, exploit, or circumvent DCP's escrow, payment, metering, or Compute Credit mechanics.
• Do not submit sham Jobs, collude with Worker operators to record work that was not done, or otherwise move Compute Credits through fake activity.
• Do not misrepresent a Job's purpose, resource requirements, or data classification to Distributive, a Licensee, or a Compute Group administrator.

7. Client libraries and published components

• You may modify your own local copy of dcp-client, bifrost2, or other Distributive-published libraries for your own use, as their open-source licenses permit.
• You may not publish or distribute a modified version under the DCP name, or in a way that could be mistaken for a Distributive release. Contribute fixes upstream instead.
• If you publish a module or package for use in Jobs, you are responsible for its content and behaviour under this policy, and enforcement may reach your publishing access as well as any Job that uses it.

8. Security research against DCP

Testing, probing, or scanning Distributive's own Scheduler, Bank, Portal, or other infrastructure requires Distributive's prior written authorization. Report vulnerabilities you find to ops@distributive.network.

9. Export control and sanctions

Your Jobs may be executed on machines in many countries. You are responsible for complying with the export control and sanctions laws that apply to you, your code, and your data, wherever you and the machines running your Jobs are located. You may not use DCP from, or for the benefit of, any sanctioned jurisdiction, person, or organization.

10. Legal compliance and law enforcement

• You will cooperate reasonably with any investigation of suspected violations.
• Distributive forwards infringement notices to the account concerned where applicable law requires, and may disclose information to authorities where the law requires or permits.
• Distributive is required by law to report child sexual abuse material it becomes aware of, and will do so.

11. How this policy is enforced

• Reporting. Report suspected violations to abuse@distributive.network. Include the Job ID (for example 3WyHPo6fWLetUI9iQlThF1), which Distributive needs to investigate and act. Reports are acknowledged within one business day.
• No monitoring. Distributive does not monitor Job content. It acts on reports and on knowledge it otherwise obtains.
• Actions. Distributive, or the administrator of the Compute Group concerned, may take any of the following, in proportion to the violation and without prior notice where the matter is serious: warn you; detach your Job from a Compute Group; suspend or terminate your account; freeze the Compute Credits in your account during an investigation; and, in an emergency affecting the platform, suspend Job dispatch for everyone.
• Detaching a Job from a Compute Group stops it receiving further work from that group. It does not cancel the Job, which remains yours.
• Forfeiture. If you attempt to defraud the network, violate the privacy of others, or otherwise breach this policy, Distributive may freeze your account and the Compute Credits in it, and you forfeit both. Compute Credits consumed by a Job that violated this policy are not refunded.

12. DCP Compute Credits

Compute Credits are a unit of account for computing services on DCP. They have no cash value. Nothing in this policy, the Portal, or your agreement gives you a right to demand cash redemption of Compute Credits; any cash redemption that may occur is at Distributive's sole discretion. Credits escrowed for a Job are released to Workers as work completes and returned to your account if the Job is cancelled.

13. Changes

Distributive may change this policy on 30 days' notice through the Portal and https://distributive.network/legal. Material changes require re-acceptance. The version you accepted governs until then.

14. Relationship to your agreement

If you deploy through Distributive directly, this policy is part of your account terms. If you deploy through a Licensee's platform, this policy applies through your agreement with that Licensee, which may add terms. Where a Licensee's terms conflict with this policy, this policy prevails on the matters it covers.

15. Contact

• Abuse and violations: abuse@distributive.network (include the Job ID)
• Privacy: privacy@distributive.network
• Security incidents: ops@distributive.network

Related documents

• All legal documents
• Privacy Policy
• DCP Worker Acceptable Use Policy and Operator Terms