What bauta Sends
What bauta sends to our server and when, what it never sends, what the server answers, and what happens when the server cannot be reached.
Only bauta and its gateway talk to our server; the browser never does. This page lists when they do, what they
send, and what the server answers.
What is sent
| when | what is sent |
|---|---|
bauta setup with no account (anonymous activation) | this machine's install id (random, made once), the bauta version |
bauta activate <key> | the license key, the install id, the bauta version |
bauta login | to api.bauta.dev/v1/cli/github: a GitHub token of the scopes read:user user:email (checked with GitHub, then discarded), the install id, the terms version |
bauta status | the license key |
bauta serve, at most once a minute | the license key, the install id, how many personas are active, the bauta version |
For an anonymous activation, the server also sees your IP address, which limits new free activations, and keeps it in memory only.
After bauta login, bauta activates the key it receives, as bauta activate does. bauta logout takes the machine
back to its free session with an anonymous activation. With no account, bauta status answers from this machine and
sends nothing.
What is never sent
- Nothing about pages, URLs, proxies or personas is ever sent.
- The browser sends nothing to our server.
- The GitHub token of
bauta loginreaches only our/v1/cli/githubendpoint, and is never written to disk. bauta browser fetchdownloads from GitHub's releases ofBautaBrowser/bauta-browser, and sends nothing to our server.
What the server answers
The server answers with a signed license token, which bauta keeps in ~/.bauta/license. The token says how many
personas may be active on this machine, and until when; bauta activate prints both. The browser checks the license
once, at launch.
For bauta login, the server answers with your account's license key, which bauta keeps on this machine, and your
plan. For bauta status, it answers with your plan and the sessions in use across your machines.
When the server cannot be reached
If the server cannot be reached, the last token holds until it expires. A persona that is running is never stopped, and a license that expires while the browser runs does not stop it.
Other connections
These do not go to our server:
bauta loginsigns you in through GitHub's device flow: you enter a code on GitHub, on any device.- With a proxy, and no timezone or locale stated in the persona,
bauta serveasks an IP echo through the proxy to place where the proxy exits:https://api.ipify.orgby default, orBAUTA_IP_ECHO. bauta widevine fetchfetches Google's Widevine CDM, the same way Chrome fetches it.
See also the privacy policy.
Next
- Sessions and the license: the license token, renewed by
bauta serve. - Environment variables:
BAUTA_SERVER,BAUTA_LICENSE_KEYand the rest. - FAQ: common questions about your account.