TuneFalls · Quick Lateral

Privacy policy

Effective 27 October 2026

Your Plex library and playback

The TuneFalls apps connect directly from your device to your Plex Media Server (or through Plex's relay when a direct connection isn't possible). Your music, audio and artwork flow between your device and your server — TuneFalls has no server in that playback path. Optional sync and music metadata lookups send the data described below to their respective services.

You sign in with your Plex account through Plex's own sign-in flow. The resulting access token is stored on your device and used only to talk to Plex on your behalf; we never see your Plex password. Plex is a separate company with its own privacy policy.

The apps prefer secure Plex connections where available. A Plex server configured for local HTTP can use an unencrypted connection on your network; secure storage of a token on the phone does not encrypt that network connection.

Anonymous app analytics

The Mac, iPhone, and Android apps report that they launched and a periodic heartbeat while running, so we can count active installs. These events carry a random install ID, the app version, and the platform — no name, no email, no Plex identity, and no listening data. They're processed by PostHog on EU servers in anonymous mode, and development builds send nothing. The ID is stored locally and sent with these events; it is not linked to your Falls or Plex account by the app. Removing local app data removes the local ID but does not delete events already received by PostHog.

Anonymous play counts

When a song starts, the Mac, iPhone, and Android apps send its artist, title, and time of play to our server so we can count plays across all listeners. To count listeners as well as plays, the app also says whether this is your first play of that song today, this week, month or year, and whether it's your first play of any song in each of those periods. Your device works the answers out itself, from a small record it keeps of when it last counted each song, and sends only the answers. If you use Falls sync, plays synced from your other devices update that record too, and a signed-in app fills it once from your account's synced plays, after an update or when you first sign in: our server looks up when each song was last played in your sync data and sends just that back to the app, storing nothing new. Until then, that app's plays are counted from their synced copy, as older versions' are, or, if its sign-in has expired, the app sends their answers itself. Clearing your play history clears the record. Each play carries only a random ID of its own, used so a resent play isn't counted twice — no install ID, no account, no Plex identity, no device details, and no file paths, and the play counter doesn't record your network address. Plays of a local file with no title tag aren't counted, including plays synced by older versions of the app, so the file's name never reaches the play counts. Development builds send nothing.

Our server keeps totals, not a record of each play. For each song, and for all songs together, it keeps plays and listeners per day, week, month and year, plus each song's all-time plays and the first and last day it was played. The time of play only decides which day, week, month and year a play is added to. A listener is one Falls account, or one device when you're signed out, so listener numbers are approximate. The random ID is kept for about 30 days so a resent play isn't counted twice, then deleted. It is stored with only the day it arrived.

Plays synced to a Falls account by older versions of the app, which didn't send play counts themselves, and by an updated app before it has filled its record, are added to the same totals from the account's sync data. The server works out the same first-play answers from that synced history while it counts them, and stores nothing new about the account. Nothing in these totals is linked to you, your account or your device.

Music metadata lookups

Features like library enrichment and station building look up artist, album, and track names against public music databases (MusicBrainz, Last.fm). Those queries contain only the names of the music being looked up — nothing about you or your account.

Mood and activity stations also use TuneFalls' shared music metadata service. The app sends keys derived from artist and track names to look up cached classifications, and can send artist and track names for tracks needing classification. This works without a Falls account. Our service stores those names and classifications in a shared music cache and uses OpenRouter and Anthropic to classify the music from its names; it does not send your audio, Plex credentials, or Falls account identity to those providers. As with other network requests, the receiving service can receive connection information such as an IP address.

Falls account (optional)

You only need an account to buy or manage a subscription, or to use cross-device sync. If you create one, we store your email address and your subscription status. Sign-in uses emailed magic links, so there's no password to store. Payments are handled by Stripe — we never see your card details. Transactional emails (magic links, receipts) are delivered via Resend.

Cross-device sync (optional)

If you sign in to a Falls account and enable sync, the things sync exists to carry — your radio stations, thumbs and learned taste, play history and listening stats — are stored on our sync server, tied to your account, so your other devices can pick them up. This account-linked sync is optional and its data is included when you request account deletion.

The website

tunefalls.com uses Google Analytics to measure website visits and interactions, including clicks on download links. Google Analytics uses cookies to distinguish visitors and sessions. See how Google uses information from sites that use its services. Your theme preference is kept in your browser's local storage. This privacy page itself loads no analytics or ad tags.

Retention and deletion

• Usage events are identified by a random install ID, not your account. Clearing app data removes the local ID; this does not itself erase previously received events.
• Falls account data and synced listening data are kept while your account exists. You can request deletion of your Falls account and associated TuneFalls sync data through our account deletion page or by emailing hello@tunefalls.com.
• Anonymous play counts are kept only as totals, with no identifier; individual plays are not stored. The random ID sent with each play is deleted after about 30 days. Deleting a Falls account doesn't change these totals, since they aren't linked to it.
• Release-notes signups are kept until you ask to be removed.
• Shared music classifications are cached by artist and track rather than by Falls account. They are not removed by deleting a Falls account.

Deleting a Falls account does not delete your Plex account or music on your Plex server. Removing TuneFalls from your device does not by itself delete your Falls account or synced data. If specific records must be retained for legal obligations, we will explain this when handling your request.

Your rights

Under UK and EU data-protection law (GDPR) you can ask us for a copy of the personal data we hold about you, ask us to correct it, or ask us to delete it. Email us and we'll do it — there's little to hold in the first place.

Children

TuneFalls is not directed at children under 13, and we don't knowingly collect personal data from them.

Changes

If we change what we collect, we'll update this page and the effective date above before the change ships.

Contact

TuneFalls is made by Quick Lateral. For anything privacy-related, email hello@tunefalls.com.