Privacy Policy

iPlay-Lists and your privacy

For privacy questions or a request concerning your data, contact iPlay-Lists at contactiplaylists@gmail.com. Do not send passwords, access tokens or private media files. We do not sell your personal data.

Your library and connected services

The app processes the playlists, folder names, file identifiers, media URLs, metadata, favorites, viewing progress and preferences needed to organize and play the sources you add. Library data and caches are stored on your device. Offline downloads create local copies only when requested; indexing does not itself download entire media files.

Connecting a cloud account, media server or network share is optional. The selected provider receives the requests needed to browse and play your files, including your IP address and authentication information. Credentials are stored in the device Keychain where supported. iPlay-Lists does not need your cloud password when the provider offers its own OAuth sign-in page.

Media identification may send titles, years, artists, albums or media identifiers to TMDB, Apple’s iTunes service and fanart.tv to obtain descriptions and artwork. OpenSubtitles receives your subtitle queries, such as title, media identifiers, season, episode, language or a file hash when available, and your account authorization when you use that feature. A file hash is an identifier calculated from parts of a file, not an upload of the whole video. Casting, sharing and opening external links send the information needed to the destination you choose.

Google Drive

Google Drive is optional. Sign-in and consent take place with Google. The app requests the drive.readonly permission to browse and read files accessible to your Google account. This permission is account-wide: choosing a folder in iPlay-Lists limits the app's indexing, not the scope of Google's authorization.

The app uses file names, identifiers and MIME types to display folders and index supported media. It retrieves file contents for playback or an offline download you request. It does not create, edit, delete or change sharing permissions for your Drive files.

Native Google Drive sign-in on iPhone/iPad stores Google credentials in the device Keychain. The source configuration and local index use encrypted storage. Signing in to Apple TV with a browser instead uses a separate iPlay-Lists HTTPS authorization relay hosted by OVHcloud. This relay exchanges the Google authorization code and keeps access and refresh tokens in an encrypted server-side vault. The TV stores a temporary access token and an opaque renewal credential in its Keychain. The relay handles authorization and renewal; file listings, metadata and media are requested directly from Google by the device, not streamed through OVH. Optional metadata enrichment and synchronization may transmit the derived information described in this policy.

Our use and transfer of information obtained from Google APIs must comply with the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not used for advertising, sold, or used to train generalized AI models. Access is limited to delivering the user-facing features described here; human access is limited to situations permitted by that policy, such as specific user consent or a legal or security need.

Removing a Drive source removes its local source configuration and index without deleting the original Google files. Disconnecting a browser connection attempts to invalidate its session in the Google relay. It does not revoke the entire Google authorization, so that other devices are not silently disconnected. You can revoke iPlay-Lists in your Google account connections. Offline disconnection cannot confirm remote deletion. Downloads, history, favorites and previously synchronized data have separate controls.

Pending Google browser connections expire after 10 minutes; the one-time handover code expires after 5 minutes. A relay connection expires after 60 days without renewal through the relay. Provider revocation or token expiry may require sign-in sooner. Expired records become unusable; physical cleanup takes place during later vault maintenance and is not guaranteed at the exact expiry time. Hosting logs may include IP addresses and OAuth callback request details.

• Google API Services User Data Policy
• Manage Google Account connections

Box and the authentication gateway

The Box connection uses an iPlay-Lists gateway hosted by OVHcloud. It exchanges authorization codes and keeps Box access and refresh tokens in an encrypted server-side store. The app receives a connection credential and short-lived tokens restricted to listing or downloading. Although Box consent includes read/write permission required for this token flow, iPlay-Lists uses this connection to read your selected media, not to modify or delete your files. To issue a token limited to the file you request, the gateway also receives that Box file’s identifier; it does not relay the media file.

The gateway is separate from the native Google Drive connection. Box media is retrieved from Box. Disconnecting Box attempts to revoke and remove the gateway connection; if the network is unavailable, local disconnection alone does not prove that remote access has been revoked. You can also remove authorization in your Box account.

Pending Box sign-ins expire after 10 minutes. A native handover code expires after 2 minutes and a browser handover code after 5 minutes. Connection records expire 60 days after creation or renewal of the provider token. Expiration does not guarantee immediate physical deletion; cleanup occurs during later vault maintenance. Hosting logs may contain IP addresses and OAuth callback request details.

