Privacy policy

Effective 16 November 2026.

Who this is from

Hikki is made by Yancey Leo. This policy covers the Hikki app for iPhone, iPad and Mac, and the website at hikki.yancey.app. It is written from what the app actually does; when the app changes in a way that matters here, the date above changes too.

What Hikki stores, and where

Your private workspace stays on your devices and in your own iCloud account if you sync with it. Sharing sends only the snapshot you choose, as described below. You do not need to create a separate Hikki account.

  • Your pages are files in the app’s own storage on the device: one file per page, with its history, comments, attachments and AI conversations beside it. With iCloud on (the default when you set Hikki up), they are also kept in your iCloud account’s private database, as described below. Export writes everything out as Markdown, HTML, PDF or the original page files (JSON) whenever you want a copy.
  • A search index and a cache of the same pages live in the app’s own storage on the device, so search is fast; both are rebuilt from your files whenever needed.
  • Spotlight. By default, page titles and text are also given to the device’s own Spotlight index, so system search finds them. This stays on the device. Settings → Search turns it off and empties it.
  • Reminders on dates in your pages are local notifications, scheduled on the device.
  • Your AI keys are kept in iCloud Keychain. Settings are kept in the app’s preferences, and a copy in iCloud key-value storage (see iCloud below).

What leaves the device, and when

These connections happen when you use the optional features below. Community review and notifications make the limited data described here available to the administrator.

  • iCloud. With iCloud on, your workspace syncs between your devices through CloudKit, in the private database of your own iCloud account, on Apple’s servers and in your iCloud storage. Each file’s path, and the contents of a page up to 512 KB, are stored in encrypted fields, which are end-to-end encrypted: only your devices can read them, not Hikki’s maker and not Apple. Attachments, and a page larger than that, go as CloudKit assets, encrypted by Apple, and end-to-end encrypted when you turn on Advanced Data Protection. Apple’s terms govern iCloud. If you set Hikki up for this device only, or turn iCloud off in Settings → Storage, your workspace doesn’t sync. Settings and AI keys sync either way: keys through iCloud Keychain, end-to-end encrypted; the other settings (theme, shortcuts, the AI model — never a key or anything you wrote) through iCloud key-value storage, encrypted by Apple but not end-to-end.
  • AI, only when you ask: Ask AI on a selection, the chat beside a page, making pictures or a diagram. The request goes from your device straight to the provider you chose, OpenAI or Anthropic (or the address you set for it), with your own key. It carries what the task needs: the selected text and the words around it, or for the chat the open page’s text (long pages are cut), any pages you add with @, any picture or PDF you attach, and your question. The provider may search the web for an answer; in the chat a switch turns that off. The provider’s privacy policy governs what it does with the request. A key is sent only to the address it was entered for. If you turn on file use in Settings → AI, the chat may also list, read and search the files in your workspace folder (kept in the app’s storage on the device) when your question calls for it; what it reads goes to the provider with the question. It writes or changes a file only after you allow that change. File use is off until you turn it on.
  • AI tools on your Mac, only when you turn on the hikki command in Settings → Integrations. Programs on the same Mac, such as Claude Code or Cursor through MCP, can then list, search and read your pages, never change them, and only after you allow it. An Allow is for that one running program: once it quits (in a terminal, once you close that window or tab) or Hikki does, it asks again, and nothing you allowed is kept. The command talks to Hikki through a private socket on the Mac, for your own user; nothing listens on the network. What such a program reads is then its own: it may send it to its model or anywhere else it goes, under its own policy. Settings → Integrations lists the programs allowed now, removes them or turns the command off.
  • Unsplash, when you search it for a cover: your search words go to Hikki’s small server, which forwards them to Unsplash with Hikki’s key and sends the results back; the photos load from Unsplash. That server logs each request’s method, path, status, duration and an id, not the search words. Choosing a photo is reported to Unsplash as a download, as its guidelines ask.
  • Sharing a page, only when you choose Share on it. A copy of the page as it is then (its words, pictures and attachments, its icon and cover, the tags you pick and the name you give as its author, if any) goes into Hikki’s iCloud container. Shared with anyone with the link, the copy is encrypted on your device first with a key that exists only in the link, so nobody without the link can read it, Apple and Hikki’s maker included. Anyone who receives the complete link can read and forward it; it does not verify a named recipient. These pages are available without waiting for approval and are not listed in Community. Submitted to Hikki Community, a snapshot is stored without end-to-end encryption in a record readable only by its creator and the administrator’s server role. The administrator manually reviews it; only approval creates a publicly readable page and listing. No content is sent to an AI moderation service. Updates follow the same review process, with the old approved version remaining public until the replacement is approved. CloudKit records associate a submission with its creator’s opaque account identifier. Your Apple Account email is never displayed on the shared page. New snapshots include the sharing terms version and the time you confirmed them. Comments, history and AI chats never go along. Stop Sharing removes the hosted copy, but cannot recall copies already saved by readers. Saving a shared page into Hikki adds a copy to your own workspace.
  • Reporting a shared page. A report sends the page’s identifier and sharing mode, your chosen reason and the explanation you enter. The server records the current hosted version, submission time and the administrator’s handling outcome. Reports are accessible only through the protected administrator service, not published to readers or the page’s author. No Hikki sign-in is required. The form does not automatically upload the page’s text, attachments or decryption key; link-only pages remain encrypted and are not proactively inspected. Avoid including private information or a complete sharing link in the explanation. Reports and handling records are kept to investigate concerns and document action taken. Content concerns can also be sent to abuse@yancey.app. Contact us below with privacy or deletion requests. The service uses temporary per-address request limits to reduce spam.
  • Community notifications are optional on iPhone and iPad. When you enable them, the app registers an Apple push token, its platform and push environment, an installation identifier and proof, your opaque iCloud account identifier, the enabled state and update time. These are used to deliver review results through Apple’s Push Notification service, not for advertising or analytics. Notifications can include the page title, decision and rejection reason, which may appear on the lock screen under your system settings. Turning the switch off disables that installation’s Community notifications. Delivery records and pending notifications are kept so failed deliveries can be retried. Administrator review alerts require a separate, time-limited connection initiated from the authenticated CMS; the binding stores the reviewer’s label, opaque iCloud identifier, linking administrator and connection time. The CMS can disable or remove that binding. Community push registration is not used on Mac.
  • Links and embeds. Pasting a web link makes the device fetch that page once to show its title and description (public addresses only). An embedded page or video loads from its own service when you view the page that holds it; a YouTube video loads through a page on Hikki’s server, so the player works, and that server then sees the video’s id. Adding a picture from a web search fetches it from where it is. Browsing Excalidraw’s libraries opens excalidraw.com in your browser.

