UrDatabase

Privacy policy

Last updated:

No accounts, advertising or analytics scripts. But serving a website still involves network requests. This is what the downloads site asks for, who receives it, and how to contact us.

Who and what this covers

This policy covers the UrDatabase downloads website, including urdatabase-downloads.web.app and its Firebase Hosting alias urdatabase-downloads.firebaseapp.com. The UrDatabase project maintainer (larabail on GitHub) operates the site and is responsible for the personal information we handle. In this policy, “we” means that maintainer.

The website is separate from the desktop application. Visiting this site or downloading a build does not give the website access to your film folders, local catalogue, credentials or viewing history. The application has its own local storage and network features, described in the application documentation; this is a policy for the website, not a complete description of those features.

Requests made when you visit

Firebase Hosting

Google’s Firebase Hosting serves the website. Your browser sends ordinary request information, including your IP address, the requested URL and browser headers, which can include a user agent and referrer. The hosting service processes request data to deliver the site, detect abuse and provide operational usage information. Google describes this in its Firebase privacy documentation. We use Hosting, not Firebase Analytics, Authentication or a Firebase database, for this site.

Google Fonts

The downloads page loads typefaces from fonts.googleapis.com and fonts.gstatic.com. These requests go directly from your browser to Google and include your IP address and browser request headers, which may identify the referring site. Google states that the Fonts Web API does not use cookies or use this information to create end-user profiles or for advertising. See Google Fonts privacy information. This privacy page uses system fonts instead, so reading it does not make font requests to Google.

GitHub

With JavaScript enabled, the downloads page automatically requests the public release list from api.github.com to show current builds and release notes. GitHub receives your IP address and ordinary request headers. Clicking a download, source, release or issue link also connects you to GitHub or its download infrastructure. Those services handle their own logs and any cookies under the GitHub General Privacy Statement.

Suggesting the right download

The downloads page reads your browser’s user agent and number of touch points, and, where available, processor architecture and the WebGL graphics renderer name. It uses these details to distinguish Windows, Intel Macs, Apple silicon Macs and unsupported devices.

This comparison happens in your browser. The collected hints are kept only in page memory, not saved between visits, and not sent to us or attached to the GitHub API request. They are not used to create a cross-visit identifier. This does not prevent your browser from sending its usual request headers to the services described above. You can always choose a build manually.

Cookies, storage and tracking

The website’s own code does not set cookies or store visitor data in localStorage, sessionStorage or IndexedDB. We do not include advertising, analytics scripts, tracking pixels or session recording. We do not sell personal information or share it for targeted advertising.

Your browser may cache pages, scripts and fonts normally. That is separate from a visitor profile. External services you visit through links have their own storage and cookie practices.

Contact and information you send

For privacy questions or requests, email larabailen.lb@gmail.com. We receive your email address, anything you put in the message or its attachments, and the ordinary email headers. We use that information to respond and handle your request, not to add you to a marketing list. This mailbox is hosted by Gmail, so Google also processes the message under its Privacy Policy.

GitHub issues and comments are public. Please do not put personal data, passwords, API keys or private logs in a public GitHub issue. Use the email address above for private privacy requests, and include only what is needed to explain the request.

Use, retention and processing locations

Where applicable law requires a legal basis, we rely on our legitimate interests in providing and securing the downloads website and responding to messages, and on legal obligations where they apply.

Device-detection hints last only for the page visit. Firebase states that Hosting retains IP data for a few months. Other provider records are retained according to the linked provider policies; we do not set their retention periods. We keep correspondence only as long as needed to handle the request and meet applicable legal obligations.

Google and GitHub operate internationally, so request data and messages may be processed outside your country. Their linked policies describe their processing locations and international-transfer safeguards. Information may also be disclosed when required by law. We cannot promise that third-party logs or public copies of a GitHub post can be removed by us.

Your choices and rights

You can block third-party fonts or disable JavaScript in your browser. The downloads page still has links to the releases on GitHub without scripts, although automatic build selection and release details will not run. This policy needs no JavaScript. Your browser also provides controls for cached files and cookies.

Depending on where you live and which laws apply, you may have rights to access, correct or delete personal information, restrict or object to processing, or receive a portable copy. Contact us at the email address above about information we handle. We may need enough information to confirm that a request concerns you. For data a provider controls independently, use the contact options in its privacy policy. You may also complain to your local data protection authority.

Changes to this policy

We will update this page and its date when the website’s privacy practices change. The policy’s history is available in the public repository.