Sallyport
MenuClose

Terms of Service

Last updated: 9 October 2026

These terms cover Sallyport Cloud, a service that executes outbound calls on behalf of software agents you control, using credentials you store with us. Using the service means accepting them.

  1. 01

    What the service does

    You store credentials in a per-tenant vault. Your agents name actions. We classify each action, apply the policy you configured, request a human decision where your policy calls for one, record the intent, place the credential on the outbound request, execute it, and return the result. We do not return credential values to agents, to you, or to anyone else, and no route exists that does.

  2. 02

    Your account and your agents

    You are responsible for the credentials you store, for the agent identities you create, for the tokens those identities hold, and for the policies you set on them. Rotate an agent token when a machine that held it is out of your control. An approval given by a person on your account is treated as authorised by you.

  3. 03

    Acceptable use

    Use the service against systems you own or are authorised to access. Do not use it to reach third-party systems without permission, to circumvent another party's access controls, to send unlawful traffic, or to attack anyone. We may suspend an agent, a workspace or an account that does, and we will tell you why.

  4. 04

    The credentials you store

    Credentials remain yours. You may revoke them at the provider at any time. Each stored value is encrypted per record under a key derived for your tenant alone. Deleting a credential removes the stored value and writes the deletion to your journal. No route on this service returns a credential value to anyone, including to you, to our staff and over the API; the only path that opens one is the dispatch of a call that has already been authorised.

  5. 05

    The journal

    Every call produces records in a hash-chained journal for your tenant. Each record carries the hash of the record before it and an Ed25519 signature, and sequence numbers are issued from a counter row rather than a database sequence, so a removed record leaves a gap that verification reports. Records are stored as readable canonical JSON, which means the service can read what it wrote; the integrity claim is the chain and the signature, not confidentiality from us. The database role this service runs as holds INSERT and SELECT on the journal table and neither UPDATE nor DELETE. You may export any segment. Each record in the export carries its Ed25519 signature, the hash of the record before it and the identifier of the key that signed it, and those public keys are published. We retain journal data for the period configured on your plan.

  6. 06

    Availability and limits

    The service targets 99.9% monthly availability for the MCP endpoint. Plan limits, rate limits and concurrency limits are published on the pricing page with the reason for each. Exceeding a plan’s monthly calls does not block calls; the console shows a notice. Creating an agent beyond the plan’s agent count requires a bigger plan.

  7. 07

    Fees

    Prices are published on the pricing page in US dollars. Each self-serve plan starts with a 7-day free trial, one per organization; the card you add is charged when the trial ends unless you cancel before then. A plan is then charged in advance for each month or year, as you choose. A move to a bigger plan takes effect at once and is charged pro rata; a move to a smaller plan takes effect at the end of the billing period. Without a plan in force, calls stop until an owner picks one, and nothing is deleted. People on your team are free on every plan. We will give notice before a price change takes effect for an existing account.

  8. 08

    Liability

    The service is provided as it is. To the extent the law allows, our liability for any claim is limited to the fees you paid us in the three months before the claim arose. Nothing here limits liability that cannot be limited by law.

  9. 09

    Ending the agreement

    You may close your account at any time and export your journal before you do. We may end the agreement for non-payment or for a breach of acceptable use, with notice and with time to export.

  10. 10

    Changes and contact

    We will post changes to these terms on this page with a new date, and material changes are announced to account owners by email before they take effect. Questions go to [email protected].