Haunt

Haunt Privacy Policy

Effective October 13, 2026

Haunt is a place to write, made by Sleeping Potato, Inc. This policy says what happens to your writing and your data when you use it. It is short because there is not much to say: Haunt has no accounts, no servers of ours, no analytics, and no tracking.

Your writing stays with you

Everything you write in Haunt is stored on your device. Sleeping Potato never receives it, and there is no service of ours it passes through.

Haunt indexes your documents for Spotlight so you can search them from your device. That index lives on the device, like the writing. Exporting a document makes a file on your device. Where you send that file is up to you.

Where your writing can go, and only when you send it

Some of what Haunt does needs to send text somewhere: to a language model, to a site you publish to, to a folder on your Mac, or between your own devices. One rule covers all of them, now and as Haunt grows:

Nothing leaves your device until you connect a destination and act. It goes directly from your device to that destination, under that destination’s own terms. Sleeping Potato is never in the middle and never receives a copy.

Today that means:

  • Language model providers. You choose the provider. Text is sent only when you ask Haunt to do something that needs a model: the writing you add to a voice profile as a source, what you type in that voice profile’s chat, and, when you ask Haunt to read a document, that document.
  • Sites you publish to. When you connect a site and choose Send to Site, that document goes from your device to the site, under the site’s own terms. The site receives the document’s title, its text, and its tags and status where the site has them, and never any other document. Nothing is sent until you choose Send to Site.
  • A folder on your Mac. If you choose a folder for a space’s Local Copy, Haunt writes each document in that space to the folder as a Markdown file, and reads changes back from it. Haunt writes only to the folder you chose and reads only from it, and the files stay on your Mac.
  • Your own Apple devices. iCloud sync is on unless you turn it off, and Handoff works between your devices. Your writing moves between them through your Apple Account, in your private iCloud storage, under Apple’s privacy terms.

As Haunt adds ways to send your writing where you choose, the same rule applies, and this section names each one when it ships.

The providers you can connect today, and where your text goes:

  • Anthropic: api.anthropic.com
  • OpenAI: api.openai.com
  • Google: generativelanguage.googleapis.com
  • OpenRouter: openrouter.ai
  • Apple: Apple’s models run on your device, or in Apple’s Private Cloud Compute under Apple’s privacy terms.
  • A local server you run: Ollama, LM Studio or another model server at the address you enter. Your text goes to that address, on your own machine or your own network, and nowhere else.

The sites you can connect today, and where your writing goes:

  • Ghost: your site’s own address, with the staff access token or Admin API key you enter.
  • WordPress: your site’s own address, with an application password you make in WordPress. A WordPress.com site connects when you sign in to WordPress.com, and its text goes to public-api.wordpress.com.
  • Micro.blog: micro.blog, with an app token you make in Micro.blog.
  • Notion: api.notion.com, with an integration token you make in Notion. Each document you send becomes a page under the parent page you choose.
  • Google Docs: www.googleapis.com, after you sign in to Google. Haunt asks Google only for access to the files it creates and for your email address, which shows which account is connected. Each document you send becomes one Google Doc in your Drive, and Haunt can’t see any other file there.
  • A static site: api.github.com, with a token you make in GitHub. Each document you send becomes a Markdown file in the repository you choose, and your site’s host builds the site from there.

Haunt reads from a site when you choose Refresh from Site, which brings back the post for that document as a new version, or Import Posts, which brings the site’s posts into a new space on your device. While a site is connected, Haunt also asks it about the posts you sent there when you open a document or come back to Haunt, to show whether a post changed on the site or went live. Those requests read from the site and send none of your writing.

Each file in a Local Copy folder carries Haunt’s identifiers for the document, its version and your Mac in the file’s extended attributes, so Haunt can tell its own writes from your edits. Haunt keeps the folder’s location and your Mac’s name with the space, and they sync with your library, so your other devices can show which Mac keeps the copy. If the folder is inside iCloud Drive, Dropbox or another synced folder, that service carries the files under its own terms.

Sleeping Potato is not in the middle of any of it and does not see what you send or what comes back.

Your API keys, passwords and sign-in tokens are stored in your Keychain, protected by the system, and sync between your devices through iCloud Keychain under Apple’s terms, so a service you connect on one device is connected on all of them. Haunt uses a credential for exactly one thing: talking to the service it belongs to. If you disconnect a service, its credential is deleted from the Keychain on every device. The address of a local server, and Haunt’s permission to use a Local Copy folder, stay on the device where you set them.

Signing in through the web opens the service’s own sign-in page. Only WordPress.com returns you to Haunt through an address of ours: haunt.sleepingpotato.com/auth/wordpress, a static page that hands the sign-in to Haunt on your device and then clears it from the address bar. WordPress.com puts the sign-in in the part of the address your browser does not send to any server, so it never reaches Sleeping Potato. That page stores nothing, sets no cookies, loads nothing else, and keeps no logs of who arrives.

Haunt checks whether the links in a document still work, so it can mark the ones that don’t. To do that, your device makes a request to each linked address: a lightweight request that asks for headers, then a normal one if the site refuses. That means the sites you link to see a request from your device, the way they would if you visited. Haunt keeps the results on your device and sends them nowhere.

What Sleeping Potato receives

Nothing from the app itself unless you send it. Haunt contains no analytics, no advertising, no identifiers, and no crash reporting that runs on its own.

If you use Send Feedback, your mail app opens a message to us that shows everything in it, and nothing is sent until you send it. We receive only what you send, and use it only to answer you and fix the app.

If Haunt quits unexpectedly, the next time you open it, it shows you the crash report your device prepared, every line, and offers to open it in a message to us in your mail app. Nothing is sent unless you send it.

If you install Haunt through TestFlight or the App Store, Apple may share crash reports and basic usage statistics with us, according to the choice you make on your device under Settings ▸ Privacy & Security ▸ Analytics & Improvements. We use those only to fix the app.

This page, and the page about Haunt, live on Sleeping Potato’s blog at sleepingpotato.com, which counts page views the way its publishing platform, Ghost, does. That is the website, not the app: nothing you do in Haunt is connected to it.

Children

Haunt is not directed at children under 13, and we do not knowingly collect anything from them. That is easy to promise, since Haunt collects nothing from anyone.

Changes

If Haunt starts doing something this policy does not describe, the policy changes first, and the date at the top moves.

Contact

Sleeping Potato, Inc.

tom@sleepingpotato.com

Haunt is thoughtfully made by Sleeping Potato.