UNITIQX / DIRECTORYINDEPENDENT STATIC PUBLIC DOCUMENTATION
06 / your week away

The VPS keeps running.
Conversations are not its storage.

You can delete ChatGPT conversations without intentionally deleting applications and artifacts already written to the VPS. Public Caddy entrances, system services and scheduled audits run independently of the current chat.

INDEPENDENT OF CHAT HISTORY

What remains in place

Already deployed code, public HTML, service configuration, data stores, release receipts and systemd schedules remain on the host unless independently changed or deleted.

NOT AUTONOMOUS DEVELOPMENT

What won't magically continue

The server's configured timers can run checks and backups. A chat transcript being deleted does not cause AI agents to build arbitrary new products or confer any new API access.

PUBLIC CHECKPOINTS

Where to check after a week

Start at this static directory. Check its generated timestamp, public status, model quotas and product receipts before assuming live functionality.

RECOVERY GAP

What cannot be guaranteed yet

Local backup timers do not prove independently restored, encrypted offsite backups of the full service stack and identity settings. Expect gaps to remain until tested.

Day-one return checklist.

  1. Open the public directory status, and inspect how recently it was checked.
  2. Confirm the public hub and factory respond and can perform their intended nonprivileged tasks.
  3. Read the current Frontier model budget. Shared CPU quotas may be full temporarily.
  4. If the Hostinger HTTPS entry is unavailable, the separately hosted public Vercel continuity page can provide orientation. It is not a backup of server databases or live failover.
  5. Inspect unfinished and verified work rather than accepting a generic “everything complete” claim.
  6. Before any sensitive owner change, verify the private restoration evidence and authorization in the VPS administration boundary.

Privacy and permission boundary

Public release can include incomplete project status, demos, schematics and sanitized test facts. It must not include user sessions, database dumps, access keys, raw private files, SSH consoles or arbitrary unauthenticated writes. A week-away platform with stable permissions is safer and more credible than an ownerless public server.