Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Bouncer privacy policy

Draft for owner and legal review. Not in force. This is the draft privacy policy for the Bouncer apps. The company details, contact addresses, dates and how long information is kept aren't settled yet, so they show as placeholders such as <PRIVACY_EMAIL>. The text may change after that review.

Last updated: <DATE>. Draft: not yet published.

This policy covers the Bouncer apps: Bouncer Mobile for Android and iPhone, and Bouncer Desktop for Windows. They're made by <LEGAL_ENTITY_NAME>, called "S6 Studios", "we" or "us" on this page. The apps let you approve or deny requests for access to your organisation's systems. This page explains what the apps do with information. There's no Mac app yet; this policy will be updated before there is one.

Your organisation's server

Bouncer only works with a Bouncer server that your organisation runs itself. We don't run that server and can't see anything on it.

When you pair an Android phone or an iPhone with that server, the phone makes an approval key. It's a pair of keys: the private key stays locked inside the phone and signs your approvals, and the public key goes to the server so it can check that an approval really came from your phone. When you pair, the app sends the server:

  • the one-time pairing code;
  • the device name you type, and the kind of device (Android, iPhone or Windows);
  • on Android and iPhone, the public key (on Android, with a certificate from the phone saying where the key is kept) and a push token, so the server can notify you.

A Windows PC pairs without an approval key. If you turn on Windows Hello approvals, the PC makes one then, as a Windows Hello passkey, and the app sends the server its public key. From version 0.5.7, it also sends any certificate Windows gives from the PC's security chip saying where that key is kept.

The server also sees your device's network address when it connects, as any web server does. It records the address the device was paired from and when the device was last seen.

After that, the app sends your signed approve and deny decisions, and fetches the requests and access waiting for you. If you ask for access in the app, it sends your organisation's server what you asked for, for how long, and the reason you type. If you save a secret or create a credential in the app, the values you type go to your organisation's server. If you share a credential, or change who it's shared with, that change goes to the server too. When you approve a request from someone else to save a new secret, the value goes from them to your organisation's server and never passes through the app.

If your organisation allows it, you can view a stored secret in the app. The app fetches the value from your organisation's server, shows it on that one screen and doesn't keep it. The server records each view. The value never goes to us, Google or Apple.

The app has no sign-in of its own: your organisation's server knows you by the name its administrator set up, and your device by its pairing. Your organisation decides how long it keeps all of this and who can see it. Ask its administrator.

Screenshots, screen recordings and copies

If your Bouncer app is version 0.5.2 or later, it tells your organisation's server when one of these happens while a screen that shows a secret is open, or a form where you're typing one, or just after it closes because the app went to the background:

  • A screenshot is taken. Android 14 and later, and iPhone.
  • The screen starts or stops being recorded or mirrored. Android 15 and later, and iPhone.
  • You copy a secret you're viewing. Android, iPhone and Windows.
  • Windows couldn't keep Bouncer's window out of screen capture. Windows only.

What the app sends is a short record: what happened, when, whether the screen showed a saved secret (and which one) or a form, and whether Bouncer had asked your device to keep that screen out of captures. Your organisation's server adds who you are and which device it was, and keeps the record in its log. You can see your own in History. So can the people who approve access to that secret, and your organisation's administrator.

The record never includes the screenshot or the recording, the secret, anything you typed, or what you copied. Bouncer doesn't take, read or keep pictures of your screen. The record goes only to your organisation's server, never to us, Google or Apple.

The app sends these records only to a server new enough to keep them. There isn't a setting to turn them off.

Bouncer only knows what your device tells it, so not every screenshot or recording is noticed. On Android 13 and earlier, only copies are recorded. The Windows app can't detect a screenshot or a recording at all. Nothing is recorded on Bouncer's other screens. On Android 14 and later, Android may show its own note that Bouncer detected a screenshot.

On Android and Windows, Bouncer asks the system to keep those screens out of screenshots and recordings, unless you turn on Allow screenshots in Settings. iPhone doesn't let an app do that; instead, the iPhone app hides a value on screen while the screen is being recorded. Each record says whether the screen was protected, or whether you had turned on Allow screenshots.

Notifications

On Android, the app uses Google's Firebase Cloud Messaging to notify you. On iPhone it uses Firebase Cloud Messaging through Apple's push service. Firebase gives the app an installation ID and a push token: two codes that let a notification find this copy of the app.

Phone notifications only reach you if your organisation's server is set up to send them through our Firebase project. Today, only servers that we have set up can do that. Without notifications, the app shows what's waiting whenever you open it.

Firebase and Apple carry only an ID for the event and an ID for the request, and on iPhone the fixed text "Open Bouncer to check your inbox." Neither ID says anything about the request. A notification never contains the request's details, a secret, or anything that could approve it. The app then fetches the details from your organisation's server. On an unlocked Android phone, the notification shows who is asking, from where, for what, why and for how long; on the lock screen it shows only "Access request pending".

In the store apps, we use Firebase only to deliver notifications. Firebase's own software also sends Google technical information about how it's working, such as the app and system version and the device model. Google lists this as used for diagnostics and analytics, and Google says it isn't linked to you. Google describes how it handles it in its own privacy policy. Google and Apple may handle this information outside your country.

