SoloASR

DRAFT for the owner to approve. Not yet the published policy.

SoloASR Hub privacy

The SoloASR Hub at soloasr.bigtent.ai signs invited people in with Google and lets their SoloASR devices find each other. It is run by the SoloASR operator for an invite list. This page says what it receives and keeps.

What Google sends the Hub

• Your Google account ID, email address, whether Google has verified that address, and your name. The Hub asks for nothing else (scopes openid, email, profile) and never sees your Google password.

What the Hub keeps

• Your Google account ID, email address and name, as Google sends them at sign-in.
• The invite list.
• Your devices: each one's name, platform, certificate (its public key), app version, when it was added, last seen and revoked, and a hash of its credential. Never a device's private key.
• The signed list of your devices that the Hub hands to them.
• While a device is signing in (at most 10 minutes): what it sent to start, and hashes of its codes.
• Every device ID the Hub has ever held, as a bare ID, even after the device or account is deleted, so that identity can't sign in again.
• A sign-in record: each sign-in, sign-out and refused sign-in, with the time and the email address. Kept for 30 days.
• Your browser's sign-in session, as a cookie. The Hub keeps only a hash of it, until you sign out or for at most 30 days.

Held in memory only

• While a device is connected: its network addresses on your local network and what it can do (microphone, transcription, its models). The Hub passes them to your other devices so they can find each other, and forgets them when the device disconnects.

What it never keeps

• Your audio and your text. When your devices can't reach each other directly, the Hub will pass their traffic along encrypted end to end; it can't read it and never stores it. On a direct path, none of your audio or text touches the cloud.
• Encryption ends at the computer that transcribes. That computer's owner could read the audio. That's fine on your own machines. On a shared office machine, its administrator is trusted.

Logs

• The web server keeps IP addresses and page paths for 30 days. No path carries a sign-in code or credential; codes that pass through a path are blanked in the log.
• The Hub's service log records errors and why a sign-in or device connection failed, without codes, tokens or email addresses.

Deleting your account

• Deleting signs out and removes every device first, then removes your account, sessions, devices and sign-in record at once. The bare device IDs stay, as above.
• Nightly backups are kept for 14 days, so a copy can remain in them for up to 14 days.
• Your email address stays on the invite list until the operator removes it, so you can sign in again later and start fresh.

Who else sees it

• Your own devices see your device list and each other's addresses and capabilities. Nobody else's devices see yours.
• The Hub runs on a server shared with other BigTent services, each under its own user. The operator can read the Hub's data and logs.
• Nothing is sold or shared with anyone else.

Signing in a device

• On a computer shared with other people, another local user could intercept a desktop sign-in, so only approve a sign-in you started yourself on that computer.

Your choices

• Remove a device, or delete the account, from the account page at any time.
• Ask the operator to take your email off the invite list.

Home