A Bethemesh account lets you retrieve your recipes on several devices. You do not need an account to use the tools.
Synchronized data
Synchronization may include:
- saved pipelines;
- personal templates;
- associated favorites;
- version and conflict metadata.
Data that is never synchronized
Source files, previews, results, undo and redo histories, and temporary content remain local.
Why separate them?
This boundary preserves the Local First promise while providing a convenient backup for recipes.
Good to know: an account does not turn Bethemesh into a file-storage service. It synchronizes only lightweight JSON configurations.
Limits and user control
A synchronized recipe may contain a pipeline name and its settings, so avoid deliberately placing secrets in either. Deleting a synchronized item should propagate to connected devices, while a JSON export remains an independent backup. Files processed by a pipeline are never part of this mechanism.
Lifecycle of synchronized data
Creating or changing a recipe produces a new local revision, which is uploaded once a network connection is available. A deletion must also synchronize so that another device does not bring the item back. Signing out of an account should not automatically erase local recipes without confirmation.
Pipeline names, settings, and descriptions can reveal how work is organized. Do not put passwords, tokens, or unnecessary personal data in them. The service should clearly state its retention period, account-deletion process, and transport protections.
Creating a JSON export is still recommended before a large deletion or an initial merge. Cloud Sync improves continuity; it does not replace a backup you control or the need to verify restored recipes.