Desktop reads the media folders you configure and keeps your original library on your server. Connector enables authorized remote access and reports connection and server health to Oliyum Cloud. Cloud relay can carry media, catalogue responses and playback requests; local storage does not mean that no information leaves your device.
You choose folders, profiles and sharing permissions. Privacy questions and requests can be sent to admin@oliyum.com.
1. Who and what this policy covers
This policy is provided by Oliyum, the publisher of Oliyum Desktop and Oliyum Connector. It covers these apps and the Oliyum Cloud account, licensing, connectivity and support services used with them. It applies to administrators, viewers and invited guests. Features and data flows depend on your app version, configuration and the services you enable.
Oliyum processes information needed to operate its services. The owner of a self-hosted Desktop server separately controls the folders, local profiles and people allowed to access that server. If someone else manages your server, contact that administrator about information held there. Third-party services have their own privacy policies.
2. Information we access and collect
“Personal information” includes information that identifies you or can be linked to you. The table distinguishes access on your device from information sent to connected services.
| Feature / information | Where it is processed and why |
|---|---|
| Desktop media library | Configured folder paths, filenames, file sizes and modification times; movies, videos, photos, artwork, subtitles and associated metadata; media duration, codecs and technical characteristics. Desktop scans these locally to build catalogues, thumbnails and playback or conversion caches. Media and relevant catalogue information are sent to devices or guests you authorize when they browse, stream or download. |
| Profiles and viewing activity | Profile IDs and names, profile roles, PIN/password verification data, age or content restrictions, folder assignments, favourites, watchlists, playback progress and session activity. These support access control, personalisation and playback on the server. Remote use can transmit the relevant profile, catalogue and playback information through Connector and Cloud. |
| Cloud account and authentication | Name, email address, account/customer identifiers, role and server memberships, password verification data, verification/reset records, session cookies and tokens. Oliyum Cloud uses these to register and authenticate users, manage access and send account messages. Passwords are submitted for authentication; Cloud stores salted password hashes rather than the original password. |
| Trials and licensing | Account email, activation code, installation ID, device/host name, device public key, licence tokens, entitlements, dates and user limits. Desktop exchanges these with the licensing service to activate, validate, renew or release a licence and prevent misuse. |
| Connector pairing and health | Server ID/name, pairing credentials, configured Desktop/Cloud addresses and available local connection addresses. While connected, Connector sends health reports including app/server versions, reachability, timestamps, profile IDs/names, active-stream and transport statistics, transferred bytes, CPU count/load, free memory/memory usage, uptime, conversion status and connection errors. Cloud uses these for discovery, routing, availability, troubleshooting and access enforcement. |
| Network and remote access | IP addresses, connection details, requested paths, authentication/access tickets, session identifiers, timing, bandwidth and relay usage. Remote requests and responses can include catalogue metadata, images, subtitles, media streams and playback activity. Connector and Cloud process them to deliver the requested feature, enforce permissions and manage service usage. |
| Guest sharing | Guest name, email or phone number when provided, shared folder names/IDs, share identifiers, PINs, permissions, expiry and photo-selection/completion details. Desktop and connected Cloud notification services use this information to manage invitations and the access you request. |
| Online information and subtitles | Movie-title/search information, title identifiers, language and subtitle requests are sent to the relevant provider when you use online lookup/download features. Providers also receive ordinary connection information such as your IP address. Downloaded metadata and subtitles are saved for your library. |
| Support, security and purchases | Support contact details, ticket messages and attachments you submit; security/audit records including account/server identifiers, actions, times and IP addresses; licence purchase references, invoice and subscription/usage records where applicable. These support troubleshooting, abuse prevention, billing and recordkeeping. Information visible in a screenshot is also information you submit. |
The apps require file and network access for these functions. They are not intended to collect your unrelated documents, contacts, microphone recordings or precise GPS location. Photos and videos you select may themselves contain personal or sensitive information, including embedded metadata. Remove information you do not want viewers or support staff to see before sharing it.
3. How information is processed
We use the information described above to provide the features you request: organise media, authenticate accounts, enforce profile permissions, deliver playback, maintain licences, connect your server, send service messages, respond to support requests and protect the service. Usage and connection records also support capacity management and any applicable relay limits or billing.
Local playback primarily uses your Desktop server and viewing device. Enabling Connector introduces Cloud pairing and periodic health reporting. Remote playback may use a direct connection when available or a Cloud relay. With relay, request and response content passes through Oliyum infrastructure; the service is not represented as end-to-end encrypted or invisible to the relay operator. Streaming through a relay is distinct from uploading your entire original library into permanent Cloud storage.
Where applicable law requires a legal basis, processing is based on providing the requested service, your consent for optional disclosure, legitimate interests such as security and service reliability, or legal obligations. Optional sharing should be enabled only when you have the necessary permission from the people concerned. A privacy policy does not replace an in-app consent requirement.
Oliyum does not sell the personal information described in this policy or use your private media for targeted advertising.
5. Storage and security
Original media and Desktop catalogue/configuration data are stored on your server and its configured storage. Connector stores pairing/configuration credentials and status information on its host. Cloud stores account, membership, licensing, operational, audit, billing and support records. Viewing devices may store session information, preferences, caches and downloads.
Security measures include password hashing, authenticated sessions, pairing credentials, short-lived access tickets, profile/folder permission checks and restricted remote endpoints. Connections to the public Oliyum Cloud service use HTTPS and secure WebSocket transport. Local Desktop/LAN connections can use HTTP depending on configuration; use a trusted network and do not assume every local connection or locally stored file is encrypted.
No system guarantees absolute security. Protect the server, use strong unique passwords and PINs, keep apps updated, restrict operating-system access to configuration files and backups, and revoke access you no longer need. Do not send passwords, pairing secrets or activation codes in ordinary support attachments.
6. Retention and deletion
Local media remains under the server owner's control. Catalogue records, settings, viewing history and generated files remain until removed through available app controls or by the administrator. Removing a folder from a catalogue is different from deleting its original files. Uninstalling an app may leave configuration, caches, downloads or backups, depending on the installer and operating system.
Cloud account, licence and operational records are retained for the service relationship and as needed for security, support, disputes and legal/accounting obligations. Session and access tickets expire according to their configured lifetimes. Support attachments follow the service's configured retention and cleanup policy. This policy does not promise a fixed deletion period for every record.
Request account closure or deletion at admin@oliyum.com. We will verify your authority, explain applicable retention exceptions and address the request as required by law. Disconnecting Connector or releasing a licence does not automatically delete a Cloud account. Backups and recipients' copies may remain after active records or access are removed.
7. Your choices and rights
- Choose which folders Desktop scans and which profiles can access them. Remove folder assignments or sharing permissions when no longer needed.
- Use local viewing where appropriate. Stop or disconnect Connector to stop its ongoing connection and health reporting; this also affects remote access.
- Use available administrator controls to remove users/profile access, revoke shares, set expiry and restrict downloads. Revocation prevents future authorized access but cannot recover copies already downloaded.
- Use available favourites, watchlist and viewing-history controls to manage local activity. Contact the server administrator for information held on a server you do not own.
- Choose whether to use online metadata/subtitle features or submit support attachments. Review screenshots and remove private information first.
- Request access, correction, deletion, a copy of your information, or withdrawal of consent and objection/restriction where applicable law provides these rights. Contact Oliyum using the address below. You may also complain to the relevant data-protection authority.
Withdrawing permission can make the associated feature unavailable. Identity verification may be necessary before we disclose or delete information. We do not require you to send your password to make a privacy request.
Browser access uses session cookies/tokens and local storage for authentication, preferences and applicable playback/download functions. Clearing browser data can sign you out and remove locally stored preferences or downloads; it does not delete server or Cloud records.
8. Children and family profiles
ChildSafe and family profiles provide content-access controls; they are not a guarantee of suitability or a substitute for parental supervision. Adults who manage a server should configure permissions and obtain any legally required parental consent. Oliyum does not require a child to create an independent Cloud account to use a local family profile. If you believe a child's personal information has been provided without the required permission, contact us to request review and removal.
9. Changes to this policy
We will update this page when features or data practices change and revise the last-updated date. Material changes requiring notice or consent will be handled as required by applicable law. The policy URL remains available without signing in.
10. Contact Oliyum
For privacy questions, access/correction requests, account closure or deletion requests, contact Oliyum Support at admin@oliyum.com. Include the app name, your account email or server identifier and a description of your request. Do not include passwords or secrets.
Policy URL: https://oliyum.com/privacy