HappyProto Beta: Data Loss and Availability
Last updated: 18 November 2026
Plain-language summary for closed-beta testers. The binding version is Section 7 of the Beta Terms of Service; if the two differ, the Terms win.
Thanks for testing HappyProto! Before you put anything into your instance, here’s what “beta” means for your data.
TL;DR
- Your data could still be lost. We back up instances, but backups are best-effort during the beta.
- Keep your own copies of anything you can’t rebuild.
- There’s no uptime guarantee. Instances can go down or be slow at any time.
- We may have to reset your instance if a breaking change requires it. We’ll try to warn you 7 days ahead.
- It’s free, and we’ll warn you at least 30 days before anything costs money.
Backups
Each instance lives on a single server. We back it up automatically about every 6 hours, encrypted, to separate storage in the same region (Helsinki, Finland). Backups are best-effort during the beta: if a server fails, you could lose up to about 6 hours of changes, or more if a backup didn’t work.
We also take a short-lived snapshot before we upgrade HappyView, so we can roll back a bad upgrade.
Backups are normally kept for up to 30 days. Restores are done by us; there’s no self-serve restore yet.
What you can rebuild, and what you can’t
| Data | If it’s lost… |
|---|---|
| Public atproto data your instance indexes | Usually recoverable by backfilling from the network again (it may take a while) |
| Your configuration, lexicons and scripts | Gone, unless you kept a copy. Keep these in version control. |
| Private data in spaces | Gone, unless you kept a copy. It exists only in your instance. |
| Your end users’ sign-in sessions | Users will need to sign in again |
Resets
HappyView and HappyProto are moving fast. If a change can’t be migrated safely, we may need to reset or re-create your instance. When that happens:
- we’ll email you at least 7 days ahead, where we can;
- we’ll try to help you save what you need first. There’s no export tool yet, so keep your configuration, lexicons and scripts in version control;
- for urgent security or stability problems, we may have to act faster.
Availability
- There’s no SLA during the beta.
- Planned maintenance happens in a weekly window, on Mondays from 02:45 to 04:00 UTC, and only in weeks that need it. Your instance may restart and be down for a few minutes, usually 10 minutes or less in total.
- Once we offer maintenance emails, we’ll email you at least 48 hours before we use the window.
- Urgent security or stability fixes may happen at other times, without notice.
- Support is best-effort, through email (support@happyproto.at) or Discord (https://discord.gg/Cbt6EVthyQ).
Please don’t
- use your beta instance as the only copy of anything important;
- store private data you’re legally required to keep;
- run anything where downtime or data loss could hurt someone or cost real money.
If you have end users
If real people use your app, you’re responsible for telling them it runs on beta infrastructure, and for what your own privacy policy promises them about their data.
When you delete an instance or close your account
Your instance stops right away. For 7 days we can restore it if you ask. After that, its data is permanently deleted from our servers, and backup copies normally expire within 30 days of deletion.
Questions?
Email support@happyproto.at. Full details: Beta Terms of Service (Section 7) and Privacy Policy.