Boring

Privacy policy

Last updated .

Boring is an inbox of new videos from the creators you follow. It is built to know as little about you as it can. There is no Boring account and no Boring server: the app reads feeds straight from the places that publish them, and keeps what you do on your own devices and in your own iCloud.

This page covers the Boring app for iPhone and iPad and this website. It is written to match what the app's code actually does, and the code is checked against it every time it changes.

The short version

What stays on your devices

Your follows and the state of each video (new, seen, watch later, archived) are stored on your device. If you're signed in to iCloud, Apple syncs them between your devices through your private iCloud database, which only you can read. The developer has no access to it. Apple's handling of iCloud data is covered by Apple's privacy policy.

The video list itself, including titles, thumbnails and descriptions, is rebuilt on each device from the feeds and never syncs. Your filter and sort choices and the Super Boring setting are remembered on that device only.

The Picked sort learns from what you do in Boring: which videos you queued, watched (and how far through), opened in YouTube, or archived unwatched, and which channel each was from. That record syncs like your video states, through your private iCloud database, and nowhere else. The Picked order and its reasons are worked out on your device and never leave it. You can reset what Picked has learned in Settings.

Summaries of video descriptions are made on your device by Apple Intelligence. The description never leaves your device to be summarised, and summaries are kept on the device.

To keep your devices in step, iCloud may send the app silent background notifications when something changes. Boring never shows you notifications and never asks to.

Who the app talks to

Boring fetches what it needs directly from these services. Like any internet request, each one sees your device's IP address and the request itself. None of them receives your iCloud data.

HostRun byWhy
www.youtube.comGoogleReading each followed channel's public feed of new videos, looking up a channel's name and icon when you follow it, and YouTube's own player when you watch.
i.ytimg.comGoogleVideo thumbnails.
www.googleapis.comGoogleThe YouTube Data API: video lengths and live status, looked up 50 videos at a time by video ID; a channel's latest uploads, by channel ID, when YouTube's public feeds for that channel fail; and your subscriptions if you connect your YouTube account.
accounts.google.comGoogleSigning in with Google, only if you choose to connect your YouTube account.
oauth2.googleapis.comGoogleKeeping that sign-in working, and revoking it when you disconnect.
oops.nickjones.techThe developerCrash and error reports (see below).
eu.i.posthog.comPostHogAnonymous usage analytics, unless you turn them off (see below).

Beyond those, the app also contacts:

Connecting your YouTube account

This is optional. If you connect your account, you sign in with Google in a secure Apple sign-in window and give Boring read-only access to your YouTube account (the youtube.readonly permission). Boring uses it for one thing: reading the list of channels you subscribe to, so it can follow them for you.

The sign-in is stored in your device's Keychain, on that device only. It never syncs and never reaches the developer. Disconnecting deletes it from the device and asks Google to revoke it. You can also remove Boring's access at any time from your Google account.

Boring's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Boring uses YouTube API Services, and by using that feature you agree to the YouTube Terms of Service.

How your data is protected

Boring is designed so that your data, and anything it gets from your Google account, stays with you. These are the protections in place.

Boring's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. That data is used only to follow the channels you subscribe to. It is never sold, used for advertising, used to train AI models, or shared with anyone, and no person reads it.

Crash and error reports

When the app crashes or hits an error, it sends a report to a Sentry server the developer runs at oops.nickjones.tech, so the problem can be fixed. Reports say what went wrong: the error, where in the code it happened, the device model and system version, and the app's version.

Reports never carry your IP address, an identity, screenshots, a recording of the screen, or the layout of what you were looking at. Web addresses in reports lose everything after the ?, and tokens and keys are removed. Only a small sample of performance timings is sent.

If you install Boring through TestFlight, Apple may also share crash logs and any feedback you choose to send with the developer, as described by Apple.

Usage analytics

To see which parts of the app get used and which don't, the app records what you do in it, anonymously, with PostHog, sending to PostHog's servers in the EU: which screens you open, and which buttons, swipes and settings you use. Each event's details are only choices from short fixed lists, such as which list an item was in, whether it was a video or a Short, or which sort you picked. The app also records when it opens, its version, whether it's a TestFlight or App Store build, and the device model and system version.

Events never include what you watch or follow: no video or channel titles, names or IDs, no links, nothing you type, and nothing from your Google account. Each install gets a random ID made on the device, so events from one install can be counted together, but it isn't linked to you: Boring never tells PostHog who you are, keeps no profile of you, and records no screens or session replays. Boring asks PostHog not to work out your location from your IP address, though PostHog sees the address as part of each request, as any server does.

To stop it, turn off Share usage analytics in Boring's Settings. From then on the app sends nothing to PostHog, and it remembers that choice on the device.

Code from others in the app

Boring includes two third-party libraries: sentry-cocoa, which sends the crash reports described above, and posthog-ios, which sends the usage analytics described above. Neither contains advertising code.

What the app asks Apple for

Boring doesn't ask for your camera, microphone, photos, contacts, location or anything else.

This website

The home page of boring.nickjones.app uses PostHog, sending to PostHog's servers in the EU, to count visits and see how the page is used, such as which links are clicked. PostHog keeps its state in memory, so the site sets no cookies and doesn't recognise you on a later visit. PostHog sees your IP address and browser details as part of each request. Every page of the site also loads a page-view counter that we run ourselves at t.nickjones.app, which counts visits and the pages they view without cookies. Nothing else on the site loads from another company. The site is hosted by GitHub Pages, which keeps its own server logs, covered by GitHub's privacy statement.

Children

Boring isn't directed at children under 13 and doesn't knowingly collect anything from them.

Your choices

Changes

When what Boring does with data changes, this page changes with it, and the date at the top moves.

Contact

Boring is made by Nick Jones. Questions about privacy can go to nick@nickjones.tech.