Davvy Privacy Policy

Davvy is operated by Polyphasic Developers ("we," "us," or "our"), based in the United Kingdom. This Privacy Policy explains how Davvy handles information when you use the Davvy app for iPhone.

For the product overview, visit the Davvy landing page.

Davvy connects directly to a WebDAV server chosen by the user. Polyphasic Developers operates no Davvy media backend.

Summary

• Davvy has no app account, first-party analytics, first-party crash reporting or tracking.
• The current App Store release contains no advertising SDK, shows no advertising and offers no in-app purchase.
• Davvy connects directly to the WebDAV server you configure and may use TMDb, IntroDB services and SubDL for requested media features.
• Server profiles, credentials, viewing data and selected settings sync through the user's private iCloud storage. The scanned media index stays on the device.
• The iPhone and iPad builds include Google Cast. Its SDK declares unlinked Device ID, product interaction and diagnostic data for analytics and app functionality, without tracking.

What Polyphasic Developers Receives

Polyphasic Developers receives no information about the user's Davvy library, server credentials, viewing activity or use of the app. Davvy has no Polyphasic Developers account system or media backend.

Davvy contains no first-party analytics or crash-reporting service. The third-party services and SDKs below may receive information directly from the device for the features they provide.

Your WebDAV Server

Davvy sends WebDAV listing, authentication and media requests directly to the server addresses the user configures. Those requests can include the server username and password and the media paths needed to browse and play the library. Traffic does not pass through Polyphasic Developers.

Davvy permits a user-configured plain HTTP server. When HTTP is used, credentials and media are not encrypted in transit. Use HTTPS for any server reached across an untrusted network.

The server operator determines what the server logs and retains. If the server belongs to somebody else, their terms and privacy policy apply.

TMDb Artwork and Metadata

Davvy sends an app or user-supplied API key, a cleaned title and an optional year to api.themoviedb.org when searching for metadata. Follow-up requests send TMDb identifiers for title details, external identifiers and season metadata. Artwork loads from image.tmdb.org.

These requests are sent directly to TMDb. TMDb receives ordinary network information such as the device's IP address and determines its own logging and retention. See the TMDb privacy policy.

This product uses the TMDB API but is not endorsed or certified by TMDB.

IntroDB Services

For optional skip-timing lookups, Davvy sends a TMDb identifier, optional season and episode numbers, duration when known, and a Davvy version user agent to api.theintrodb.org.

If the primary service has no result, the fallback at api.introdb.app receives an IMDb identifier, optional season and episode numbers, and the same user agent. The service operators receive ordinary network information and determine their own logging and retention.

SubDL Subtitle Search

SubDL is contacted only after the user supplies a SubDL API key and searches for subtitles. Davvy sends that key, the title, media type, optional year, season and episode numbers, and selected languages to api.subdl.com.

When the user selects a result, Davvy downloads it from dl.subdl.com. SubDL receives ordinary network information and determines its own logging and retention.

iCloud Sync and Device Storage

Davvy uses the user's private CloudKit database to mirror server profiles, including server addresses, folder rules, usernames and passwords. It also mirrors watch progress, watch-intent events, metadata corrections, Continue Watching decisions and hand-made skip marks.

Davvy uses iCloud key-value storage to sync user-entered TMDb and SubDL keys, skip preferences, and film and programme sorting preferences.

This information is stored under the user's Apple Account and is processed by Apple. Polyphasic Developers cannot access the user's private iCloud records. The scanned media index remains on each device.

Google Cast and Local Network Playback

The iPhone and iPad builds include the Google Cast SDK. It discovers and communicates with nearby receivers over the local network and Bluetooth. Davvy may give a selected receiver a local HLS stream URL and the media title so the receiver can play the chosen item.

Google Cast's bundled privacy manifest declares Device ID, Product Interaction and Other Diagnostic Data. It describes these as unlinked to the user, not used for tracking, and used for analytics and app functionality.

This processing is performed by Google's SDK, not by a Polyphasic Developers analytics service. See Google's privacy policy.

Apple Services and StoreKit

Davvy is distributed through the App Store. Apple handles downloads and App Store account activity under Apple's privacy policy.

The shipped app asks StoreKit for product details and current entitlements when it launches. The current App Store release does not expose a purchase to the user. Apple processes these StoreKit requests.

CloudKit uses Apple's silent push mechanism to notify Davvy about private iCloud changes. Davvy has no custom push-notification service.

Advertising and Tracking

The current App Store release does not link Google Mobile Ads, does not display advertising and does not show Apple's App Tracking Transparency prompt. Davvy does not request the advertising identifier and does not track users across apps or websites.

Google Cast's analytics processing is described separately above.

How Data Is Shared

Polyphasic Developers does not sell personal information. Information leaves the device only for the user's WebDAV server, the user's private iCloud storage, Apple services, and the optional or app-supporting third-party services described in this policy.

Each server or third-party provider determines how it processes the requests it receives.

Data Retention

Data stored locally remains until it is deleted through normal use or the app is removed. Data in the user's private iCloud storage remains according to the user's actions and Apple's retention rules.

WebDAV server operators, Apple, TMDb, IntroDB service operators, SubDL and Google set their own retention periods for data they receive. Polyphasic Developers does not hold a copy of that data.

Your Rights and Choices

Users can remove local Davvy data by deleting it in the app where available or deleting the app. They can manage iCloud data and permissions through their Apple Account and device settings, and can stop optional SubDL use by removing its API key.

Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing of personal data, and to complain to a supervisory authority. In the UK, that authority is the Information Commissioner's Office. Contact us if you need help identifying the appropriate provider.

Children

Davvy is not directed to children under 13. Polyphasic Developers does not knowingly collect personal information from children through Davvy.

Security

Connections to Apple, TMDb, IntroDB services, SubDL and Google use encrypted transport. Connections to a user-configured WebDAV server use the transport selected by the user and may be unencrypted when the address begins with http://.

No method of electronic storage or transmission is completely secure. Users should prefer HTTPS for WebDAV servers reached outside a trusted local network and protect their Apple Account and server credentials.

International Transfers

Polyphasic Developers does not operate a Davvy backend or transfer Davvy user data. Apple, TMDb, IntroDB service operators, SubDL and Google operate their own infrastructure and determine any international transfers arising from requests sent to them. Their privacy policies describe their safeguards.

Changes to This Policy

We may update this Privacy Policy when Davvy changes how it handles information. If we make a material change, we will update the effective date and provide additional notice where appropriate.

Contact Us

For questions about this Privacy Policy, contact [email protected].

Polyphasic Developers, Lincoln, United Kingdom.