The Windows app doesn't use a push service or Firebase. While it's running, it asks your organisation's server directly for new requests, so it can't notify you while it's closed.

Scanning the pairing QR code

On Android, the QR scanner uses Google's ML Kit, which reads the code on your phone. When the scanner runs, ML Kit sends Google technical information about how it's working: the device model and system version, the app's name and version, an identifier for this installation, and performance and error details. Google says it uses this for diagnostics and analytics and doesn't pass it to anyone else. No image from the camera leaves your phone. If you'd rather not use the scanner, type or paste the pairing code instead.

On iPhone the scanner uses Apple's own on-device code and sends nothing. The Windows app has no scanner.

On your device

The pairing and your approval key stay on your device:

  • Android: the key is kept in Android's protected key storage (the Keystore), which doesn't let it be copied off the phone. The code the app uses to prove it's paired is stored encrypted, and Bouncer's data is left out of backups.
  • iPhone: the key is kept in the Secure Enclave, a separate security chip inside the iPhone. The pairing is kept in the iPhone's keychain and isn't backed up or synced to your other devices.
  • Windows: the key is a Windows Hello passkey. From version 0.5.7, when you turn on Windows Hello approvals, Bouncer asks Windows for evidence that the key is kept in your PC's security chip, and your organisation's server checks any evidence Windows gives. Earlier versions don't ask, and keys set up before 0.5.7 have no such evidence (Device keys). The pairing is encrypted for your Windows account.

Fingerprint, face and PIN checks are done by your device itself; Bouncer never sees them.

From version 0.5.2, the app keeps two settings on your device as on-or-off values: Hide values when switching apps and Allow screenshots (iPhone has only the first). Bouncer never sends them. On iPhone and Windows, a backup of your device or your Windows profile may include them, as it can any app's settings.

If you view a secret, the app shows it on that screen and doesn't keep it. If you copy it:

  • iPhone: the copy stays on that iPhone (it isn't shared with your other Apple devices), and iPhone removes it after 30 seconds.
  • Android: the copy is marked sensitive, and Bouncer clears it after 30 seconds if Bouncer is still running.
  • Windows: from Bouncer 0.5.1, the copy is kept out of clipboard history and isn't synced to your other devices by cloud clipboard. Bouncer clears it after about 30 seconds, when Bouncer quits, or when Windows ends your session (when you sign out or shut down, for example). If Bouncer crashes or is forced to close, it can't clear the copy, and the copy stays on the clipboard until something else is copied. Earlier versions used the ordinary clipboard, where clipboard history and sync could keep a copy.

What we don't do

The apps show no ads, don't track you across apps or websites, and have no analytics or crash reporting of our own. We don't sell your information. Apart from Google's Firebase and ML Kit, and Apple's push service, described above, we don't share it with anyone.

Test builds that we send to named testers through Firebase App Distribution include Firebase's in-app feedback, which sends a tester's report and screenshot to our Firebase project when the tester chooses to send it. The apps in Google Play, the App Store and the Microsoft Store don't include it.

Deleting your data

Sign out in Settings. The app asks your organisation's server to remove this device, then deletes the pairing from the device, and on Android and iPhone the approval key too.

  • Android: uninstalling also deletes everything Bouncer keeps on the phone.
  • iPhone and Windows: sign out before you uninstall. Uninstalling may not remove the pairing: iPhone usually keeps keychain items after an app is deleted, and Windows doesn't always remove the pairing either. On Windows, the Windows Hello passkey stays after both; on Windows 11 you can remove it under Settings > Accounts > Passkeys.

Uninstalling removes the push token from your device, not from Firebase; Firebase deletes tokens that aren't used on its own schedule. Records on your organisation's server are deleted by its administrator. We have no account for you, so there's nothing for us to delete. If you have a question, email <PRIVACY_EMAIL>.

How long information is kept

  • Your organisation's server: your organisation decides.
  • Google and Apple: they keep push tokens and technical information for the periods in their own policies.
  • Emails you send us: <RETENTION, TO DECIDE>.

Your choices

You can choose not to use the QR scanner (type or paste the pairing code instead), not to allow notifications (you then see requests when you open the app), and to sign out at any time. For information on your organisation's server, contact your organisation, which is responsible for it. <YOUR_RIGHTS, TO DECIDE>

Children

Bouncer is a workplace app and isn't meant for children.

Changes

When this policy changes, we'll update this page and the date at the top. If the apps start sending anything new, we'll update this policy before that version is released.

Who we are

<LEGAL_ENTITY_NAME>, registered in <JURISDICTION>. Postal address: <POSTAL_ADDRESS>. Privacy questions: <PRIVACY_EMAIL>. Help with the app: <SUPPORT_EMAIL>. This policy is governed by <GOVERNING_LAW>.

This manual covers Bouncer 0.5.7. Built from source commit cdd3b5958d5be0b33e865b1b56b770f6bccffaf7 (workspace version 0.5.7+34).