How your data moves
AuthBeam has no database or file storage for your users, so there's nowhere for them to be kept. Here is where they go at each step. Your own account is separate: see the privacy notice.
Reading your users
- A file on your device: read by your browser. It isn't uploaded.
- A link to your cloud storage: your browser fetches the file from your bucket, using a time-limited link you create.
- Entra ID: your browser reads users straight from Microsoft.
- Auth0 and Okta: these calls go through AuthBeam's pass-through. Auth0's API refuses browsers, and Okta doesn't document API tokens from a browser.
Converting them
Always in your browser tab. Users are held in the tab's memory, never in browser storage, and they're gone when you close it or select Clear everything.
Writing them
- Entra ID and External ID: straight from your browser to Microsoft.
- Auth0 and Okta: through the pass-through, which you agree to before each run.
- Prefer nothing goes through us? Download the pack, or save it to your storage, and run the included script on your own machine. It talks only to the vendor.
What the pass-through does
It forwards one request to your tenant and hands back the answer. Users and tokens are in the server's memory only while that request runs. It writes nothing to a database or a file, and it doesn't log request bodies, tokens or tenant names. It works only for signed-in customers, and it can reach only a fixed list of Auth0, Okta and Microsoft addresses.
Your credentials
Client secrets and tokens stay in the tab's memory and are never stored. Vendors refuse secret-based sign-ins from a browser, so the secret you type and the token that comes back cross AuthBeam's pass-through for that request. To avoid this with Microsoft, paste a Graph token or run the script. With Auth0 or Okta, run the script. AuthBeam tells you to delete the app or token when you finish.