Dropbox and OneDrive

Dropbox and OneDrive sign-in takes place on the provider’s authorization pages, from a compatible Apple device or a browser. On Apple TV, Dropbox uses an authorization code protected by PKCE; OneDrive uses Microsoft’s device-code authorization. The app exchanges and renews tokens directly with the provider, without the Google or Box token vault. These credentials are stored in the device Keychain; the optional iCloud connection profile is described below.

The providers receive the account authorization and requests needed to browse the chosen folders, index file identifiers and names, and read or download compatible media you request. These connectors do not modify or delete your originals. Removing a folder from iPlay-Lists and revoking the app in your Dropbox or Microsoft account are separate actions.

Local transfers and Apple device controls

Importing a playlist to Apple TV by QR code opens a temporary web page served by the TV on your local network. The file you select is transferred to the TV, not uploaded to the public iPlay-Lists website. Browser-based cloud sign-in also offers a local page for handing over a temporary code; account sign-in itself remains on the provider’s pages and, for Google/Box, uses the relay described above. Local pages are temporary and require access to the same reachable network. Their HTTP transport does not offer the protection of HTTPS: use a trusted network and do not publish the address online.

Pairing an iPhone with Apple TV stores pairing credentials in Keychain and uses a protected local connection for playback commands and media references. Apple Watch commands pass through the paired iPhone. Sending a video can transmit the title, playback position and playable URL, including a temporary authorized URL when a file-access service is used. The target TV or receiver then requests the media from its source. These features require the devices and permissions involved; they do not give access to content absent from your authorized library.

Optional iCloud and Trakt synchronization

If you enable iCloud, iPlay-Lists uses private CloudKit data associated with your Apple account for library source references, favorites, metadata choices, watched status and playback progress. Selected subtitle files and album descriptions or track references can also be synchronized. This does not upload your original audio or video files.

“Sync connections and settings” is a separate option, enabled by default when iCloud synchronization is enabled. On iPhone, it can send compatible service credentials, server addresses, API keys, passwords, OAuth tokens and selected app settings in an encrypted private CloudKit configuration payload. The Apple TV receives this profile in its Keychain. This is not a copy of the whole system Keychain. Premium rights, the parental PIN, system permissions and advertising consent are not transferred as app preferences.

A received credential is not necessarily an active sign-in: rotating OAuth sessions can require separate authorization on the TV to avoid invalidating the iPhone session. The connection and settings profile is sent from iPhone to TV; favorites and playback progress keep their bidirectional synchronization. Switching on iCloud does not grant a new third-party authorization or turn on Trakt sharing.

Turning off the connections/settings option on iPhone requests withdrawal of its exported connection profile when synchronization succeeds. Turning it off on TV stops receipt of that profile. Turning off the main iCloud switch stops future exchanges but does not by itself erase existing local or cloud copies. Use the relevant deletion and account controls for copies already stored. Network availability and app activity can delay synchronization; it is not a guaranteed instantaneous backup.

If you enable Trakt synchronization, media identifiers, watched status and progress are exchanged with your Trakt account. Trakt is optional and separate from iCloud. Depending on the device, authorization uses the provider’s device-code page or an HTTPS return page on our site; the app manages its Trakt tokens. Disabling synchronization or uninstalling the app does not by itself revoke third-party permissions or erase their stored data.

Purchases and advertising

Apple processes purchases and subscriptions. The app checks transaction and subscription status to provide your entitlements; we do not receive your payment card details. Manage billing and cancellation through Apple.

The free iPhone/iPad app can display Google AdMob advertisements. Its SDK can process IP addresses, device identifiers, ad interactions, performance and diagnostic information to deliver and measure ads and prevent fraud. The data and personalization depend on consent, platform permissions and Google's settings. The app's advertising privacy choices are available where Google requires them. Premium access disables the app's advertising flow.

We do not provide your Google Drive files, access tokens or library-derived Google data to advertising systems. Advertising consent is separate from connecting a media source.

