docs: point the privacy-policy step at the published Gitea remote

docs/PLAY_RELEASE_CHECKLIST.md

@@ -101,20 +101,19 @@ action except the items marked **[code]**.
 - [ ] Host [PRIVACY.md](../PRIVACY.md) at a public URL and paste that URL into the
       Play Console. **This is mandatory** because the app accesses photos. The contact address
       in it is final (`softwareapp.hb@gmail.com`), so the file publishes as-is.
-      This is the one item here that cannot be finished from the working copy, because the repo
-      has **no git remote** yet. Shortest route:
-      1. create a public repository and push this working copy:
-         ```bash
-         git remote add origin git@github.com:<user>/foto-dup-finder.git
-         git push -u origin main
-         ```
-      2. **Settings › Pages › Source: Deploy from a branch**, branch `main`, folder `/ (root)`;
-      3. the policy then renders at `https://<user>.github.io/foto-dup-finder/PRIVACY.html` —
-         open that in a private window to prove it needs no login, then paste it into
-         **App content › Privacy policy**.
+      **Hosting half done (2026-10-14):** the working copy is published to the Gitea instance as
+      [`fishfacegit/foto-duplicate-finder`](https://gitea.softwareapp-hb.de/fishfacegit/foto-duplicate-finder)
+      (`origin` = `ssh://git@gitea-container.incus:2222/fishfacegit/foto-duplicate-finder.git`), so
+      the policy now has a public, login-free URL:
+      - **rendered HTML (use this one in the Console):**
+        `https://gitea.softwareapp-hb.de/fishfacegit/foto-duplicate-finder/src/branch/main/PRIVACY.md`
+      - raw `text/plain` fallback:
+        `https://gitea.softwareapp-hb.de/fishfacegit/foto-duplicate-finder/raw/branch/main/PRIVACY.md`
 
-      Any static host works the same way; the requirement is only that the URL is public, stable
-      and readable without an account.
+      What is left is the Console paste: open the URL in a private window to prove it needs no
+      login, then put it in **App content › Privacy policy**. A dedicated HTML page (the landing
+      page would do) reads better than a file view inside the repo; any static host works the same
+      way, the requirement is only that the URL is public, stable and readable without an account.
 
       > **Note on Play's automatic translation:** it translates the *store listing*, not
       > the hosted policy. If you want the policy in another language, host a translated