Legal Consent

Publish a version

1. Open Legal, pick a document — Terms, Privacy or DPA (Cookies is marked Coming soon) — and click New version.
2. Write the content, set the effective date, and choose how it's delivered:
   • Notify users by email — announce + reminder emails (optional).
   • Require in-app acceptance — the blocking gate. This is what drives the SDK.
3. Publish. Signed-in users are gated from the effective date; users who joined before the version took effect are the audience — brand-new users are bound at sign-up and never re-prompted.

How the SDK gate works

Every SDK reads a server-computed blocking flag (enforcement is decided on the server, never the client clock). When a blocking document is outstanding, the SDK presents the hosted gate and, on the user's choice:

• Accept → records the acceptance, then re-checks for the next stacked document.
• Sign out → signs the user out (there is no “dismiss”).

Updates arrive in real time — the moment you publish, the gate appears in every running, signed-in app over a live connection. No polling, no restart.

Per-platform behaviour

Web / Electron — return to login on sign-out

Use ONE SDK instance and subscribe to session changes on onelo.auth — the same instance the consent gate signs out. A separate auth instance would never receive the event.

import { Onelo } from '@onelo/js'

const onelo = new Onelo({ publishableKey: '...', apiUrl: '...' })

// The blocking gate auto-presents on sign-in and on publish. Nothing to wire.
// Just return to your login UI when the gate's "Sign out" clears the session:
onelo.auth.onAuthStateChange((session) => {
  if (!session) showLoginScreen()   // declined gate, revoke, or expiry
})

import { Onelo } from '@onelo/electron'

const onelo = new Onelo({ publishableKey: '...', apiUrl: '...', protocol: 'onelo-my-app' }) // YOUR app's unique scheme — see /docs/security/app-identity
const auth = onelo.auth                     // same instance the gate signs out

app.whenReady().then(async () => {
  const mainWindow = new BrowserWindow({ show: false })
  onelo.consent.setGateParent(mainWindow)   // required for a true modal hard block

  auth.onSessionChange((userId) => {
    if (!userId) { mainWindow.hide(); void auth.presentAuthWindow(null) }
  })
  // ...create + show your window after sign-in
})

Custom UI (drive it yourself)

To build your own gate instead of the hosted one, disable auto-present and read the pending documents. This is the same API the built-in gate uses.

const onelo = new Onelo({ /* ... */ autoPresentConsentGate: false })

// React to a live publish:
onelo.consent.onConsentRequired(() => renderYourBanner())

// Read + record:
const pending = await onelo.consent.requiredConsents()
const blocker = pending.find(c => c.blocking)   // block | notify | unknown
if (blocker) {
  // show blocker.url (the full document), then on accept:
  await onelo.consent.acceptConsent(blocker.versionId)
}

Availability