website: publish D3/D5 (the whole truth on privacy; the minimum machine) and D36's two sentences, HU + EN (operator yes 2026-10-23; R-985, R-991, R-1225, R-1226)

website/en/backups.html

@@ -269,8 +269,9 @@
                     <p>On one disk, every local copy is <strong>on the same disk</strong>. That protects against deleting something by mistake and against broken files, but not against a disk failure. A <strong>different disk</strong> or the <strong>remote backup</strong> protects against a disk failure. Felhom shows this too: it counts a second copy only when it knows for sure that the copy is on another disk, and when it cannot check that (for example inside a virtual machine), it says so.</p>
 
                     <h3 style="margin-top: 24px;"><svg class="ico-lg" aria-hidden="true"><use href="/assets/icons.svg?v=1#i-lock"/></svg> The recovery code – only you know it</h3>
-                    <p>Your remote backup is encrypted, and the key to the encryption is a <strong>recovery code</strong>. The code appears exactly once: on your screen, when it is set up. We keep no copy of it.</p>
-                    <p>This is a deliberate choice, and it has two sides. One: <strong>nobody</strong> but you can read your remote backup – not even us. The other: if the box is destroyed and the code is lost too, then <strong>we cannot restore</strong> the remote backup either. So the code goes on paper, and somewhere safe.</p>
+                    <p>The box encrypts your remote backup before it leaves your home. The key is made on the box, and it stays there. The box also makes a locked copy of the key, which the <strong>recovery code</strong> opens. We keep that locked copy, but we cannot open it. The code is made on the box too, and it appears exactly once: on your screen, when it is set up. We keep no copy of it.</p>
+                    <p>This is a deliberate choice, and it has two sides. One: the remote storage holds only the encrypted backup, and we hold only the locked key. From these, <strong>nobody</strong> can read your backup – not even us. The other: if the box is destroyed and the code is lost too, then <strong>we cannot restore</strong> the remote backup either. So the code goes on paper, and somewhere safe.</p>
+                    <p>One thing we tell you honestly. While your box runs, we have <strong>administrator (root) access</strong> to it for support. With it, we could reach the data on the box and the backup key too. We use this access only to run the service and to fix faults. So the recovery code protects the remote copy, not the running box.</p>
 
                     <h3 style="margin-top: 24px;"><svg class="ico-lg" aria-hidden="true"><use href="/assets/icons.svg?v=1#i-chart-column"/></svg> Monitoring and notifications</h3>
                     <p>We watch the backups all the time. If there is a problem – a failed backup, storage filling up, a connection fault – it shows up in our monitoring, and an e-mail goes out about it. One aim of the closed test is to polish these notifications in real use.</p>

website/en/download.html

@@ -92,6 +92,11 @@
                     <p>Installing <strong>erases every piece of data</strong> on the disk you select. The installer never chooses for you: it lists the disks with their size and type, and overwrites the one you pick.</p>
                     <p>Unplug the external drive you use for backups before you start. If you are not certain which disk is the right one, <strong>stop and call your operator</strong>.</p>
                     <p>The guide from your operator describes every step, screen by screen. Do not start without it.</p>
+                    <h3 style="margin-top: 24px;"><svg class="ico-lg" aria-hidden="true"><use href="/assets/icons.svg?v=1#i-cpu"/></svg> Which machines can it install on?</h3>
+                    <p><strong>At least:</strong> an x86-64 processor (Intel or AMD) with 4 cores, N100 class or newer; 8 GB of memory; a 256 GB SSD. 8 GB runs the basics; the photo app needs 16 GB.</p>
+                    <p><strong>Recommended:</strong> 16 GB of memory and a 512 GB SSD. Photos and films go on a separate data drive.</p>
+                    <p><strong>Not supported:</strong> Raspberry Pi and other ARM boards, Synology / QNAP, routers, rented cloud servers.</p>
+                    <p>To estimate how much memory your own apps need, use the <a href="/en/sizing">Which machine do I need?</a> page.</p>
                 </div>
             </div>
         </section>

