Synctuary

Your privacy,
in plain words.

What stays on your devices, what gets shared, and the choices you have.

Read the policy

Synctuary for iPhone, iPad, Mac, Apple Watch and Apple TV. Last updated November 12, 2026.

Synctuary plays your connected Plex library and live TV, and contacts the services you choose. You supply the servers, logins and media. There is no Synctuary account. The app includes no analytics or advertising SDK and does not track you across apps. Live TV channels may carry advertising from their providers.

Most library data and settings stay on your devices. Two optional features send data to services we run: push notifications use stored device identifiers, and bug reports and feature requests are forwarded to our email inbox. This policy explains those details.

What the app stores, and where

  • Services and settings: server addresses, names, themes and layout choices are saved on your device. Service records and some settings are also shared through your private iCloud key-value store. Service credentials are stored separately. On Apple TV, small settings use system preferences and iCloud because the system can clear app files.
  • Service credentials: API keys, provider passwords, M3U playlist and guide links, Plex account tokens, Trakt tokens and Send to TV pairing keys are stored in the device's keychain. On iPhone, iPad and Mac, service credentials and Trakt tokens can also sync through iCloud Keychain. Apple TV keeps its credentials locally. Credentials are sent to the service they belong to. Transfer Setup copies credentials only for the services it supports. Transfer Setup lists any services it cannot copy. Tautulli uses its own API key, supplied by the owner. Connecting it requires PRO. Push tokens are separate, as explained below.
  • Push settings: push tokens are saved in the app's local settings, outside the keychain. Before build 234, the relay's authorisation token was also stored there. Build 234 moves that token into the Keychain. Your devices' push tokens and household setup key are also shared through your private iCloud key-value store so the devices can receive the same alerts. We cannot access that private iCloud store.
  • Offline downloads: films and episodes downloaded on iPhone, iPad or Mac stay on that device until you remove them, reset the app or delete its local data.
  • Artwork and library lists: local caches let the app show posters and titles without fetching them on every visit. Settings → Setup & Help lets you clear those caches. Apple TV may also clear cached files when storage runs low.
  • Search and Siri: library titles are indexed on the device for Siri on iPhone, iPad and Apple TV, and for system search on iPhone and iPad. Synctuary does not upload that index. Apple handles spoken requests under its own Siri terms.
  • Apple Watch: the phone sends the watch what is playing, who is watching, download progress and the week ahead through Apple's Watch Connectivity.
  • Widgets and Apple TV top shelf: Widgets use the app's owner-approved setup and credentials from the keychain to read your connected services, including Plex and Tautulli. Now Playing can show titles, viewer names, devices, playback details, progress and cached pictures. Layouts show different amounts of this information. Progress is estimated between readings; pause and seek changes need a new server reading. Last good readings can be shown with their time when a refresh fails. Owner or setup changes clear cached readings. Widget commands recheck the owner, server and credential before sending. The TV home screen reads a local list of titles. Before build 234, authenticated artwork links were supplied to Apple's shelf service; build 234 caches that artwork locally first. Mac widgets work the same way. The Mac has no Siri, system search or watch feed.

Permissions

Local Network lets Synctuary reach servers on your network and find another Synctuary device through Bonjour for Transfer Setup or Send to TV.

Notifications are optional on iPhone and iPad. You choose which services and events can send alerts. Apple TV and Mac do not receive notifications.

Between your devices

Transfer Setup copies supported selected services and their credentials over your local network. It lists any services it cannot copy. The sending device shows a code; the receiving device needs that code to unlock the encrypted setup bundle. The transfer does not pass through our relay.

Send to TV pairs a phone with an Apple TV using a four-digit code shown on the TV. Both devices keep a pairing key in the keychain. Commands travel over your local network and include the title to play, a signature and a timestamp.

Watch Together uses Apple's SharePlay. The people on your FaceTime call receive the title and playback state, including play, pause, seek and position, so their apps can stay in sync. This uses Apple's services and can travel over the internet. It does not use our relay.

Push notifications

