PRIVATE EVALUATION DEMO
Trust & data handling
What enters Guardian, what stays on the server, and how to ask about your information.
- Named-account access
- Retained server records
- Scoped recovery-copy expiry
Before choosing files
Use the supplied synthetic examples or data verified not to identify a person. Do not upload patient-linked information or personal identifiers for this demo. Public availability does not establish anonymity; replacing names with codes does not, by itself, make a dataset anonymous.
Complete files, including unused columns, enter processing. Remove unnecessary columns, direct identifiers and confidential text before choosing a file. Check report extracts, descriptions and policy explanations as well as the prediction table.
What stays on this private server?
- Uploaded files
- Temporary operation material. Normal completion, refusal and failure paths remove temporary files. A crash or cleanup failure can delay removal until recovery cleanup succeeds. Proxy buffering also handles uploaded bytes.
- Results & evidence metadata
- Retained in server-private storage, including input hashes, definitions, label and mapping text, comparison policies, provenance and execution records. Results survive a service restart. Some metadata can contain identifying text.
- Accounts & access records
- Retained separately for account administration and security. Access records can include usernames, IP addresses, timestamps and run or download activity. Disabling an account does not erase these records.
- Backups
- Enrolled recovery archives and readback copies have scheduled whole-copy expiry, with deadlines at 30 days from their recorded original copy date. Active holds prevent disposal. Missed runs retain the original deadline and report lateness; copying, restarting or restoring does not renew it. Disposal is confirmed only after the registered copy is absent and its operator receipt is recorded. Other retained metadata and provider-managed copies remain outside this expiry scope. Removing a live result does not by itself remove older copies or invalidate a previously downloaded signed pack.
- Removal requests & status
- A private journal retains the exact request, its account and result binding, and operator status. Journal retention policy: 365 days after verifiable completion โ adopted, not yet enforced. The current journal remains an operational dependency and is not yet reduced to a minimal accountability record. Safeguards against restoring removed records have a separate lifetime. A request or a scoped completion is not whole-account erasure.
- Your downloads
- Copies saved to your device remain under your control. Review result and provenance text before sharing them.
Recovery copies & journal policy
Inventory observed on 11 October 2026. This is a dated observation, not a live inventory or an erasure receipt.
- Guardian-managed copies
- 14 enrolled whole-copy units were present: recovery archives, readback copies and operator recovery copies. Their existing 30-day deadlines and hold checks remain in force. Original inventory manifests and deletion-control metadata are separate retained dependencies.
- Provider-managed backups
- The authenticated Hostinger console listed two weekly backups, dated 29 September and 6 October 2026, stored in Lithuania. The server location was Frankfurt, Germany. No snapshot was listed in that view. These backups are outside Guardian's enrolled-copy expiry controller. Their final removal and any other provider-internal copies have not been verified.
- Recovery protection
- Controlled result restoration checks retained removal records before access resumes. Restoring an entire provider snapshot can also restore an older deletion journal. Safe provider recovery therefore requires an independently current reference outside that snapshot and isolation before access resumes. This full-provider recovery procedure has not yet been exercised.
What the adopted 365-day policy means
The future minimal record supports accountability: what was requested, its scope, what was removed and why anything remained. Its allowed fields are request and run or account identifiers, the digest of the removed record, timestamps, statuses, acting-account identifier and residual-reason codes. It excludes input and result content; identifiers and digests can still be linkable metadata.
The clock starts from a verifiable completion receipt, including completion limited to its stated scope, or a recorded authority/not-found refusal. Pending backup copies do not start the clock. Reopening or republishing a status must not restart it.
Markers that prevent removed data from returning remain while a restorable copy may still exist. While provider-copy coverage is unresolved, their end date is unknown and retention is indefinite. The 365-day policy does not authorize their removal.
The owner adopted this duration for complaint follow-up and audit; it is not presented as a legal requirement. Review is due every 12 months or when legal requirements change. Actual retirement requires a verified migration, an intact custody chain and restore tests. It is not enabled by this policy statement.
Access & signed downloads
The hosted service uses named accounts and checks ownership of assessment results and downloads. Sign-in cookies support authentication and session protection.
A signed Intake pack contains the same assessment JSON and Markdown as its unsigned downloads, plus a signature record. Verification with the confirmed public signing identity checks the signed bytes. It does not establish the truth of the data, the historical origin of model predictions, or clinical or regulatory acceptance.
Questions & data requests
There is no self-service server-record deletion. The request form records a request for separate operator review.
Contact info@acuvizionai.be about data handling or to request access, correction, restriction or deletion of information relating to you.
Describe what you want reviewed and give only the minimum account or assessment reference needed to locate it. Do not attach datasets, patient information, passwords, private keys or identity-document copies to an initial request.
A request needs manual review of identity or authority, scope, applicable obligations and affected storage. It is not an automatic erasure command. Any removal response must distinguish what was removed, what remains for a stated reason, and unresolved backup or other copies. Signed-in, enrolled accounts can record a request for one completed Intake result on the Assess files page and return to its status link. The request is bound to that account and result. Recording it does not remove files. Current status distinguishes a recorded request, incomplete operator work, pending declared backup copies and completion limited to the stated scope.
Where GDPR rights apply, the responsible controller must respond without undue delay and normally within one month; a permitted extension must be explained within that month. Rights and exceptions depend on the processing concerned. You can also contact the Belgian Data Protection Authority or another competent supervisory authority.
Current scope
Guardian checks supported AI claims against supplied evidence. These four kinds of review answer different questions.
| Review | Question | Current scope |
|---|---|---|
| 1. Report consistency | Do the reported values agree with the supplied rows and declared evaluation rule? | Supported within the accepted input contract. A match applies to those inputs and that rule. |
| 2. Model execution | Did the identified model and preprocessing actually produce these predictions? | Not independently established. Intake does not run your model. A signed pack does not prove model execution. |
| 3. Evaluation design | Are labels, splits, selection history and population appropriate for the claim? | Limited to the evidence and checks explicitly shown. Numerical agreement does not establish label accuracy, absence of leakage or generalisation. |
| 4. Clinical or drug use | Is the model suitable for the intended medical use? | Not established by Guardian. A matching result is not evidence of clinical suitability, drug safety or efficacy, or regulatory approval. |
A signature binds a statement to a signing key and protects its bytes. It does not establish that the statement is true.
Report-only reassessment creates an independent child result. The original result is not overwritten. A child retains minimal parent identifiers, hashes and report-value metadata; removing the parent does not remove that child. Each result needs its own removal scope. Original files are held temporarily during processing, not added to a permanent upload store.
A signed child pack covers its result and reassessment supplement as bytes. Only the existing B1/B2 decisions enter the native claim index. Signature verification alone does not replay the arithmetic or authenticate the original model execution.
This is a retained-state service. Zero retention, secure erasure, complete disaster recovery and readiness for a new real personal-data pilot are not established. This page describes current technical data handling; it is not a certification of legal compliance.