Quarantine Win10 Users: simple how-to

Forum rules
Guests and members can post here. Only members can EDIT their posts.

Extra Smileys: http://forums.mydigitallife.info/misc.p ... _Editor_QR

Not moderated, so you are on your own. Spambots, stalkers and anti-semites will be banned without notice. Else, POLICE YOURSELF.

Post a reply

This question is a means of preventing automated form submissions by spambots.

BBCode is ON
[img] is OFF
[flash] is OFF
[url] is ON
Smilies are OFF

Topic review

Expand view Topic review: Quarantine Win10 Users: simple how-to

Quarantine Win10 Users: simple how-to

Post by brainout » 06 Sep 2015, 20:58

It has long been known and is now being admitted more often, that Windows 10 uses what's called a 'keylogger', a program which keeps track of all your "typing, inking, and voice" as Microsoft states in its own disclosure about this, at Windows 10 installation. Which then gets sent to MSFT's servers. Allegedly, you have the right to purge or turn that data off. But in the EULA, you have already given MSFT the right to both collect and police, whatever it wants. So then, turning the privacy options off, might be ignored, since by contract in the EULA, you gave MSFT the discretion to collect and police whatever is on your machine.

:!: Not only your data: but the data of any other folks with whom you work, for whom you work, with whom you correspond. :!:

All this was covered in the EULA thread, especially the 'Legal Dangers' posts. Okay, but now what do you do to defend yourself? Well, the first obvious step is, do not adopt Windows 10. But you know, others will. So what are YOUR risks, from others who adopt Windows 10? Can you in effect, guard against them?

You are only at risk from the Windows 10 user, to the extent that user has information about you, on his/her Windows 10 machine. So your first level of risk, is the same as the risk of putting anything into public statements, like comments in articles, Youtube, etc. [highlight=#ccffcc]So you 'quarantine' your communication with such Win10 users, in the same way: to whatever could (accidently or not) be disclosed in public.[/highlight]

Your second level of risk, is deeper: does the Windows 10 user have personal data which you'd never disclose in public? If so, what kind? Were it disclosed, would that harm you or someone else? If 'yes', you can try asking the Windows 10 user to purge that data from Windows 10, so the person can avoid liability for having it on his/her machine, in case MSFT somehow disclosed it. In short, you're helping that person realize s/he's open to future lawsuit.

But what if you don't know whether the person is using Windows 10? Well, the issue isn't relevant until you exchange personal information, like an email address. So if you're asked for your email address, don't answer. Ask what version of Windows the person uses. If the person says 'Windows 10', then get THEIR address, say you'll send an email with the right address for them to use; then create some other new email address which will never have personal information in it; if the person asking for the email address doesn't know your real name, then pick a new email address where you don't have to provide identifying detail, to get a new address. Finally, treat all subsequent correspondence as if it were public.

What if it's a client or patient? Warn them of the Windows 10 slurping/policing rights problem. Client-provider privilege is in effect broken, if a client/patient has Windows 10. They need to know that. If they insist on keeping Windows 10 anyway (and many will, there's a religious fanaticism in such folks); then, get them to say so in writing, keep the email for your own protection. And then use some other computer, to correspond with them, a computer which has no private data on it (or at least, data which isn't already protected under other laws which supercede your being a third and non-contracting party, to someone who has a Win10 machine).

For the risk with such a user, is that data YOU exchanged, though YOU are not a Win10 user, resides on THEIR Win10 machine. So anyone seeking data on you or them, can go to MSFT and petition for the data on THEIR machine.

[highlight=#ccffcc]So now, you quarantine your own machine for use with Win10 folk. Use a computer with no private data on it -- other than the Win10 folks' -- to correspond as needed with Win10 people.[/highlight] Separated from, your other machines. For there eventually will be no way to avoid such correspondence, the willful blindness to the EULA is strong. When a company (MSFT) blatantly tells you it will slurp your data at signup; even if you didn't read the EULA then, you should take pause. But that's not happening. Instead, folks get religiously belligerent.

So when, not if -- when someone among your Win10 contacts is sued by some other party and thus YOUR data exchanged with the Win10 contact is now at risk -- the risk is 'contained'. Limited, to the machine you used. For you didn't use any other machine to communicate with that person.

:?: Could a smart lawyer defeat the foregoing paragraph? :?:

Yeah. And they will try, if you have what someone considers deep (i.e., insured) pockets. But the EULA is limited to data on Win10 devices. So if you have no such devices, that limits the extent of the 'discovery', and if the other person's Win10 device containing what you said is also only on your one non-Win10 device, well.. then the ability of a smart lawyer to get at you, is likely curtailed. Not guaranteed unsuccessful, but definitely reduced success. Right?

[highlight=#ccffcc]Of course, that also means you keep your backups/clones segregated and quarantined, too.[/highlight]

If you can think of some other solution than this quarantine analogy, let me know? Right now, this is the only solution I can think of. Denying the problem won't make it go away.