Spaces:
Running on Zero
Running on Zero
DISCLAIMER §8: document auto-delete behaviour
Browse files- DISCLAIMER.md +13 -0
DISCLAIMER.md
CHANGED
|
@@ -126,6 +126,19 @@ personally-identifiable, or regulated information to a public
|
|
| 126 |
deployment.** Host a private instance for any such material. See
|
| 127 |
[`ACCEPTABLE_USE.md`](ACCEPTABLE_USE.md) §1.7.
|
| 128 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 129 |
## 9. Inheritance to forks
|
| 130 |
|
| 131 |
This DISCLAIMER, in unmodified form, must accompany every distribution,
|
|
|
|
| 126 |
deployment.** Host a private instance for any such material. See
|
| 127 |
[`ACCEPTABLE_USE.md`](ACCEPTABLE_USE.md) §1.7.
|
| 128 |
|
| 129 |
+
By default, the web interface deletes the uploaded source file, rendered
|
| 130 |
+
page images, and intermediate artefacts from the server **as soon as the
|
| 131 |
+
report is generated**. Only the verdict markdown (and its download copy)
|
| 132 |
+
remains, in a session-scoped location that is pruned after the retention
|
| 133 |
+
window (24 h by default). This auto-delete is on by default and can be
|
| 134 |
+
disabled per-audit via the "Delete uploaded file…" checkbox in the GUI.
|
| 135 |
+
It is a best-effort *operational* control on the application layer; it
|
| 136 |
+
does **not** displace platform-level retention, backup, caching, or
|
| 137 |
+
logging behaviour of the underlying hosting infrastructure (Hugging
|
| 138 |
+
Face Spaces, browser-side caches, CDN edges, etc.). Treat the
|
| 139 |
+
auto-delete as a sensible default, not as a cryptographic guarantee of
|
| 140 |
+
irreversibility.
|
| 141 |
+
|
| 142 |
## 9. Inheritance to forks
|
| 143 |
|
| 144 |
This DISCLAIMER, in unmodified form, must accompany every distribution,
|