3 ms·
If you document it properly then this basically destroys any legal claim they can make about that checkbox.
by amelius 1mo ago
If you document it properly then this basically destroys any legal claim they can make about that checkbox.
- vb-8448 1mo agoOut of curiosity, how one is supposed to "document it properly"?
- deleted 1mo ago[deleted]
- g-b-r 1mo agoYou can obtain a cryptographic proof by recording the tls exchange, including the keys You need to use a tls intercepting proxy for that. I couldn't find any ready-made tool unfortunately, there's tlsnotary.org but it seems far from simple.
- vb-8448 1mo agoSo basically I record what the browser sends to the server when I click the toggle and the server response? I wonder how I can attach a timestamp that cannot be faked.
- amelius 1mo agoLook into court-grade eDiscovery Software. https://en.wikipedia.org/wiki/Electronic_discovery https://en.wikipedia.org/wiki/Electronic_discovery Specifically forensic web preservation or web capture tools. PS: If they made it impossible for you to prove that you clicked a checkbox or not, then, logically, the burden of proof is on THEM.
- g-b-r 1mo agoThat Wikipedia article seems to have no bearing on the issue; there's not even any log on a normal user's computer of having or not having clicked a checkbox. > If they made it impossible for you to prove that you clicked a checkbox or not, then, logically, the burden of proof is on THEM Even in Europe the only "proof" that's required to companies is a log or database entry (both easily manipulated); if a user strongly disputed to have done it and sued the company for that, maybe you'd able to obtain some investigation on their systems.
- g-b-r 1mo agoIf you have the TLS session with all the keys, that's signed with the server's key, so it's basically certified by them themselves. They could only claim that it's been faked by claiming that you stole their TLS private key.