Scope
This policy is part of the Terms of Service and applies to every member of every organization that uses Fleet by Oracis, and to every job, validation and publication they submit. Draft pending counsel review.
You may not
- Submit a repository you do not control, or one you are not permitted to have processed by the parties on the subprocessors page.
- Include protected health information, payment card data, government identifiers, or credentials of any kind in a repository, a task description or a support message during the pilot. Fleet is not offered for regulated data yet.
- Attempt to escape the execution jail, reach another organization's data, exhaust another tenant's capacity, or probe the service for weaknesses other than through the vulnerability reporting route.
- Run malware, credential harvesting, cryptomining, denial-of-service tooling or anything designed to harm a third party as a job or a validation.
- Use Fleet to produce or verify software whose purpose is unlawful, or that infringes someone else's rights.
- Resell access, share an account, or connect a client on behalf of a person who has not accepted these terms.
- Present a Fleet receipt as more than it is: a receipt identifies the exact source, the approved policy and what an independent runner observed. It is not a certification and not a warranty.
What happens
A breach can lead to the suspension or revocation of the identity involved, which ends its sessions and cancels its running jobs, and to the organization's access being ended under the Terms. Where the law requires it, we may also have to report an incident.
Reporting misuse
To report misuse of Fleet, use support. Security issues go through the security report route.