Skip to main content
Hiveku keeps your work safe and available without you having to think about storage. This page explains how long each kind of data is retained, where it lives, and what (if anything) is ever removed.
The short version: your current files, content, and data are kept, and nothing is deleted out from under you, apart from the few items in the table below that expire on a schedule, such as the content of a sent email 30 days after it is sent. Older revision history is moved to cold storage over time to keep your project fast, but it stays restorable.

​
Retention by data type

​
Earlier copies of files

Every time you save a file, Hiveku keeps an earlier copy so you can bring it back. Over time that history can grow large, so it’s tiered:
  • The current version of every file is kept inline and instantly available — forever, no matter how long ago you last edited it. There is no “inactivity” cleanup; a file you haven’t touched in a year keeps its content exactly as it was.
  • Older revisions (more than 90 days old) are moved to cold storage. They are not deleted — they stay listed under the file’s History and can be brought back on demand. The only difference is they’re fetched from cold storage, which takes a moment longer.
To bring back a single file, open it in the code editor and click History. For the whole site, go back to a version, or use Project history to bring back images and data too.

​
Restore points

Restore points are project-wide backups of pages, images and data, listed in Project history. Hiveku keeps them on a schedule, so you don’t manage their storage:
  • The last 7 days: every restore point.
  • 7 to 30 days old: the newest of each kind for each day (for example, one daily backup and one saved before an AI request).
  • 30 to 90 days old: the newest of each kind for each week.
  • Older than 90 days: removed.
Some are kept on purpose: your 20 most recent ones you saved yourself (up to 90 days old), the last 5 saved when you published to production (at any age), and any restore point one of your versions relies on. A project holds at most 100; past that, the oldest go first, never one kept on purpose. See Project history for when they’re saved, what they hold, and how to restore one.

​
Database backups

Backups, under Hosting > Backups, are copies of your site’s files, media and database. Hiveku makes them by itself, and you can make one yourself at any time. They are stored encrypted, separate from your project’s database, and kept on this schedule:
  • Automated backups of Your site run each night from 2 AM UTC when it has a database and its files or media changed since its last backup. Hiveku keeps each one for 30 days, then one a week until they are 90 days old.
  • Manual backups are kept for 90 days: every one for its first 7 days, your 20 newest for the whole 90 days, and of the others one a day until they are 30 days old, then one a week. The safety copies Hiveku saves before a restore or a rollback count as Manual backups too, so they are among the 20. A backup that a saved version needs is kept as long as that version.
  • At most 100 backups are kept for a site. Past that the oldest go first, except Manual backups under 90 days old and the backups of recent publishes to Production.
See Back Up Your Database for how to create, download, and restore backups.

​
Where your data is stored

  • Project files and metadata live in your project’s database.
  • Earlier copies of files, restore points, assets, and backups are stored in object storage with encryption at rest, separate from your project’s database. This separation is what lets Hiveku retain a deep history without slowing down your project.
  • Website analytics are stored in Hiveku’s analytics warehouse, optimized for reporting in your dashboard.

​
Plan limits

Retention is about how long data is kept; your plan determines how much you can store and use (projects, databases, contacts, and more). See Billing for the limits on each plan.

​
Common questions

No. The current version of every file is always kept, no matter how long ago you last edited it. The 90-day mark only applies to older revisions in a file’s history — and even those aren’t deleted, just moved to cold storage where they stay fully restorable.
No. Older copies are moved to cold storage to keep your project database fast, but they remain available to bring back from a file’s History. Your current files always stay instantly available.
An earlier copy is one file as it was at an earlier save. A version is a saved copy of all your pages, on Your site or a branch. A restore point in Project history backs up pages, images and, for a project with a database, its data. Bring back one file from its earlier copies, go back to a version for your pages, and use a restore point when images or data must come back too.
Yes. Save it yourself with Save restore point in Project history: your 20 most recent saved ones are kept for 90 days, while automatic ones are thinned after 7 days. Give it a name you will recognize. Current files are always kept regardless.
To download your data, go to Settings > Export data: your websites’ code and databases, your records as spreadsheets, your automations and your files. See Export your data. Deleting a project removes that project’s data. Deleting an account removes the account’s data and also deletes the profile of anyone whose home account it is, which removes those people from every other account they belong to.

​
What’s next?

Project history

Restore points for pages, images and data

Back Up Database

Create, download, and restore database backups

Billing

Plans, resource limits, and storage capacity

Deployments

Deployment history and ways back