Privacy
Tuck has no account, no server of its own and no analytics. Your library lives in your iCloud. This page lists everything that touches the network and why.
What Tuck doesn't do
- No Tuck account. There's nothing to sign up for.
- No analytics, no crash reporting, no tracking, no advertising identifiers.
- No third-party code that phones home. The only outside code in Tuck is three small open-source JavaScript libraries that render articles, and none of them use the network.
- No sign-in inside the app. Tuck never asks for a website password or signs in anywhere for you.
Your library
Everything you save is stored on your device and in the private part of your iCloud, where only you and your devices can read it. That's how your devices stay in step. When something changes, Apple's push notification service nudges your other devices to check iCloud. The nudge carries no content. I can't see any of it, and Apple's iCloud privacy policy covers how it's protected.
What's in there: your folders, each saved article (its link, title, the cleaned-up article text and pictures, its summary, and how far you've read or listened), your highlights and notes, and any book you've imported.
When you save from Safari, Tuck keeps a copy of the page as Safari showed it. That's how Tuck saves the complete article when you're signed in. It also means the copy can hold whatever was on the page, including your name or account details if the site showed them. It stays on your devices and in your iCloud, nowhere else.
Turn off iCloud for Tuck in your device's settings to keep everything local. Delete Tuck from all your devices and remove its iCloud data to remove the library entirely.
What touches the network on its own
To turn a link into a readable article, Tuck has to fetch it. These requests go to the article's own website like a browser's would, with a standard browser identity and nothing that identifies you or Tuck:
- The page itself, for the article text, title and lead image. Tuck skips this when you saved the page from Safari, since it already has it.
- The article's pictures, downloaded once so the reader never loads them live and the site never sees you reading.
- The site's feed, if it has one, for details like the author and publish date.
- A small icon or thumbnail for the list. To choose between the two, Tuck loads the site's home page once. Until Tuck has stored its own copy, the list may load it straight from the site.
- For an http:// link, one quick check for a secure https:// version first.
Text you paste and files you import aren't fetched from anywhere, but if one points to pictures on the web, Tuck downloads those pictures once, the same way.
Sites can set cookies during those fetches, the way they would in a browser. They stay in Tuck's own storage on your device, and Tuck never reads them or sends them anywhere else.
Videos are the one case that involves another company. If a page is a video, Tuck asks the video service (usually YouTube or Vimeo) for its title and thumbnail. For a YouTube video saved from Safari, Tuck may also load the video's public YouTube page, without your account, to read its description and length. Open a video item, or an article with a video embedded in it, and the player loads from that service, under the service's own privacy policy. An audio or video file that belongs to the article itself loads from the article's site only when you press play, never on open. Tuck never downloads videos.
Tuck refuses to connect to anything on your local network.
What touches the network when you ask
- A link you tap opens in your browser, or on iPhone and iPad in Safari's in-app view. From there it's an ordinary web page.
- On the Mac, Preview Link loads a page in a small throwaway popover that keeps nothing afterward.
- Summaries are written on your device by Apple Intelligence. Nothing is sent to Apple or anyone else to make one.
- Read aloud uses the voices already on your device, and Tuck downloads none. To highlight each word as it's spoken, Tuck runs that speech through Apple's on-device speech recognizer. The first time, iOS may download Apple's language model for your device (the same one dictation uses). The audio and the article never leave your device. Tuck keeps the audio it has made for an article, with its word timings, in a private folder on the device, so rewinding and replaying are instant. That cache is never synced or backed up. It's deleted on its own when the article is gone, a week after you finish listening, after 30 days unplayed, or when it grows past 500 MB (oldest first).
- Handoff passes the open article between your own devices, through Apple's Handoff, the way other apps do.
Report a Problem and Send Feedback
These are the only things in Tuck that send anything to me, and only when you press Send. A report or feedback goes to a small server I run at api.tuck.place, which emails it to support@tuck.place and keeps no copy. The server runs on Cloudflare and the mailbox is Google Workspace, so the message passes through those two companies on its way to me, under their own policies. Your connection's address is used there only to limit how many can be sent at once, and it isn't logged.
A report contains: the reason you picked and your note; your email address only if you typed one in; the version of Tuck, your operating system version and your device model (for example iPhone 17); the article's link and title and how it was saved; the article as Tuck showed it to you, plus a fresh attempt at reading it and Tuck's notes on what it decided along the way; and the article's summary, if it had one. If the article was saved from Safari, the report includes that saved copy of the page, and the sheet reminds you that it can contain account details. Your highlights and notes are never included.
Feedback contains only what you typed, your email address if you typed one in, and the version of Tuck, your operating system version and your device model. Nothing from your library is included.
I use reports only to fix the problem you reported and feedback only to make Tuck better, and I delete them when I'm done. If you'd like one deleted sooner, email me.
Purchases
Apple handles payment through the App Store. Tuck never sees your payment details.
Children
Tuck isn't aimed at children and collects nothing from anyone, children included.
Changes and questions
If this page changes, so does the date below, and anything new is explained here in plain words. Questions go to support@tuck.place.
Last updated November 18, 2026.
