Privacy & security
Every file you save on their machine is now their problem.
Downloading your slides onto a client's work computer feels like nothing. But their machine is governed by their policies, their monitoring and their audit trail — and your file just joined all three.
5 min read
Mar 2026
Every claim sourced · 2 references
You email yourself the deck, open it on the client's PC, present, and leave. Somewhere in that machine now sit: a download, a "recently opened" entry, a temp copy, and — because it's a managed corporate device — very possibly a log of the whole thing. You don't control any of it, and you can't clean it up.
✕ The myth
"It's just my own file on their computer for five minutes."
It's my content; no big deal to pop it onto their desktop.
✓ The reality
Their machine, their rules, their logs.
A managed device may back up, index, scan and log what you download — and data-protection best practice says don't create copies you don't need.1
There's a second, subtler risk: their content ending up on your device, or yours mingling with theirs, blurring who is responsible for what. Zero-trust security is built on limiting exactly this kind of casual data crossover between parties.2 The clean rule is boring and effective: show, don't save.
Show, don't save
The goal was always to put your slides on their screen, not your file on their disk. Keep the document on your own device and stream the view to the display. Your content stays yours, their machine stays clean, and there's no awkward "let me just delete this" as you pack up — nothing was ever downloaded to delete.
Logged
Managed corporate PCs may record downloads and file activity you can't see or remove.
Caches
Opening a file leaves temp copies and history that "delete" often misses.
Crossover
Mixing files between parties muddies responsibility — the thing zero-trust avoids.
2
⚖ The honest bit — sometimes they ask for the file
Deliberate hand-offs are fine — through the right door.
Of course a client will sometimes legitimately want a copy: the proposal, the spec, the deck for their records. That's completely reasonable — the point isn't "never share," it's "don't share by accidentally saving onto a random machine." Send it deliberately through a controlled channel: an email they can govern, a secure portal, or an expiring link, so the copy lives somewhere accountable rather than scattered in a shared PC's Downloads folder. Intent, not accident.
Where SyncBy!App fits
SyncBy is "show, don't save" by construction: you present from your own phone or laptop to their screen, and nothing is downloaded onto the client's computer. When they genuinely want the document, you hand it over on purpose, through whatever channel your compliance rules prefer — not as a stray file left on their desktop. The display gets the pixels; their disk gets nothing.
TL;DR
- Downloading onto a client's managed PC creates copies, caches and audit entries you can't control.
- Data-minimisation and zero-trust both say: don't create the copy, don't blur the boundary.12
- Default to "show, don't save" — stream the view, keep the file on your device.
- Honest caveat: real hand-offs are fine — do them deliberately via a controlled channel.