Account data & privacy

What stays in this browser

Plays, formations, merges, installs and team information save locally in this browser first. Local saving is immediate, remains available offline and does not disappear when you sign out.

The browser also keeps small account-specific sync markers such as the last verified cloud revision and checksum. Clearing browser/site data can remove the local playbook and these local markers.

Optional cloud playbook and recovery history

If you create an account, the authentication provider stores the account information needed to sign you in, such as your email address and login-provider records.

Signing in alone does not enable new cloud features. Cross-device sync and automatic recovery history are separate choices on the Account page, and a manual recovery point does not enable either automatic feature. The current cloud copy mirrors the latest Plays, Formations, Merges and Installs instead of creating duplicate library items every time you edit something.

Recovery history is separate from the current playbook. Verified snapshots do not appear as duplicate plays or installs in the normal library. Recovery points are not removed automatically in this release. Pinning is an organizational marker only; pinned and unpinned recovery points remain until you deliberately delete them.

Access and sessions

Cloud playbook and recovery-point rows are protected by database row-level security so an authenticated account can access only rows owned by that account. Cloud operations also validate the signed-in session on the server.

Your login session is persisted in browser storage so you can remain signed in and refresh expired access tokens. You can sign out this browser, sign out other devices, or revoke sessions everywhere from the Account page.

Automatic cross-device sync

After cloud sync is enabled, normal edits still save to this browser immediately. A stable local change is then mirrored to the current cloud playbook a few seconds after you stop editing. Returning to another previously synced device automatically loads a newer cloud copy when that device has no unsynced changes.

On a new empty device, the verified current cloud playbook can be loaded automatically after sign-in. If the browser already contains different unsynced work, LazyPlaymaker stops instead of choosing a winner. You decide which copy becomes current, and the other copy is protected first.

Empty, unreadable or suspicious local data is blocked from automatically replacing a good cloud copy. Offline edits remain local and sync after connectivity returns.