OutPost Privacy Policy
Last updated: 7 September 2026
OutPost is an app for publishing to your own website. It has no account system, no server, and no analytics. I do not collect, receive, store, or transmit any information about you or what you write.
That is the whole policy. The rest of this page explains what the app actually does, so you can check the claim rather than take it on trust.
What OutPost keeps on your device
Everything OutPost stores stays on the device you are using. None of it syncs to iCloud, and none of it reaches me.
- Your access tokens, in the system Keychain. These are what let OutPost publish to your site on your behalf. They are never written to a file, never logged, and never sent anywhere except back to the site that issued them.
- Your accounts, in a local database: the address of your site, the endpoints your site advertises for publishing and authorisation, and the display name and profile picture your site publishes about you, if it publishes any.
- A record of posts you have published from OutPost: the address, title, a short excerpt, and when you posted it. This is a local convenience so the app can show you what you have written. Your site remains the real home of your posts, and deleting OutPost’s copy does not delete the post.
- One preference: which of your accounts is currently selected.
What leaves your device, and where it goes
OutPost talks to exactly one place: the website you signed in to. Every request it makes is to your own site or to the endpoints your site advertises.
That covers finding out what your site supports, signing you in, publishing and editing posts, uploading images you attach, and fetching the icon your site publishes for itself.
Your posts, drafts, and images go to your site and nowhere else. They do not pass through any service of mine on the way, because there isn’t one.
Signing in
OutPost signs you in with IndieAuth, which means you authenticate with your own website, not with me and not with any third-party login provider. The sign-in screen that appears is your own site’s, shown in a system browser view. OutPost never sees your password.
One honest detail. So your site can show you what you are authorising, the
IndieAuth standard has your site fetch the app’s identification page at
https://jimmitchell.org/apps/outpost/. That request is made by your website’s
server, not by you and not by the app, and it contains nothing about you beyond
the fact that some server asked for a public page. My web host records it in its
ordinary access logs, the same as any other visit to that page.
Photos and files
When you attach an image, iOS shows you the system photo picker. OutPost receives only the specific images you choose — it has no access to your photo library, which is why it never asks for permission to one. Images you attach are uploaded to your own site’s media endpoint when you publish.
What I collect
Nothing. There is no OutPost account, no OutPost server, no analytics, no crash reporting service, no advertising, and no tracking of any kind. OutPost contains no third-party SDKs. The only outside code in it parses Markdown and does no networking at all.
TestFlight builds
If you are testing OutPost through TestFlight, Apple provides me with crash logs and basic usage figures for the beta, such as how many testers installed it. That collection is Apple’s, not the app’s, and it is governed by Apple’s privacy policy. It tells me nothing about what you write or where you publish it.
Deleting your data
- Remove an account in OutPost and the app asks your site to revoke the access token — if your site offers a revocation endpoint — then deletes the token from the Keychain and removes that account’s local records.
- Delete the app and everything described on this page goes with it.
Neither affects anything you have already published. Those posts live on your own site, and only you can remove them from there.
Children
OutPost is not directed at children and collects no information from anyone, including children.
Changes
If this policy changes, the date at the top changes with it. Material changes will be described in the app’s release notes rather than made quietly.
Contact
Questions about this policy, or about anything above that doesn’t match what you observe: hello@jimmitchell.org