website/en/faq.html

@@ -77,7 +77,7 @@
           "name": "What machine do I need?",
           "acceptedAnswer": {
             "@type": "Answer",
-            "text": "For most homes a mini PC (for example with an Intel N100 processor and 16-32 GB of RAM) is perfectly fine. They are quiet, energy-saving (15-35 W) and compact – one fits on the shelf next to the router. If you want more storage (for a film library, say), you can add a NAS or external hard drives. More detailed set-ups are on the Technology page. To estimate how big a machine your own apps need, use the Which machine do I need? page."
+            "text": "For most homes a mini PC (for example with an Intel N100 processor and 16-32 GB of RAM) is perfectly fine. They are quiet, energy-saving (15-35 W) and compact – one fits on the shelf next to the router. The smallest machine: an x86-64 processor (Intel or AMD) with 4 cores, 8 GB of memory and a 256 GB SSD. Recommended: 16 GB of memory and a 512 GB SSD. Not supported: Raspberry Pi and other ARM boards, Synology / QNAP, routers, rented cloud servers. If you want more storage (for a film library, say), you can add a NAS or external hard drives. More detailed set-ups are on the Technology page. To estimate how big a machine your own apps need, use the Which machine do I need? page."
           }
         },
         {
@@ -197,7 +197,7 @@
           "name": "Can you get at my data?",
           "acceptedAnswer": {
             "@type": "Answer",
-            "text": "That is an important, fair question, and I answer it honestly. For support and maintenance I normally have remote access to your server – as any IT provider has to the systems it manages. I need it to check backups, install updates and fix faults. The key to your remote backup, though, only you know: the recovery code appears once, on your screen, and I keep no copy of it. So I cannot read the remote backup either. Important: unlike the big cloud providers, Felhom does no algorithmic analysis of your data and no profiling for advertising, and your data leaves your home only encrypted (the remote backup)."
+            "text": "That is an important, fair question, and I answer it honestly. For support and maintenance I have administrator (root) remote access to your server – as any IT provider has to the systems it manages. I need it to check backups, install updates and fix faults. With this access I could reach the data on your server and the backup key too. I use it only to run the service and to fix faults. The box encrypts your remote backup before it leaves your home, and the key is made on the box. The recovery code only you know: it appears once, on your screen, and I keep no copy of it. So I cannot read your backup from the remote storage or from my central system. On the running box, though, I could reach the key with the access above. Important: unlike the big cloud providers, Felhom does no algorithmic analysis of your data and no profiling for advertising. What you open from outside your home passes through Cloudflare's network and is readable there; the backups leave your home only encrypted."
           }
         },
         {
@@ -533,6 +533,7 @@
                         </button>
                         <div class="faq-answer"><div class="faq-answer-inner">
                             <p>For most homes a <strong>mini PC</strong> (for example with an Intel N100 processor and 16-32 GB of RAM) is perfectly fine. They are quiet, energy-saving (15-35 W) and compact – one fits on the shelf next to the router.</p>
+                            <p><strong>The smallest machine:</strong> an x86-64 processor (Intel or AMD) with 4 cores, 8 GB of memory and a 256 GB SSD. Recommended: 16 GB of memory and a 512 GB SSD. Not supported: Raspberry Pi and other ARM boards, Synology / QNAP, routers, rented cloud servers.</p>
                             <p>If you want more storage (for a film library, say), you can add a NAS or external hard drives. More detailed set-ups are on the <a href="/en/technology#hardware">Technology</a> page.</p>
                             <p>To estimate how big a machine your own apps need, use the <a href="/en/sizing">Which machine do I need?</a> page.</p>
                         </div></div>
@@ -711,9 +712,9 @@
                         </button>
                         <div class="faq-answer"><div class="faq-answer-inner">
                             <p>That is an important, fair question, and I answer it honestly.</p>
-                            <p>For support and maintenance I normally have remote access to your server – as any IT provider has to the systems it manages. I need it to check backups, install updates and fix faults.</p>
-                            <p>The key to your remote backup, though, <strong>only you know</strong>: the recovery code appears once, on your screen, and I keep no copy of it. So I cannot read the remote backup either.</p>
-                            <p>Important: unlike the big cloud providers, Felhom does <strong>no algorithmic analysis of your data</strong> and no profiling for advertising, and your data leaves your home only encrypted (the remote backup).</p>
+                            <p>For support and maintenance I have administrator (root) remote access to your server – as any IT provider has to the systems it manages. I need it to check backups, install updates and fix faults. With this access I could reach the data on your server and the backup key too. I use it only to run the service and to fix faults.</p>
+                            <p>The box encrypts your remote backup before it leaves your home, and the key is made on the box. The recovery code <strong>only you know</strong>: it appears once, on your screen, and I keep no copy of it. So I cannot read your backup from the remote storage or from my central system. On the running box, though, I could reach the key with the access above.</p>
+                            <p>Important: unlike the big cloud providers, Felhom does <strong>no algorithmic analysis of your data</strong> and no profiling for advertising. What you open from outside your home passes through Cloudflare's network and is readable there; the backups leave your home only encrypted.</p>
                         </div></div>
                     </div>
 

website/en/own-cloud-storage.html

@@ -219,7 +219,7 @@
                 </div>
                 <div class="info-card">
                     <p>Your files are on the machine standing at your home. Every night the server makes backups by itself, on three levels: on the box, on a second drive if there is one, and encrypted on remote storage.</p>
-                    <p>The remote copy leaves encrypted, and the key is yours: without the recovery code that copy cannot be read. The machine belongs to you, and there is no storage subscription that climbs year after year.</p>
+                    <p>The remote copy leaves encrypted. The key is made on your box, and your recovery code, which only you know, opens its locked copy. So nobody at the remote storage can read it. For support, I have administrator access to the running box. The machine belongs to you, and there is no storage subscription that climbs year after year.</p>
                     <p>The details are written out on the <a href="/en/backups">Backups</a> page.</p>
                 </div>
             </div>

website/en/services.html

@@ -129,7 +129,7 @@
                         </li>
                         <li class="caps-item">
                             <h4><svg class="ico-lg" aria-hidden="true"><use href="/assets/icons.svg?v=1#i-lock"/></svg> A recovery code only you know</h4>
-                            <p>The key to your remote backup's encryption is a recovery code that appears exactly once — on your screen. I do not know it and cannot recreate it. That also means that without the code, I cannot read the remote backup either: keep it somewhere safe.</p>
+                            <p>The box encrypts your remote backup, and a recovery code locks its key. The code appears exactly once — on your screen. I do not know it and cannot recreate it. If the box breaks, you need this code to bring the remote backup back: keep it somewhere safe. For support I have administrator access to the running box; the <a href="/en/backups">Backups</a> page says more.</p>
                         </li>
                         <li class="caps-item">
                             <h4><svg class="ico-lg" aria-hidden="true"><use href="/assets/icons.svg?v=1#i-rotate-cw"/></svg> Restore when something goes wrong</h4>

website/en/sizing.html

@@ -96,8 +96,9 @@
         <section class="shell-section sizer-advice-section">
             <h2>What the machine needs</h2>
                 <ul class="sizer-advice">
-                    <li>Processor: x86-64 (Intel or AMD), 4 cores, N100 class or newer.</li>
-                    <li>System disk: a 256 GB SSD; 512 GB recommended.</li>
+                    <li>Processor: x86-64 (Intel or AMD), at least 4 cores, N100 class or newer.</li>
+                    <li>Memory: at least 8 GB; 16 GB recommended.</li>
+                    <li>System disk: at least a 256 GB SSD; 512 GB recommended.</li>
                     <li>Photos and films go on a separate data drive.</li>
                     <li>Not supported: Raspberry Pi and other ARM boards, Synology / QNAP, routers, rented cloud servers.</li>
                 </ul>