The Apple TV app does not display iPlay-Lists advertising, including in its free version. Third-party streams can contain their own advertising, which Premium does not remove. The website’s analytics and the iPhone/iPad advertising choices are separate from the TV app.

• Google privacy policy
• Apple privacy policy

Website, support and TestFlight registration

Visiting the website sends technical request information, such as IP address, browser information and requested pages, to our hosting provider OVHcloud. The website includes Google Analytics for audience measurement, Google reCAPTCHA to protect the registration form, and a Spline scene on the home page. These services receive network requests and may use cookies or similar technologies according to their configuration. Browser privacy controls can limit some of this processing; this policy is not a cookie-consent choice.

The TestFlight interest form sends your email address, optional name, selected device and cloud-service interests to Supabase. Registration, invitation and unsubscribe status are used to manage the beta program. Invitations are sent through our OVH infrastructure. Submitting the form is optional and does not guarantee beta access. You can unsubscribe through the invitation or contact us to request deletion.

When you email support, Google/Gmail processes your address, message and any attachments. We use them to respond to your request. Share only what is necessary. Apple's TestFlight service separately handles beta enrollment and may provide crash information and feedback under Apple's terms.

• Supabase privacy policy
• OVHcloud personal data protection
• Spline privacy policy

Purposes and legal grounds

Where the GDPR applies, processing needed to deliver the features you request relies on performance of the service; optional consent-based functions rely on your consent where required. Security, abuse prevention and responding to support requests can rely on our legitimate interests, balanced against your rights. Records required by law are retained to meet legal obligations.

You can use the app without connecting a cloud account or joining the beta mailing list. Refusing an optional permission can make the corresponding feature unavailable. Withdrawing consent does not affect the lawfulness of processing before withdrawal. We do not use your library to make automated decisions with legal or similarly significant effects about you.

Retention and deletion

Local playlists, settings, history, downloads and caches remain according to their feature's storage and removal controls. Cached data may be replaced or purged; downloaded copies and favorites may remain after a source is removed. Keychain credentials and cloud data have separate lifecycles and may survive reinstalling the app.

On Apple TV, downloaded media and caches use storage that tvOS can reclaim. Keep your original files; the app does not promise permanent offline storage.

Beta registration data is used while managing your participation and invitations. Unsubscribing stops invitations but can retain a suppression record so that you are not contacted again. Contact us for deletion of registration or support data. Support correspondence is retained for handling the request and necessary follow-up or legal claims. Server diagnostic logs are retained for operational security and troubleshooting according to the hosting services' retention and backup cycles; they are not an archive of your media library.

An erasure request covers data we control, subject to required legal retention. Apple, Google, Box and other connected providers manage their own account records, backups and retention. Removing a connection does not erase those providers' original files or previously shared data.

Recipients, security and international processing

Access is limited to the service providers needed for the functions described above and to people handling authorized support, security or legal requests. Our infrastructure providers include OVHcloud, Supabase and Google/Gmail. The connected media, metadata, advertising and Apple services act under their own applicable privacy terms.

Public authorization relays use HTTPS and encrypted token vaults. The app uses Keychain and encrypted source storage. Private CloudKit configuration uses encrypted fields; this is distinct from the providers’ own token stores and does not mean the relay cannot decrypt tokens to renew access. No system is risk-free. User-configured unencrypted network shares and temporary local HTTP pages have different protections.

Some providers can process information outside your country, including outside the European Economic Area. Applicable transfer safeguards and locations depend on the provider and service; consult their privacy information or contact us for details. Connecting to a provider does not mean your data is stored only in France.

Your rights and children

Where applicable, you can request access, correction, erasure, restriction or portability of your personal data, object to certain processing and withdraw consent. Contact contactiplaylists@gmail.com and specify the service concerned. We may request proportionate information to verify the request, but never your password. You may complain to your local data protection authority, including the CNIL in France.

The app and beta registration are not directed at young children. Respect the age rules of Apple and the services you connect. A parent or guardian who believes a child provided personal data to us can contact us to request review and deletion.

• CNIL

Policy updates

We update this policy when our features or data practices change. The date above identifies this version. Material changes will be brought to your attention as appropriate, and new consent will be requested where required. Reading or continuing to use the app is not, by itself, consent to optional tracking.