Provider terms

Your own provider credentials (BYOK)

When you register your own provider credentials, your hardware use runs under your provider account and is governed by your own agreement with that provider, not by any agreement between Pauli and the provider. By registering credentials you make the representations in Terms of Service §8: you hold a valid direct agreement with the provider in your own name; that agreement and applicable law permit delegating access to third-party tooling, including credential storage or role assumption by Pauli; you bear all provider fees and provider-terms compliance, including any credential-sharing restrictions; you will revoke Pauli’s access at the provider when your use ends; and Pauli is not a party to your provider agreement.

How Pauli handles registered credentials (operational disclosures, not warranties): credentials are validated against the live provider before they are stored, stored encrypted, and never returned by any endpoint. For AWS, Pauli stores no keys at all: you create a cross-account IAM role that Pauli assumes with a Pauli-issued external ID. A job whose credential is unusable fails rather than falling back to Pauli’s own provider accounts. Providers bill you directly for hardware; Pauli charges only its platform fee.

Managed hardware (Pauli’s provider accounts)

No managed-hardware provider agreement is in effect yet. As each agreement executes, this section will list that provider’s acceptable-use, security, data-handling, and export terms that flow down to your use of the provider’s hardware through Pauli’s accounts.

Benchmark publication restrictions

Per Terms of Service §9, you may publish results of jobs you run except where a provider’s terms restrict benchmark publication. No such restriction has been identified for the results Pauli currently publishes (IonQ cloud simulator runs, labeled as simulator, not QPU hardware). Per-provider restrictions or consents will be listed here as they are identified or agreed.