Sallyport
MenuClose

Privacy

Last updated: 30 September 2026

This page says what we hold about you, what we hold on behalf of your agents, and what has no storage at all. It covers sallyport.cloud, the console and the API.

  1. 01

    Account data

    Your name, email address, organisation and the identifiers of the sessions you sign in with. Sessions are opaque random tokens looked up in our database, and they carry no personal data in themselves. We use this to run your account and to write to you about the service.

  2. 02

    Credentials

    Credential values are encrypted with a per-record key derived under a per-tenant key, and there is no route that reads a value back: not for you, not for our staff, not over the API. The only unwrap happens inside the engine for a call already on its way to an upstream. What is visible anywhere in the product is a credential's name, its version and where it is used.

  3. 03

    Call records

    Each call produces journal rows: the agent, the workspace, the binding, the class, the method, the host, the path, the decision, who took it and the result. A journal row carries no credential value, no request body and no full argument list. The canonical request a person is asked to approve is stored apart from the journal, encrypted under a key of its own, and is rendered back only into your own console.

  4. 04

    Bodies

    The part of an answer that does not fit in the agent's message is stored encrypted for 30 days, so the agent can read the rest, and is referenced from the journal. Bodies you choose to capture are stored the same way. Notifications never carry a body: a Telegram card or an email holds the target of a call and a link, never its content.

  5. 05

    Website analytics

    This site loads Google Analytics for aggregate traffic figures. The contact form is protected by Cloudflare Turnstile, which sees the interaction that proves you are a person. Neither one has access to your account or to anything inside the product.

  6. 06

    Where it lives

    The gateway, the console and the database that holds your account, your keys and your journal run in the United States, on AWS in us-east-1.

  7. 07

    How long we keep it

    You choose how long the journal is kept: 180 days unless you change it in Settings. Captured bodies are kept 30 days, and an hourly job deletes the rows and the objects whose time is up. Deleting a credential removes the stored value from the database and records the deletion in your journal.

  8. 08

    Sub-processors

    Infrastructure providers for hosting and object storage, an email provider for transactional mail, Telegram for approval cards you have linked, and the analytics and captcha services named above. The current list is available on request and changes are announced to account owners.

  9. 09

    Your rights

    Ask for a copy of your data, ask for corrections, or ask for deletion, and write to [email protected]. Your journal is exportable from the console at any time without asking anyone.

  10. 10

    Changes

    Changes appear on this page with a new date, and material changes are announced to account owners by email before they take effect.