Your privacy in plain English
FlashDesk is built on a simple idea: the person asking for help should always be in control. This page says exactly what the program collects, what it does not, and — where one area is still being documented — says so plainly rather than glossing over it. Every claim about the client program has been checked against the public source code — you can verify them yourself.
One open question about the relay server
The client program described on this page has been checked against its source code — those claims are solid. The relay server (IP: 139.28.36.247) that introduces two FlashDesk numbers to each other has not yet had the same documentation pass.
What is known: the relay is hosted by Hetzner Online GmbH, operating under German law and EU jurisdiction. Any connection event necessarily transmits both parties' IP addresses and a timestamp to the relay — that is an unavoidable consequence of how TCP connections work. What is not yet confirmed: exactly what the relay logs, how long those logs are retained, and whether they are deleted at all.
"Nothing found while checking" is not the same promise as a page that has been written and verified line by line. This callout will be replaced with a full relay documentation section once that work is done. The caveat stays until it is.
Your screen, your keystrokes, and your files are never written to disk — only sent, live, during a session you accepted.
No screen recording
Nothing from your screen is ever saved to disk or sent to FlashDesk. Screen pixels exist only long enough to be sent live during an active session.
No account, no identity
There is no sign-up. Your FlashDesk number is generated locally and carries no name, email address, or personal information.
No tracking, no cookies
This website loads nothing from other servers, sets no cookies, and runs no analytics of any kind. There is no JavaScript on this page.
You control every session
You see a confirmation dialog before any session begins. One click ends it immediately, at any time, with no delay and no reconnect unless you allow it.
What we collect
FlashDesk keeps very little — and what it does keep stays on your own computer or exists only for the instant it is needed.
Session log
A plain text file saved on your own computer at
%APPDATA%\FlashDesk\session-log.txt.
It records who connected, when the session started and ended, and what was decided —
accepted, refused, or timed out. FlashDesk has no server it reports session history to.
A helper with file access can copy this log the same way they can copy any other file;
the file panel records the name of anything copied.
Your FlashDesk number
Stored in a local config file on your own computer. The relay server that connects two numbers together knows your number and a separate private value your computer uses to prove it owns that number — it does not know your name, and nothing about who you are is attached to the number.
Relay connection data
When two FlashDesk numbers connect, the relay server at 139.28.36.247 (Hetzner, Germany) handles the introduction. Any TCP connection to the relay necessarily transmits both parties' IP addresses and timestamps. What the relay retains in logs beyond the connection event is not yet fully documented — see the callout at the top of this page.
What we don't collect
During a session, your screen is sent live to whoever you accepted — that is the product. What the code does not do is keep a copy of any of it.
Screen contents
Nothing captured from your screen is written to disk. Screen pixels exist only for as long as it takes to send them during a live session — then they are gone. There is no recording, no screenshot history, and no cloud archive.
Keystrokes
What is typed during a session is not logged anywhere, by either side. There is no keylogger. The session log records decisions (accepted, ended, timed out) — never what was typed.
File contents
If a file is copied during a session, its filename is written to your session log so you know what moved. The contents of the file are not stored, logged, or sent anywhere except to the computer your helper is using during the session.
Audio
Audio is transmitted live during a session — your microphone input goes to the helper, the same as screen pixels go to the helper. It is never recorded, never written to disk, and never sent to FlashDesk. Audio exists in memory only for as long as the session is active; when either party ends the session, it is gone immediately.
No account data
There is no registration, no login, and no profile. FlashDesk does not know your name, email address, location, or any other personal information — because you never provide any. There is nothing to look up, hand over, or leak.
No analytics or tracking
The program sends no usage statistics back to FlashDesk. The website loads nothing from any other server — no fonts from Google, no scripts from a CDN, no analytics from anywhere. If you check your browser's network tab on this page, you will find a single stylesheet request and nothing else.
The program's own internal diagnostics — a capture-health log and a diagnostics report, both used for troubleshooting — record only technical numbers (timings, counts, which capture method was used). They never contain anything you saw, heard, or typed.
How long data is kept
Session log — kept by you
The session log lives at
%APPDATA%\FlashDesk\session-log.txt
on your computer. It stays there until you delete it.
FlashDesk does not schedule deletion and does not access the file after writing it.
You can open, read, and delete it at any time using any text editor or File Explorer.
Your FlashDesk number — kept by you
Your number is stored in a local config file and persists until you uninstall or reset the program. No copy of it is held anywhere else beyond the relay's connection table.
Live session data — session only
Screen pixels, audio, and input events exist in memory only during an active session. When the session ends — by either party, for any reason — that data is gone immediately. It is not buffered to disk at any point.
Relay connection data — duration unknown
The relay at 139.28.36.247 necessarily logs connection events (IP addresses, timestamps) as part of normal TCP operation. How long those logs are retained has not yet been verified. See the callout at the top of this page for the full status of relay documentation.
Your rights under GDPR and similar laws
Under GDPR (and equivalent laws including UK GDPR and similar data-protection frameworks), you have specific rights over personal data held about you. Because FlashDesk holds almost no personal data, most of these rights are moot in practice — but here is what each one means for this specific product.
Right of access
You already have it. Everything FlashDesk holds about you is on your own computer:
the session log at
%APPDATA%\FlashDesk\session-log.txt
and your FlashDesk number in the local config file. There is no server-side database to
request access to.
Right to erasure
Delete the session log file directly — it is a plain text file and no backup of it is held anywhere else. Uninstalling the program removes your FlashDesk number from the local config file. There is nothing else to erase from a FlashDesk server, because nothing is stored on one.
Right to portability
The session log is already a plain text file on your own computer. You can copy it, move it, or transform it into any format you like. No conversion or export request is needed.
Right to rectification
The session log records objective events (connection times, decisions) rather than personal profiles. There is no data held about you that could be factually incorrect and in need of correction on our side.
Right to restriction
You can stop any session immediately using the stop button. No connection can start without your active consent via the confirmation dialog. There is no background processing to restrict.
Right to object
FlashDesk does not process personal data for marketing, profiling, or legitimate-interest purposes that you could object to. The relay connection data is the one area where processing happens outside your direct control — see the relay caveat above.
What you can do right now, without contacting anyone
- Read or delete your session log — open
%APPDATA%\FlashDesk\in File Explorer and deletesession-log.txt. - Reset your FlashDesk number — uninstalling removes the locally stored number. A fresh install generates a new one.
- Stop a session immediately — the stop button ends any session at once. No delay, no reconnect unless you explicitly allow one.
- Refuse any connection — the consent dialog lets you decline before any screen sharing begins. No connection can start without your acceptance.
For data requests or concerns not covered above, write to support@flashdesk.org.
Third-party services
Two external parties handle data that FlashDesk cannot fully control.
GitHub — download hosting
FlashDesk releases are served from GitHub (github.com/conorhonor111-art/flashdesk/releases). When you download FlashDesk, GitHub may log your IP address and the time of the request as part of normal server operation. This is a data-processing event by a third party that FlashDesk does not control. See GitHub's privacy statement for details of what they collect.
Hetzner — relay hosting
The relay server at 139.28.36.247 is hosted by Hetzner Online GmbH, a German provider operating under EU law. When your computer connects to the relay, Hetzner's network infrastructure necessarily handles that traffic. See Hetzner's privacy policy for their data-processing terms. A formal data-processing agreement covering this relay has not yet been established — this will be updated when that work is complete.
MSI installer variant
The MSI installer (flashdesk.org/dl/FlashDesk-setup.msi)
installs FlashDesk to %ProgramFiles%\FlashDesk\
and writes an uninstall entry to the Windows registry. From a privacy standpoint,
the MSI variant behaves identically to the portable .exe — the same session log path,
the same local config file, the same data flows. The registry entry contains only the
standard uninstaller metadata (display name, version, uninstall path) and no personal
information.
Children's privacy
FlashDesk is designed for adults seeking remote technical support. It is not intended for use by children under 13 (or the applicable age of digital consent in your jurisdiction). FlashDesk does not knowingly collect information from children. If you believe a child has used FlashDesk in a way that has created a privacy concern, contact support@flashdesk.org.
Data controller and policy changes
Data controller identity
For the purposes of GDPR and similar data protection laws, the data controller is:
Conor Honor
Kyiv, Ukraine
support@flashdesk.org
Changes to this policy
The date at the top of this page changes whenever the policy changes. The current version was last reviewed in September 2026.
For material changes — new data collection, new third-party sharing, or changes to your rights — a note will be added to the Changelog. There is no email notification; check the date at the top if you return to this page.
Contact and further reading
If anything on this page is unclear, or you want to ask about something it does not cover, write to support@flashdesk.org. Replies come directly from Conor Honor, not a support bot. You can expect a response within a few business days.
For common questions about how sessions work, who can reconnect, and what the 90-second reconnect window means, the FAQ has specific answers.
Terms of service are on a separate page.