Shuttle API ("the App", "we", "us") is a developer tool for composing, sending, and inspecting network requests on Mac, iPhone, and iPad. This policy explains what information the App handles, where it is stored, and the choices you have.
We designed Shuttle API to be private by default: your collections, credentials, and responses live on your devices and in your iCloud account, and we do not run a server that receives them.
At a glance
- We do not operate a backend server that stores or processes your requests, responses, collections, or credentials. If you enable it, your data syncs through your own iCloud account.
- The App has no user accounts to create or maintain: there is nothing to sign in to.
- There are no analytics, no telemetry, and no crash-reporting SDKs. The App sends us nothing of its own accord: not on first launch, not when it crashes. The one exception is the update check, which runs only when you press it; see Checking for updates below. shuttle-run, our command-line runner, asks our site at most once a day whether a newer version is out; see the same section.
- We do not sell, rent, or share your data, and there is no advertising or tracking.
- The App's network traffic is the requests you compose and send, to the servers you address, plus iCloud sync if you turn it on, plus the Git repositories you link a collection to if you do, plus the secret manager you choose to keep your secrets in if you do, plus the AI provider you choose for the assistant when you write to it, or when you pause while writing a script if you turn on its code suggestions, plus the images and stylesheets an HTML response points to if you turn on loading them in its preview, plus the update check if you press it.
- You can erase everything the App stores from Settings → Data.
Who this policy covers
This policy applies to the Shuttle API apps for macOS, iOS, and iPadOS distributed through the Apple App Store and TestFlight, and to shuttle-run, the command-line runner downloaded from our site. shuttle-run runs your collections on your Mac as the App does, and what this policy says of the App's handling of them holds for it too.
Information the App handles
Everything the App holds is content you created or imported:
- Collections, folders, and requests: names, URLs, methods, query and path parameters, headers, request bodies, documentation, and tags.
- Environments and variables: the global, collection, environment, and folder values you define. Values you mark as secret are held in the device Keychain rather than in the App's data files.
- Credentials: bearer tokens, usernames and passwords, API keys, OAuth 1.0 and 2.0 client secrets and access tokens, AWS keys, Hawk and NTLM credentials, and any client certificate and private key you import. These are stored so the App can send them on your behalf.
- Scripts: the JavaScript you write to run before and after a request, and any helper module you save in a folder's settings.
- History: a snapshot of each request you send and the response it received, capped at the most recent 200 entries, so an entry stays replayable after the request is edited or deleted.
- Collection History: what each collection was each time you stopped editing it: its folders, their settings, its requests and its Collection variables, never a value marked secret, what is on the Auth tab, or a value a script wrote. Up to 100 entries per collection, plus any you name, kept only on this device: never synced through iCloud and never pushed to Git.
- Saved examples and run reports: responses you choose to keep on a request, and the results of a collection run.
- Saved API specs and mock servers: OpenAPI documents and mock server settings you save in a collection, with their versions: the latest 25 of each, and every one you name. They go where their collection goes: to your other devices if iCloud sync is on, into backups and collection files you export, and to its Git repository if you keep it in one.
- Cookies: cookies returned by the servers you address, or imported from a file you choose, kept per collection in the App's own jar.
- Settings: your theme, language, layout, shortcut bindings, proxy configuration, timeouts, and TLS options.
- Git settings (only if you use Git): the repositories you add (their address, branch, and user name), the access token for each, the name and email your commits are signed with, which collection is kept in which repository, and in which folder of it if not the whole, and the commit each last synced at; and, for a collection you keep in Git by hand, the commits waiting to be pushed and the changes you set aside, never with a secret value in them. What each sync reached, the commits waiting and the changes set aside stay on the device even if you share Git settings between your devices.
- Vault settings (only if you keep secrets in a vault): which secret manager you chose (HashiCorp Vault, AWS Secrets Manager, Azure Key Vault or Google Cloud Secret Manager), its address, region, vault, or project, the account or app registration it signs in as, and the credential for it; and, on each secret variable, where its value is in that vault.
- Assistant settings (only if you use the assistant): the AI provider you chose (Anthropic, OpenAI, Ollama, LM Studio, or a server you give the address of), its API key if it needs one, the model, which MCP requests the assistant may use, what it sends beyond secret values, how much the model thinks, for Claude and for OpenAI's models, and whether it suggests code in the script editors, with which model.
- Assistant conversations (only if you use the assistant): what you and the assistant said, and what it read and did to answer, with secret values only as the ••• it saw: the latest 50 conversations, so you can go back to one.
The App does not collect or receive your name, email address, contacts, photos, location, browsing history, health data, or advertising identifiers. It does not read files you have not explicitly chosen in a file picker.
Where your data is stored
- On your device. Collections, requests, environments, history, settings, and cookies are written as inspectable JSON files in the App's own Application Support directory. Nothing there leaves the device unless you enable iCloud or export a file yourself.
- In the device Keychain. Every value you mark as secret, every stored credential, every Git access token, the credential for a vault, and the assistant's API keys, are held in the Keychain rather than in those JSON files, protected by the system. The Keychain items stay on the device they were made on: they are never synced through iCloud. Vault and assistant settings, and the assistant's conversations, stay on their device too, unless you choose to share them between your devices; see In your private iCloud container below.
- In memory only, for secrets read from a vault (optional). A value read from your vault is held in memory while the App runs, to send the requests that use it, and is gone when it quits. It is never written to a file, synced, exported, or pushed to Git.
- On the device, for the assistant's conversations (optional). The latest 50 conversations are kept in the App's Application Support directory, so you can go back to one. They are never exported or pushed to Git, and are synced through iCloud only if you tick Assistant conversations under Share between your devices. You can delete one or all of them in the assistant, and Erase data deletes them (while they are shared, on every device sharing them). A device that stops sharing them leaves the copy in iCloud to the devices still sharing it; your iCloud storage settings can delete it.
- A local copy of each Git repository (optional). If you keep collections in Git, the App keeps on that device the part of each repository its syncs need, beside its own files. These copies and the tokens stay on the device they were made on: they are never synced through iCloud. Git settings do too, unless you tick Git under Share between your devices.
- In your private iCloud container (optional). If you enable iCloud sync, your collections, environments, and history are stored in the App's private iCloud container under your Apple ID, and so is each of the settings a device otherwise keeps for itself (Git, Secrets, Assistant, Assistant conversations) that you tick under Share between your devices, in Settings › Data, never with the tokens, keys, or credentials the Keychain holds. Only your Apple ID, and devices signed into the same Apple ID, can access this data. We have no access to it.
We hold none of it. There is no Shuttle-operated database, log, backup, or cache of your content anywhere.
The requests you send
This is the one part of the App that necessarily involves other parties, and it is worth being precise about.
When you send a request, the App connects to the host you addressed and transmits exactly what you composed: the URL, headers, body, cookies, and any authentication values you configured. That data goes to that server's operator, not to us. Which servers you address, what you send them, and what they do with it are governed by your relationship with them, not by this policy.
A few consequences worth knowing:
- Credentials leave the device when you send. That is the point of an API client, but it means a token entered here is transmitted to whatever host you point the request at. Check the URL before sending a request that carries a credential.
- Turning off TLS verification removes a protection. The App lets you disable certificate verification or trust a custom certificate authority for a specific host. Doing so means the connection can no longer be trusted to reach the party it claims to. The App will not override your choice, and this policy cannot protect data on a connection you chose to weaken.
- A proxy sees your traffic. If you configure a proxy, requests pass through it, and its operator can see them.
- Loading remote images in an HTML preview tells their hosts. The preview of an HTML response shows only what arrived in it, unless you turn on Settings › Requests › Load remote images and styles. Then it fetches the images, stylesheets and fonts the page points to, from whichever hosts the page names, which need not be the one you addressed, and those hosts learn that the response was opened, and from what address. They are fetched without cookies, through the App's proxy when you set one by hand and your device's own network settings otherwise, and scripts in the page still never run.
- Scripts run with full access. Pre-request and post-response scripts, including any module you
requireand any code you paste from elsewhere, can read and modify your variables and environments, including secret ones, and can change the request before it is sent. Review anything you paste. - The mock server listens locally. When you start it, the App accepts connections on the port you chose. On a shared or untrusted network, other machines may be able to reach it. It serves only the OpenAPI document you loaded, and stops when you stop it.
Collections kept in Git (optional)
If you link a collection to a Git repository, or to a folder in one, the App syncs it with the host that repository is on (GitHub, GitLab, or a server you run) using the access token you gave it, when you sync and, if you leave it on, on its own while the App is open. That host receives what is pushed, not us, and its own terms and privacy policy apply to it.
- What is pushed. The collection as files: its folders and their settings, every request (name, URL, method, parameters, headers, body, scripts, documentation, tags, saved examples), its Collection variables, its environments, and its saved API specs and mock servers: each spec as you wrote it, and each version you named. Of a file a request sends, only its name is pushed, not where it is on your device.
- What is never pushed. Credentials on the Auth tab, values you mark as secret, values scripts wrote, schemas and lists fetched from a server, and whether you approved a folder's scripts. A credential written as nothing but a
{{variable}}is pushed as that variable, since it names where a secret is rather than holding it. - The rest of the repository is left as it is. Whether the collection takes the whole repository or a folder of it, the App writes only the collection's own files (
collection.yamlorcollection.json, a directory for each of its folders, its environments, and its saved specs and mocks) and never changes your code or other tools' files beside them. - What you type is pushed as typed. A token typed into a header or a body, rather than into the Auth tab or a secret variable, goes into the repository as it is. Mark the row secret, or keep the value in a secret variable, to keep it out.
- Who can read it. Everyone with access to that repository, and anyone it is later shared with. Each commit carries the name and email you set in Settings › Git.
- History keeps it. A Git repository keeps every commit. Something pushed and later removed stays in the repository's history until that history is rewritten on the host.
- The token goes only to that host. Over HTTPS (plain HTTP is accepted only for a server on your own device), and never to another server a redirect points to.
Secrets kept in a vault (optional)
By default, the values of your secret variables are kept in the device Keychain. If you choose in Settings › Secrets to read them from a secret manager instead (HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, or Google Cloud Secret Manager), the App contacts that service, and only that service and its provider's sign-in service, when a request, a run, or an OAuth token fetch uses one of those secrets, and when you press Test connection. That service is run by you or your organization, or by its provider, not by us, and its own terms and privacy policy apply to it.
- What is sent to it. The credential you gave it, to sign in, and the names of the secrets the App needs, nothing else: not your requests, not your collections.
- What comes back. The values of those secrets, held in memory only, as described above, and sent only to the servers your requests address.
- What travels with your collection. Where a secret is in the vault (its name or path) goes where the variable goes, into an export or a repository, because it names the secret without holding it. The value never does.
- Over HTTPS. Plain HTTP is accepted only for a vault on your own device.
The assistant (optional)
If you set up the assistant in Settings › Assistant and write to it, the App sends what you write to the AI provider you chose (Anthropic, OpenAI, Ollama, LM Studio, or a server you gave the address of, which may be on your own device), using your key and your account with that provider where it needs one. Ollama and LM Studio run a model on a computer of yours: with it on this device, what you write stays on this device; with it on another computer of your local network, reached over plain HTTP, it crosses that network unencrypted. To answer, the assistant reads parts of your collections, and those go to the provider too. That provider, not us, receives it, and its own terms and privacy policy apply, including whether it keeps what it receives and for how long.
- What is sent. Your messages, and what the assistant reads to answer them: the names of your collections, folders and requests; a request's URL, parameters, headers, body, scripts and documentation; a response it was sent or read; and variables that are not marked secret.
- What is never sent. Values you mark as secret, headers marked secret, and the credentials on an Auth tab: the model sees them as •••. Your API key goes only to the provider, as its own sign-in.
- Not stored at OpenAI, by request. The App asks OpenAI not to store your conversations: each request to it is sent with storing turned off. What OpenAI still keeps, for abuse monitoring for instance, is under its own terms.
- Code suggestions, if you turn them on. With Suggest code as you type on, in Settings › Assistant, each pause while you write a script sends the script around the caret to the same provider, with which script it is, the request's name, method and URL, held back as What it sends says, and for a script run after the response, that response's status and its body's shape: each value's type, never the value. They are off until you turn them on.
- What you can hold back. Under What it sends, in Settings › Assistant, credentials nobody marked secret are shown to the model as ••• too: in headers and URLs, in the fields of what a request sends and a response returns, and in variables named like one. These are on until you turn them off. Names you add there are hidden whatever the switches say, and responses can be sent as their shape alone, each value replaced by its type.
- What it does. It makes and changes requests, folders and variables, sends requests and runs folders, on this device, through the App, as you could. By default each such step waits for you to allow it, and every change is in the collection's history to undo. A request it sends goes where that request is addressed, as when you send it.
- MCP servers. If you let it use an MCP request's server, the tools it calls on that server receive what it sends them, as when you call them yourself.
- Kept on your devices only. The latest 50 conversations are kept on the device they were had on, and reach your other devices, through your own iCloud, only if you tick Assistant conversations under Share between your devices. You can delete one or all of them; Erase data deletes them too, and while they are shared, on every device sharing them. Nothing of them reaches us.
How your data is used
Your information is used only to make the App work: to build and send the requests you compose, to display the responses, to substitute your variables, to authenticate as you have configured, to run your scripts and folder runs, to sync between your own devices if you enable iCloud, to sync with the Git repositories you link collections to, if you do, to read your secrets from the vault you chose, if you do, and to answer you through the AI provider you chose, if you use the assistant.
We do not use your data for analytics, profiling, advertising, machine-learning training, or any purpose unrelated to the App's core function. We cannot, because we never receive it.
Checking for updates
Settings has a Check for update button. Nothing checks on its own: not at launch, not in the background, not on a schedule. No check happens unless you press it. The App from the App Store is updated by the App Store: there, the check only tells you whether a newer version is out and shows its notes.
When you do, the App sends one request to our site carrying three things: which app it is, the version you are running, and your language, so the release notes can come back in it. It carries nothing about you, nothing from your collections, and no identifier of any kind: there is no account, and the App has none to send. What comes back is a version number and its notes.
We keep nothing from these requests. Our site is hosted by Vercel, and as with any web host their infrastructure necessarily handles the connection itself (the address it came from, and the time) under Vercel's own privacy policy. We do not use that for anything, and we build no record of who checked, or when.
If you would rather send nothing at all, do not press the button. Everything else in the App works the same either way.
shuttle-run, the command-line runner, has no store to keep it up to date, so it checks on its own, within limits. Run in a terminal, at most once a day, it sends our site the same request as Check for update above, carrying which app it is, the version you are running, and English, the only language it speaks; when a newer version is out, it says so under its results. The request carries nothing about you or your collections, and no identifier, and what comes back is a version number and its notes. Our host sees it as described above, and we keep nothing from it. It never checks in CI, when its standard error goes to a file or another program rather than a terminal, with --quiet, or when SHUTTLE_RUN_NO_UPDATE_CHECK is set. The time of its last check is kept on your Mac, in ~/Library/Caches/shuttle-run/update-check, and nowhere else.
Third-party services
The App integrates no third-party SDKs at all: no analytics, no advertising, no crash reporting, no feature flags, no A/B testing. Its platform dependencies are Apple iCloud, and only if you enable sync, and the host of our own site for the update check described above; your use of it is also governed by Apple's privacy policy: apple.com/legal/privacy.
Any diagnostics you may choose to share with Apple are governed by your device's analytics settings and Apple's privacy policy. If you send us a crash report or a wire transcript yourself, by email, we receive whatever you chose to include: the App strips secrets from exports and masks credentials in transcripts by default, but you should still read what you are sending.
The Git hosts you link collections to (GitHub, GitLab, or a server of your own) are, like the servers you send requests to, services you choose: the App integrates none of them, and contacts one only for a repository you added, with the token you gave it. Your use of each is governed by its own terms and privacy policy.
The same goes for the secret manager you may choose in Settings › Secrets (HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, or Google Cloud Secret Manager): the App integrates no SDK for any of them, and contacts the one you chose only to sign in, read the secrets your requests use, and test the connection when you ask, with the credential you gave it.
The AI provider you may choose for the assistant (Anthropic, OpenAI, Ollama, LM Studio, or a server of your own) is a service you choose too: the App integrates no SDK for it, and contacts it only when you write to the assistant, test the connection, or pause while writing a script with code suggestions on, with your key where it needs one. Your use of it is governed by its own terms and privacy policy.
The App reads and writes file formats defined by other projects (Postman, Insomnia, Bruno, Thunder Client, HAR, OpenAPI). Those are file formats, not services: importing one reads a file you selected, and contacts nobody.
Permissions the App may request
You are always in control. The App may ask for the following, and you can change or revoke each in System Settings (Mac) or Settings (iPhone/iPad):
- Network access (all): to send the requests you compose. This is the App's core function.
- Local network (iPhone/iPad): only if you address a host on your local network, or run the mock server.
- Files you select (all, optional): to open a
.protofile, a certificate, a data file for a collection run, or a collection to import, and to save an export. The App receives access to the file you picked and nothing else. - iCloud (all, optional): to sync your collections between your own devices.
The App never requests camera, microphone, location, contacts, calendar, photo library, or notification access, because it has no feature that needs any of them.
Data retention and deletion
- Everything the App stores stays until you delete it. There is no expiry and no server-side copy to outlive it.
- History is capped at the most recent 200 sends; older entries are dropped automatically as new ones arrive.
- Deleting a collection or an environment removes it and its secrets from the Keychain. A deleted request or folder goes to the App's Trash first, its secrets with it, where the 25 most recent deletions wait to be put back; emptying the Trash, or an entry falling off the end of it, removes them and their secrets for good. If you turn the Trash off in Settings, a deleted request or folder is removed with its secrets at once, and what the Trash held is removed when you turn it off. A deleted request or folder also stays, without its secrets, in the earlier entries of its collection's Collection History, until those entries are pruned, the collection is deleted, or the data is erased.
- Settings → Data → Erase removes everything the App stores on that device in one action.
- If you enabled iCloud, deleting the data also removes it from your iCloud container. You can also manage the App's data in your iCloud storage settings.
- Unlinking a collection, or removing a repository in Settings › Git, leaves the repository as it is. Settings → Data → Erase also removes the Git settings, their tokens, and the local copies of repositories. What was pushed stays in the repository, under its host's control and yours.
- Settings → Data → Erase also removes the vault settings and their credential. Values read from a vault are gone when the App quits; what the vault holds stays there, under its owner's control.
- Settings → Data → Erase also removes the assistant's settings, its API keys and its kept conversations. What a provider kept of them is under that provider's terms.
- Uninstalling the App removes its local files and Keychain entries from that device.
Security
- Secrets and credentials are stored in the system Keychain, not in the App's data files, and are protected by the device's own protections.
- Exports strip secret values by default, and wire transcripts mask
Authorization,Cookie, and similar headers until you explicitly ask to see them. - Requests use TLS wherever the URL you entered does, with certificate verification on by default.
- Data in transit to iCloud is protected by Apple's encrypted services.
- Git access tokens are stored in the Keychain and sent only to the repository's host, over HTTPS.
- A vault's credential is stored in the Keychain and sent only to that vault, or to its provider's sign-in service, over HTTPS; what is read from it is held in memory only.
- The assistant's API keys are stored in the Keychain and sent only to the provider they belong to, over HTTPS unless the provider is on your own device.
- No Shuttle-operated server ever stores or processes your content.
While no method of transmission or storage is 100% secure, we rely on Apple's platform protections to safeguard what is on your device, and we minimize risk by never receiving your data in the first place.
Children's privacy
Shuttle API is a developer tool, is not directed to children under 13 (or the equivalent minimum age in your country), and we do not knowingly collect personal information from children.
Your rights
Because we hold none of your data, there is nothing for us to disclose, correct, or delete on your behalf. You can access, export, or delete everything directly in the App, or through your iCloud storage settings. Depending on where you live, you may have additional rights (such as access, correction, portability, or deletion) under laws like the GDPR or CCPA; since we operate no server and hold no personal data, those requests are satisfied by the App's own export and erase functions. For anything else, contact us using the details below.
Changes to this policy
We may update this policy from time to time. When we do, we will revise the "Last updated" date shown on this page, and significant changes may also be noted in the App or its release notes. If required by applicable law, we will provide additional notice or request your consent before changes take effect.
Contact
If you have questions about this policy or how Shuttle API handles your data:
Email: cliffrubio.dev@gmail.com