Privacy
Bouncer app privacy policy
What Bouncer Mobile and Bouncer Desktop send, to whom, and what stays on your device.
Last updated 22 November 2026.
Contents
Who this covers
This policy covers the Bouncer apps: Bouncer Mobile for Android and iPhone, and Bouncer Desktop for Windows. They are made by S6 Studios Pty Ltd ("S6 Studios", "we" or "us"). The apps let you approve or deny requests for access to your organisation's systems. There is no Mac app yet; this policy will be updated before there is one.
Visiting this website is covered by the S6 Studios website privacy notice. Emails you send us about Bouncer, including licensing and trial enquiries, are handled as that notice describes.
Your organisation's server
The apps only work with a Bouncer server that your organisation runs itself. We don't run that server and can't see anything on it. Your organisation decides how long it keeps what is described here and who can see it; ask its administrator.
When you pair the app with that server, your device makes an approval key. The official apps are designed to keep the private key on your device to sign your approvals; the public key goes to the server so it can check them. The security model explains what the server can and can't verify about where the key is kept. When you pair, the app sends the server:
- the device name you type, and the kind of device (Android, iPhone or Windows);
- the public key (on Android, with a certificate from the phone saying where the key is kept);
- on Android and iPhone, a push token, so the server can notify you.
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 the resource, how long you want it 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 someone else's request 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.
Screenshots, screen recordings and copies
From version 0.5.2, the app 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.
The app sends 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 records in History, and 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, and there is no 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 screenshots or recordings. 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.
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.
What Firebase and Apple carry is a random ID for the event and a random ID for the request, and on iPhone the fixed text "Open Bouncer to check your inbox." It 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".
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 describes this as used for diagnostics and analytics and says it isn't linked to you. Google's handling is described in Google's privacy policy and Firebase's privacy information. Google and Apple may process this information outside Australia, including in the United States.
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.
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 are designed to stay on your device:
- Android: the key is kept in the phone's Keystore. The pairing's access token is stored encrypted, and Bouncer's data is left out of backups.
- iPhone: the key is kept in the Secure Enclave. 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. 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, two settings, Hide values when switching apps and Allow screenshots, are kept as on-or-off values on your device (iPhone has only the first). Bouncer never sends them. On iPhone, a backup of your device may include them. On Windows they are kept with your Windows profile, which your organisation may back up or roam, as with 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, isn't shared with your other Apple devices, and is removed after 30 seconds.
- Android: the copy is marked sensitive, and Bouncer clears it after 30 seconds if Bouncer is still running.
- Windows: from version 0.5.1, the copy is kept out of clipboard history and cloud clipboard sync. Bouncer clears it after about 30 seconds, when Bouncer quits, or when Windows ends your session. If Bouncer crashes or is forced to close, the copy stays on the clipboard until something else is copied.
What we don't do
No ads. No tracking across apps or websites. 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, as described above, we don't share it with anyone.
Internal test builds that we send to named testers through Firebase App Distribution include Firebase's in-app feedback, which sends a tester's report, screenshot and tester account to our Firebase project when the tester chooses to send it. Store builds don't include it.
Deleting your data
Sign out in Settings. The app asks your organisation's server to revoke 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. 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 unused tokens on its own schedule. Records on your organisation's server are deleted by its administrator. We have no account for you, so there is nothing in the app for us to delete. If you have a question, email privacy@bouncervault.com.
How long information is kept
- Your organisation's server: your organisation decides.
- Google and Apple: they keep push tokens and diagnostic information for the periods set out in their own policies.
- Emails you send us: support correspondence is kept for up to 5 years after the case is closed, and other enquiries for as long as needed to handle them and any resulting business or legal requirements, as set out in the S6 Studios website privacy notice.
Your choices and rights
You can choose not to use the QR scanner, not to allow notifications (you then see requests when you open the app), and to sign out at any time. For information held on your organisation's server, contact your organisation, which is responsible for it.
You can ask us for access to, or correction of, personal information we hold about you, such as your emails to us, by writing to privacy@bouncervault.com. Depending on where you are, privacy laws such as the Australian Privacy Act or the EU or UK GDPR may give you further rights. You can complain to the regulator that covers you, such as the Office of the Australian Information Commissioner.
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
S6 Studios Pty Ltd, ACN 702 723 000 · ABN 29 702 723 000, registered in Australia. Adelaide, South Australia, Australia.
Privacy questions: privacy@bouncervault.com. Help with the app: support@bouncervault.com.
This policy is governed by the laws of South Australia, Australia.