Data policy

The detailed version.

The Your data page is the plain-language summary; this is the complete policy it points to: what we store, how backups and exports work, and the exact retention and deletion mechanics.

What we store

  • Your site content: every content file for your site's type, in the open, documented SiteValet format: the same bytes the editor writes, readable by any compatible tool.
  • Your media: uploaded photos, artwork, audio, and video files, kept in the durable media store, isolated from the served tree. Media is never silently deleted: every restore point's references still resolve against it.
  • Restore points: every time you hit Save, a restore point captures your content files plus a media index (the last 30 are kept). Media bytes are not duplicated into points; media changes only through an explicit upload or delete.
  • Your account: your email address and a scrambled (hashed) password we can never read, plus the service records the product needs: ownership, plan state, event history, and revoked login tokens.
  • Billing status: whether your plan is active. Card numbers are handled by the payment provider; we never see or store them.

We don't track your visitors for advertising, we don't sell data, and there is no third-party ad code on your site or ours.

Export: your data leaves with you, any time

Dashboard → Export & backup → download. Unlimited, on demand, included in your plan. Three shapes:

  • Full archive (default): a ZIP with the complete template tree at the paths your site serves from, every content file, every uploaded media file, and a manifest (site name, addresses, template, format version, file list). Host the archive root on any static service and your site runs as-is, even completely off SiteValet.
  • Content only: the JSON bundle, for migrating into another tool.
  • Static snapshot: just the rendered site.

Exports are generated in the background (seconds to a few minutes for media-heavy sites), and you are emailed when ready. Download links are valid for 7 days. The content format is documented and portable: it re-imports into any SiteValet-compatible tool, including the local bridge studio mode.

Backups: every Save is a restore point

Your site is pure presentation (it only changes when you edit it), so instead of wasteful scheduled copies, a restore point is captured on every Save, keeping the last 30 saved states. Dormant sites simply keep their last 30 edits.

Restore is owner-initiated from the dashboard: pick a point, preview, confirm. Restore never overwrites silently: your current state is snapshotted first. Support can assist, but cannot restore without it showing in your history. Backups are a safety net, not versioning; editor-level version history is a separate, later feature.

Retention: the honest timeline

Nothing is deleted silently, every milestone sends an email, and every window allows reactivation or export.

EventSite stays liveData retainedReactivateFinal export
You cancelUntil the paid period ends, then a retired notice90 days90 days, one clickOffered at cancel + auto-generated at deletion
Payment fails14-day grace, then offline60 days from suspensionAny time in the windowAuto-generated at deletion
Suspended for causeNo; immediate, while reviewed30 daysOn appealAuto-generated at deletion (except illegal content)

Email schedule. Cancel: confirmation, day-60 reminder, day-82 final warning. Payment lapse: day-0 notice, day-7 reminder, day-13 "offline tomorrow," day-45 final warning. Suspension: notice with reason and appeal path, day-20 pre-deletion warning.

Deletion mechanics, all cases: the served tree is removed first, then the durable media store, then the service records, then backups roll off naturally within 30 days. Before any deletion we generate a final export and email you the link, kept 30 days. You always get a last chance at your data (the one exception: illegal content, which is deleted immediately and reported as the law requires). A released address is never reissued for 30 days, so a just-deleted site can't be impersonated.

Platform backups (the safety net behind the safety net)

Behind the product-level restore points, the service database (ownership, plan state, event history) is dumped daily to a backup store that is never part of the web-served tree, with 30 days of archives on the production stack. Restore is rehearsed regularly.

Questions

Anything about your data: [email protected]. A person reads every message. If you want the full technical details of how the service is built, ask and we'll send them.

Last updated October 26, 2026.