Do I need to share my Epic password in chat or with support?
No: do not send your Epic password, temporary authorization code, or private sign-in material through chat or support. Use the official Epic authorization page supplied by the website's linking flow and confirm the intended account there.
Keep authentication on its intended page
The device-code flow requests verification through Epic and then waits for approval. If Epic needs you to sign in, complete that step on the genuine Epic page rather than pasting credentials into a support conversation or a cosmetic control. A website password and an Epic password also belong to different accounts and should not be interchanged. Read the destination and purpose of the form before entering anything, particularly when several tabs are open and one of them belongs to an older authorization attempt.
Treat codes and links as sensitive too
A temporary code can look less important than a password because it expires, but it still participates in an authorization request. An email sign-in link or a complete verification address can also grant access when used by someone else. Do not include those values in screenshots shared publicly, Discord messages, or error reports. When showing a linking problem, crop the image to the state label and explanation. Describe whether the request is pending, expired, or confirmed without exposing the material used to approve it.
Give support facts they can actually use
A useful account-linking report contains the time, your browser or device type, the step you attempted, and the visible error message after removing personal details. State whether the expected account name appeared, without providing its private identifiers. That information helps distinguish a wrong account, expired request, and delayed confirmation. Anyone who needs your password to explain a normal setup message is asking for information beyond what that explanation requires. Keep the recovery process tied to the official controls already presented by the service.