BrowserDeskHelp › At the device › F10
What BrowserDesk stores and who sees what
Your screen, your input and your voice are not stored. What is stored, for how long and who sees it — in plain words.
Preview this guide has not yet been clicked through on a real device. Button names and steps come from the program but may differ in details.
- For
- Person at the device · Employee working from home
- Applies to
- Free · Cloud · Own relay
- from version
- 20261010.22
What it is for
When someone looks at your computer, you may wonder: is this stored? Who can see it later? Here is the answer in plain words. The full version is the privacy policy.
What you need
Nothing. This page only explains.
How to do it
1. What happens during the help
- The helper sees your screen only while the session is running.
- The picture, input and files of the session are not stored.
- On the direct path everything between your computer and the helper is encrypted. Nobody in between can read along.
- If your network blocks the direct path, the session runs through the relay (the switching server). It is still encrypted if both sides use BrowserDesk version 20261010.19 or later. With older programs the operator of the relay could technically see the content. A new program shows in the session when it runs unencrypted like this.
2. Your voice
- Your microphone only switches on if you allow it — every time anew (F5).
- What you say is never stored and never recorded.
- Only the fact that you agreed is logged: who and when. Never the content.
3. Recordings and preview images
- Both are off by default.
- A helper can start a recording during the session. Then the small session window shows REC (F2).
- A recording contains only the picture, never sound.
- Whoever starts a recording is responsible for informing you about it.
4. What is stored nevertheless
If your BrowserDesk runs through browserdesk.de, BrowserDesk stores there:
| What | What for |
|---|---|
| Your device: name, system, version, when it first and last reported | so that the device can identify itself |
| Every session: which device, the internet addresses of both sides, start and end | so that it is traceable who was connected when |
| A log: who triggered what and when | so that later changes are noticed |
| Your consents: what you allowed whom and for how long | so that it is traceable what was allowed |
| Passwords | only as a check value, never readable |
5. For how long
- Session data and device logs: 30 days, then a nightly run deletes them.
- Device and account: as long as you use BrowserDesk.
- The log: as long as you use BrowserDesk.
- Recordings: until someone deletes them.
6. Who sees what
- The helper: your screen, only during the session. You see what he may do in the small window — and you can restrict it (F3).
- Whoever manages your access (for example your company): the device list and the sessions in the administration.
- If your company runs its own relay, all this data stays there. BrowserDesk receives none of it. Your company is then responsible.
How you know it worked
You now know what is stored. For questions, see the privacy policy.
What the other side sees
The helper only sees what your screen shows at the moment. He does not look into your stored data.
Good to know
- Your rights: you can request information about your data, its correction or deletion. For browserdesk.de, write to info@browserdesk.de. If your company runs its own relay, contact your company.
- Feedback from the app: do not write passwords or secrets into it.
- The website browserdesk.de sets no cookies and loads nothing from third-party servers.
If it does not work
| You wonder | Answer |
|---|---|
| Is it being recorded right now? | If the small session window shows REC, yes. Otherwise not. |
| Is someone listening? | Only if you clicked Mikrofon einschalten (Switch on microphone) when asked Mikrofon einschalten?. |
| I want my data deleted | For browserdesk.de: info@browserdesk.de. For your company's relay: your company. |