Buying Hikki happens through the App Store: Apple takes the payment and tells the app only the purchase information needed to unlock it; Hikki does not receive your payment details or billing email.

That is the whole list. No analytics, no advertising, no crash reports sent to anyone.

Crashes and diagnostics

If Hikki crashes, the system hands it a crash report, which it keeps on the device. Hikki’s own log never contains page content, only ids and counts. Settings → About → Diagnostics lets you export the logs and reports yourself, to send along with a report if you choose to; nothing goes anywhere on its own.

The website

Community pages record daily deduplicated views, likes, and Save to Hikki clicks to display activity and rank shared pages. A signed, HTTP-only reader cookie lasts up to one year and remembers your likes without an account. Views use a daily keyed hash of the network address and browser user agent; raw addresses are not stored in the activity database. Save counts measure clicks, not confirmed imports into the app. Activity is stored in the Hikki CloudKit public database with server-only record permissions. Counts and pseudonymous interaction records are retained to maintain totals; cancelling a like removes it from the public count. Clearing the cookie resets this browser’s like identity. Private link-only pages do not participate in these counts. Your light or dark choice is kept in your browser’s own storage. The site is served by Cloudflare, which keeps ordinary request logs for a short time, as any host does. Public Community pages are read from iCloud by the website’s server. A link-only page is read and decrypted in your browser; its key stays in the URL fragment and is not sent in requests to our server. Sharing the complete URL with another person also shares that key.

Questions

Write to developer@yanceyleo.com. Your message is kept only as long as the conversation needs. Shared content, review records and optional notification data are handled as described above.