Keys, sessions and access
Public site and page identifiers appear in installation code and cannot authorise editing. Server credentials are shown once, hashed at rest, and must remain in a backend environment. Rotate or revoke them if needed.
Embedded editing uses a short-lived, page-scoped capability obtained after login or a permitted backend request. It stays in memory, never in the iframe URL or browser storage.
Reconnect renews the session without discarding unsaved models. A private Backup can be downloaded when the server is unavailable. Suspension and credential revocation are checked on subsequent API requests.