On iPhone and iPad, push notifications use a relay we operate on Cloudflare. Your media services send selected events to it so the relay can deliver alerts through Apple's or Google's push service.

The relay stores a random household ID, a one-way hash of its setup key, each enrolled device's push token and the date it last checked in. A push token identifies an app installation for delivery; it is not a Plex password or API key. Household records do not contain your name, Plex or Trakt account ID, server addresses or library files. On iPhone and iPad the relay also stores a token iOS gives the app's widgets, so a service event can tell the widgets to refresh. A device used by a Plex Home family profile is marked yes or no, so the relay sends it only the alerts meant for family members.

Notification contents pass through the relay. They can include a viewer name, media title or request status. The worker forwards that content to the push provider without saving it in its storage or writing it to a content log. The household records remain in Cloudflare storage.

Household records now expire automatically. The relay update deployed on October 8, 2026 gives each record an expiry thirty days after the newest device's check-in. Receiving notifications does not extend it. A device that has not checked in for thirty days stops receiving alerts even if another device keeps the household active. Stale entries are pruned at a later check-in or leave request. An explicit leave removes that device; the last device leaving deletes the household. Invalid tokens are removed when the push provider rejects them. Earlier records have also been given an expiry.

The next relay update also protects against an old storage copy reappearing during a storage migration. A temporary marker holds only a random household ID and the old record's expiry date. It holds no push token or setup-key hash. Its expiry is fixed at thirty days after the old record's newest device check-in; later joins cannot extend it. The relay schedules automatic cleanup at that expiry and also removes expired markers when handling a household request.

Turning notifications off asks your services to stop sending events. A service that is offline cannot receive that change until it reconnects. Switching alerts off does not erase an existing relay record. Contact us if you want stored relay data removed.

You can use a self-hosted copy of the relay and change its address in Settings. Your relay's operator then handles the data described here.

Bug reports and feature requests

These are optional. Nothing is sent until you submit a form under Settings → Setup & Help.

A bug report includes the area you chose, summary, description, frequency and any steps you entered. If Include app and device details is on, it also includes the app version, device model, OS version, configured service types and whether the connection is costly, such as mobile data. These details are shown in the form and can be left out.

The app does not automatically add server addresses, passwords, API keys or media titles to those details. Extra bug-report diagnostics are off by default from build 234. Anything you write in the text fields is sent as written.

A feature request includes its area, summary, description, app version and platform. It does not add the bug report's device model, service list or network details.

The relay forwards reports and requests to info@synctuary.ca. The worker does not store their contents, but the forwarded emails can remain in our inbox until deleted. The report endpoint uses an IP-based rate limit to prevent abuse.

The in-app forms do not ask for an email address or attach a push token or household ID. They are one-way, so include the details we need to understand the report. Text you enter can still identify you. For a reply, email us directly; that email includes your sender address. Do not put passwords or API keys in either route.

Purchases

Synctuary PRO is bought through Apple's App Store as a subscription or a one-time purchase. Apple handles payment. The app checks purchase status through StoreKit; Synctuary does not send payment details or purchase receipts to a developer-run server. Manage and cancel subscriptions in your Apple Account settings.

Other services the app contacts

