Planned resets may happen
Database resets may be used during development, testing, maintenance, or major changes to the platform structure.
Open beta
Sklash open-beta data reset notice
Understand how planned database resets may affect accounts, projects, uploads, settings, AI history, and other data stored in Sklash during beta.
Overview
What this means in practice
Explore the systems, responsibilities, and workflows behind this part of Sklash.
Accounts may be deleted
A reset may permanently remove account records and require users to create a new Sklash account.
Project data may be lost
Websites, pages, revisions, uploads, settings, domains, AI history, generated content, and related records may be deleted.
Keep independent copies
Sklash should not be the only storage location for important or irreplaceable beta content.
What a reset means
Beta data may be permanently removed rather than migrated.
Sklash is being developed rapidly. Changes to database structures, account systems, storage, publishing, AI services, or other platform systems may make a clean database reset the safest development path.
When a reset occurs, deleted beta data may not be recoverable even if infrastructure backups exist. Backups are operational safeguards and are not a promise that every beta account or project will be restored after a planned reset.
- User accounts and login records
- Workspaces, sites, pages, components, revisions, and navigation
- Uploaded media and generated assets
- Preferences, domains, publishing configuration, and feature settings
- AI conversations, memory, missions, proposals, and generated content
- Commerce test data and other experimental records
User responsibility
Keep copies of anything you want to preserve.
Do not rely on the open beta as the only storage location for business-critical, confidential, legally required, or irreplaceable material. Export or separately save important text, media, configuration, and records whenever possible.
Sklash will continue to use reasonable security and privacy safeguards, but the beta service does not guarantee uninterrupted availability, recovery, or migration of beta data into the final production release.
Questions
Clear answers before the next step
These answers describe the current pre-release service and may evolve as Sklash approaches production.
Could my entire account disappear?
Yes. A planned database reset may delete the account itself, and you may need to register again.
Will backups always restore my beta projects?
No. Backups support operations, but Sklash does not guarantee that intentionally reset beta data will be restored.
How will I know about a planned reset?
When practical, Sklash may display an in-app warning with the expected reset date. Development needs may sometimes require changes without a long notice period.
Continue
Create an open-beta account
Ready to test Sklash with the beta conditions in mind?
Registration requires an explicit acknowledgement that planned database resets may permanently delete the account and stored data.