Is it legal to submit fake digital identification documents to private companies? Suppose that Facebook asks me to verify my identity. Is it then legal for me to create a fake digital image of a passport showing my pseudonym as the real name and submit that as if it were an image of a real passport?
Nope. 18 U.S. Code § 1028 - Fraud and related activity in connection with identification documents, authentication features, and information (a) Whoever, in a circumstance described in subsection (c) of this section— (1) knowingly and without lawful authority produces an identification document, authentication feature, or a false identification document; [...] (c) The circumstance referred to in subsection (a) of this section is that— (1) the identification document, authentication feature, or false identification document is or appears to be issued by or under the authority of the United States or a sponsoring entity of an event designated as a special event of national significance or the document-making implement is designed or suited for making such an identification document, authentication feature, or false identification document; So you're 1) producing a false identification document that 2) appears to be issued by the United States. Whether you'd actually be prosecuted for this is something that I'm not qualified to answer.
First, agree w/Dale M re: it would be an egregious and likely career-ending move for an attorney to fake his representation. That said, there is likely no reason why you would be unable to request such proof of representation. Your job consists of protecting the assets of the trust, carrying out any other duties outlined in the trust document, being honest and in communication with the trust's beneficiary, managing the assets, and ending the trust as determined by the trust document. Several of those points (particularly the "protecting the assets" part) argue heavily in favor of your confirming the veracity of any claims involving the trust and/or the identity or true intent of those seeking any information, etc., with respect to the trust. Also, demand letters are letters stating a legal claim and usually asks for restitution or performance of an obligation. It's not entirely clear what constitutes a "demand letter requesting information" unless you have a legal duty to provide that information (and this would - or should - be stated in the demand letter itself). Finally, should you be unable to obtain the confirmation you're seeking, you should consider consulting a trust administration attorney. In most cases, you may use trust assets to pay for expert help (including tax preparers and accountants).
You quoted the definition of personal data from Art 4(1) GDPR. This definition of identifiability is further explained in Recital 26: […] To determine whether a natural person is identifiable, account should be taken of all the means reasonably likely to be used, such as singling out, either by the controller or by another person to identify the natural person directly or indirectly. To ascertain whether means are reasonably likely to be used to identify the natural person, account should be taken of all objective factors, such as the costs of and the amount of time required for identification, taking into consideration the available technology at the time of the processing and technological developments. […] If the user ID is unique, then the hashed user ID will be unique as well. Thus, the hashed ID will enable “singling out”, and would still count as identifying in the sense of the GDPR. You also claim that there's no way to reverse the hash. This is not quite correct. Assuming that the hash function itself is secure, then the only way to crack the hash is to brute-force the input. The difficulty of brute-forcing depends only on the entropy of the input data, not on the size of the output hash. It is thus comparatively easy to crack hashes of short low-entropy strings like sequential integer user IDs, IPv4 addresses, or weak passwords. In contrast, it would be difficult to crack long random user IDs, such as UUID version 4 identifiers created from a cryptographically secure RNG (CSPRNG). Even if the hashes can't be cracked, they are not anonymous – you can link them to the original user ID, after all. The GDPR only considers data anonymized if there are no “reasonably likely” means to re-identify the data subject. If this de-identification is reversible, it's called pseudonymization instead. If storage allows, a better technique to generate pseudonymous IDs is to create a table that maps the true ID to a CSPRNG-random ID. Unlike a hash, the random ID cannot leak extra information about the original ID. This pseudonymization technique could perhaps also be turned into irreversible anonymization by deleting the ID mapping, assuming that no “singling out” can happen. Pseudonymization is a very good security measure. It is explicitly mandated whenever appropriate in Art 32 GDPR. So you should probably use it. It's just that GDPR continues to fully apply to processing of the pseudonymized data. Since the pseudonymized data is the data subject's personal data, you may be required to delete it when receiving an Art 17 request for erasure. You may also be required to forward the request to others with whom you shared the data. However, the right to erasure has many conditions and exceptions. If you actually need to keep the data for a particular purpose, chances are good that you can keep it.
Is X considered personal data? Can you use X to directly or indirectly identify a natural person? In the data to which you have access can X be related to an identifiable natural person? If you answer yes to either of those questions then X is personal data. Article 4(1): ‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person; Scenario 1: you want to count each user agent that comes to your site, that's the only data you have, then the user agent is not personal data (it cannot be used to identify someone - unless it has a name and address etc, which seems highly unlikely - and you cannot relate it to anyone). Scenario 2: you have customer records with names, addresses etc (clearly personal data) and want to record each customer's user agent then the user agent is personal data (it relates to the identifiable natural person). Scenario 3: in one dataset you record that a user agent was associated with order ID 123456 and in another dataset you record that order ID 123456 was for John Smith (plus address etc), then the user agent is personal data (it relates to the identifiable natural person). Is this considered storing personal data? If X is personal data. Do I need user's consent to record X? If you want to record X and X is personal data, then you must have an Article 6 lawful basis for recording X. Consent is one of the six lawful bases. Processing shall be lawful only if and to the extent that at least one of the following applies: (a) the data subject has given consent to the processing of his or her personal data for one or more specific purposes; (b) processing is necessary for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract; (c) processing is necessary for compliance with a legal obligation to which the controller is subject; (d) processing is necessary in order to protect the vital interests of the data subject or of another natural person; (e) processing is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller; (f) processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child. Point (f) of the first subparagraph shall not apply to processing carried out by public authorities in the performance of their tasks.
You are missing something. The fact that you have a tick box and its state is saved in the database is enough. The burden of proof is only "on a balance of probabilities", so someone arguing that they didn't consent would have to demonstrate that you falsified the database entry somehow. In terms of GDPR requirements in general you don't need a greater level of proof than this, the key thing is that you have a robust system in place to obtain proof (such as not allowing data into the database without a tick in the box).
Yup, it's illegal. You want something, they have something you want. They let you have the thing provided that you do certain things, otherwise they won't give it to you. So providing a credit card is material to the contract. You know that the credit card number is false, you are representing that it is true, the card is a material fact, you intend to get them to allow you in using this false representation, they don't know it is false and they rightfully rely on your truthfulness. They have been harmed by your false representation (maybe: it would cost you a lot in attorney fees to try to challenge on this point). This is fraud.
No. That clause does not give other users a licence to reproduce the work (other than what is necessary to access or use it) or create derivative works. The copyright owner has the exclusive right to do those things. (See 17 USC 106.) The clause you quote only indicates that other users can "access" (download for viewing) your "information" and use it, too. It doesn't give away any of your exclusive copyright in the work. You do grant Facebook a licence to do certain things with your work in section 2.1 of the Terms of Service, though.
Submit emails in their totality Your testimonial affidavit can quote or cite them as applicable. There is no protection of anyone’s privacy in court. By the way, the email where admissions were made is probably inadmissible if it was sent were in the course of bona fide negotiation to resolve the dispute. If the other party objects they will be thrown out - I wouldn’t hang my case on them.