A provider sees the requests made to its service and your IP address, as with any internet connection. Providers may keep their own records under their own privacy policies.

  • Plex: signing in uses Plex's own flow, so Synctuary does not handle your Plex password. Plex returns an account token. The app uses it for Plex Home profiles, your watchlist, shared servers, Plex's catalogue, community reviews and account notifications. Plex's free live channels use Plex's guide and streaming services. They may include third-party ads. Ratings and playback updates are sent to the Plex service you use.
  • Plex and Tautulli monitoring: Activity reads current streams and server readings from Plex. If you connect Tautulli, it also reads viewing history, usernames, devices, playback details and IP or location information supplied by Tautulli. Requests go directly to your servers. Synctuary verifies that Tautulli belongs to the selected Plex server. Server-wide management stays behind owner controls. Other supported Plex Home profiles see only their own verified viewing records. Optional playback alerts can contain viewer names and titles and use background checks or your configured push relay. You can share Your Year as a picture after choosing a destination. That picture can identify people, titles and viewing times; the destination you choose handles any copy you save or share.
  • Trakt (api.trakt.tv): when connected for a profile, Trakt receives the film or episode you play, identified by TMDB, TVDB or IMDb number, and playback progress at start, pause and stop. The app also reads that profile's Trakt ratings and history. Disconnecting at Settings → Account → Trakt removes its local tokens and stops future reports for that profile.
  • Live TV providers: an Xtream Codes source receives its login and channel or guide requests. An M3U source receives requests for the playlist, streams and optional XMLTV guide you supplied. Playlist or stream links may contain access credentials. The app connects to those sources directly, without our push relay.
  • TheIntroDB (api.theintrodb.org): when Plex has no intro or credits marker, the app asks for one using the show's TMDB number, season and episode. No account token is attached.
  • TMDB artwork (image.tmdb.org): the app loads posters for titles discovered through Seerr.
  • Apple and Google push services: these deliver alerts passed through the relay.
  • Cloudflare: hosts our relay and forwards submitted reports by email. Its infrastructure handles network requests, including the IP addresses needed to serve them.

Your servers can also contact their own providers. For example, Plex can fetch metadata or subtitles, and Tautulli can look up a remote stream's location. Synctuary reads those server results; it does not make those particular requests itself.

Launch emails

If you give us your email address on synctuary.ca, we keep the address and the time you sent it. We use it only to tell you when Synctuary is available. It is stored with Cloudflare, which runs our website, and it is not shared or sold. We delete the list once the launch email has been sent. To have your address removed sooner, email info@synctuary.ca.

Children

Synctuary is not directed at children. Plex restricted profiles follow Plex's viewing restrictions and hide Synctuary's management screens. Server-wide management is limited to the app owner. Other supported Plex Home profiles see only their own verified viewing records. These controls do not change the push relay and report handling described above.

Your choices

  • Remove a service in Settings to remove its saved record and credential. Deleting a credential that syncs through iCloud Keychain can remove it from your other devices too.
  • Disconnect Trakt to stop reporting playback for the current profile. Signing out of Plex removes the local sign-in token; it does not delete data held by Plex.
  • Turn notifications off to stop selected service events after the services receive the change. This does not delete relay records.
  • Reset Synctuary at Settings → Setup & Help → Reset clears local services, credentials, downloads and settings. It also clears shared iCloud settings and synchronized credentials, which can affect your other devices. Build 234 also asks the push relay to remove this device; other devices stay enrolled. If that request cannot finish, one cleanup request stays in this device's keychain and is retried when the app runs. It contains only the old relay address, household ID and key, push token and retry deadline. No media-service credentials are kept for this cleanup. The request is removed on success, or at the first cleanup attempt after 30 days. Reset does not erase your server's library, other devices' relay records or emails already sent.
  • Before uninstalling, use Reset if you want stored credentials cleared. Deleting the app should not be treated as a request to erase iCloud data, relay records or support emails.
  • Ask us about stored data or deletion at the address below. Because relay records have no name or email attached, we may need enough information to identify the record you mean.

Data handled outside your country

Cloudflare processes relay requests on its infrastructure. Reports are delivered to our Proton Mail inbox. These providers can handle data outside your country, where local laws may allow access by public authorities. Their Cloudflare and Proton policies explain their own practices. Your chosen media services and Apple also have their own terms.

Requests about your data

Email us to ask what data we hold, request a copy or correction, or ask for deletion. Depending on your location, you may also have rights to restrict or object to processing, transfer your data, or complain to your local privacy authority. You can switch off optional features; this does not undo processing that has already happened.

We may need enough information to find your relay record or report and confirm that it is yours. Do not send service passwords or API keys. Synctuary uses the data described here to provide the features you request, understand submitted feedback and prevent abuse. It does not use those records to make automated decisions about you.

Changes to this policy

Updates are published here with a new date. Release notes describe changes to how the app handles data.

Contact

Synctuary is developed by Azim Esmail. Questions about this policy or requests about stored data: info@synctuary.ca.