The short version: your current files, content, and data are always kept — nothing is deleted out from under you. Older revision history is moved to cold storage over time to keep your project fast, but it stays restorable.
Retention by data type
| Data type | Retention | Where it’s stored |
|---|---|---|
| File version history | Current version kept indefinitely. Older revisions are moved to cold storage after 90 days and remain fully restorable. | Project database + cold storage |
| Project checkpoints | Tiered — recent checkpoints kept densely, then thinned to weekly and monthly. Manual and pinned checkpoints are kept longer. | Checkpoint storage |
| Database backups | Automatic backups run on a schedule; retention depends on your plan. Manual backups stay until you delete them. | Encrypted in S3 |
| Deployments | Deployment history is kept alongside the checkpoint each deploy was made from. | Project metadata + storage |
| Uploaded images & files | The current asset is kept; previous versions are retained for 90 days. | S3 |
| Website analytics | Retained in Hiveku’s analytics warehouse and available in your dashboard. | Analytics warehouse |
| CRM, email, and account data | Kept while your account is active. | Project database |
File version history
Every time you save a file, Hiveku records a version so you can roll 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 in Version History and can be restored on demand. The only difference is they’re fetched from cold storage, which takes a moment longer.
Project checkpoints
Checkpoints are project-wide snapshots. Hiveku applies a tiered retention policy — very recent checkpoints are kept densely, then thinned to weekly and then monthly snapshots, while manual and pinned checkpoints are kept longer. You don’t manage checkpoint storage yourself. See Checkpoints for how they’re created, what they capture, and how to restore one.Database backups
Hiveku runs automatic database backups on a schedule, and you can create manual backups anytime. Backups are stored encrypted in S3, and retention is determined by your plan. Manual backups stay until you delete them. 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.
- File revision history, checkpoints, assets, and backups are stored in object storage (S3) 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
If I haven't edited a file in 90 days, do I lose it?
If I haven't edited a file in 90 days, do I lose it?
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.
Is my file edit history ever deleted?
Is my file edit history ever deleted?
No. Older revisions are moved to cold storage to keep your project database fast, but they remain available to restore from Version History. Your current files always stay instantly available.
How is version history different from checkpoints?
How is version history different from checkpoints?
Version history is per-file — it tracks every save of a single file. Checkpoints are project-wide snapshots of all files (and, for managed databases, your data). Use version history for single-file rollbacks and checkpoints for project-wide ones.
Can I keep a specific checkpoint forever?
Can I keep a specific checkpoint forever?
Yes. Pin a checkpoint and it’s kept indefinitely, outside the tiered retention policy. Current file versions are always kept regardless.
How do I export or delete my data?
How do I export or delete my data?
You can download a full SQL backup of your database anytime from Database > Backups. Deleting a project or account removes its associated data. For a complete export, contact support@hiveku.com.
What’s next?
Checkpoints
Project-wide restore points and tiered retention
Back Up Database
Create, download, and restore database backups
Billing
Plans, resource limits, and storage capacity
Deployments
Deployment history and rollbacks