The developer collects no user data whatsoever. Kakesu has no developer-run server. There are no ads, no analytics tools, and no third-party SDKs in it.
The URLs you save, along with titles, tags, notes, unread and favorite state, and app settings. So that search can dig them back out, it also stores the start of the saved page's text (up to 4,000 characters). These are held on your device and in your own iCloud (a CloudKit private database).
By Apple's design, the developer cannot reach that private database. The developer cannot read its contents, extract them, or pass them to anyone else.
Kakesu makes a network connection only in these cases.
Opening a page inside the app uses Apple's SFSafariViewController. It opens in Reader by default, which happens within that same mechanism. Cookies and browsing history are kept separate from Safari, and the developer cannot obtain the contents.
Once a week, everything you have saved is written as a JSON file into your iCloud Drive (the Kakesu folder in the Files app). It is a copy placed somewhere you can read it; it is not sent to the developer.
None. No ads are shown. There are no in-app purchases. No analytics tool measuring usage is included. You will never be asked for App Tracking Transparency permission.
On supported devices you can put questions to the app about the bookmarks you have collected. This feature runs solely on the on-device model in iOS (Apple Intelligence). Neither questions nor answers are sent to a developer server or to any external server.
What is handed to the model, after narrowing to at most six items closest to the question, is five things: title, tags, note, the site's host name, and whether it is unread. Alongside that go aggregate figures such as counts, your most-used tags, and the sites you save from most. Full URLs are never handed over.
When you ask a follow-up, the exchange so far (questions and answers) goes to the same model too. This keeps the thread of the conversation; only the last few pairs are passed. This too never leaves the device. Questions about your collection as a whole are not stored on the device either. Tap “New conversation”, or close the screen, and they are gone.
For the summary of a single article, that page's text (the beginning only) is handed to the on-device model. The only thing it rests on is that one article's text; nothing else you saved is mixed in. Here too, the text never leaves the device.
Conversations about a single article are the one thing kept on your device — the five most recent. This is so you can pick up where you left off when you open the same article again. They are not sent to iCloud, nor to the developer, nor to any external server. Delete them from “Article Conversations”, reached from the Ask screen, one at a time or all at once with “Delete All”. From the summary screen you can delete just that article's conversation. Deleting the app removes them with it.
The feature is available only on devices that support Apple Intelligence, with it enabled in iOS Settings. On other devices the entry point does not appear at all.
With App Lock enabled, opening the app verifies you with Face ID / Touch ID, or your device passcode.
Face and fingerprint data are handled by iOS, on the device. This app does not obtain them. They are never sent to the developer. All this app receives is whether the check passed.
While App Lock is enabled, the Home Screen widget shows no titles and no site names either (only the unread count). The Home Screen is on show without a lock in front of it.
Only if you have enabled “Share with App Developers” in iOS Settings may Apple provide anonymous crash information to the developer. This is Apple's mechanism, not something Kakesu sends of its own accord. That information contains none of the URLs or notes you saved.
Kakesu is not built for any particular age group, and it does not knowingly collect personal information from children.
If the contents change, this page is updated and the date at the bottom is rewritten.
The party responsible for this policy — the data controller — is Toru Fukui, the developer of this app. Please get in touch at the address below.
Last updated: 11 September 2026
Kakesu