Respond when account details are exposed

Stop further copies

Remove the public post or unnecessary share where you can, and tell the intended case owner that the material contained sensitive values. Record where it appeared, the approximate exposure period and whether the audience is known. Keep a minimal incident note; do not spread the original screenshot to prove the disclosure happened.

Ask the provider for containment

Identify the account through its private order reference. Explain which type of value was exposed and ask what invalidation, replacement or account review is available. A local app reset does not establish that a copied secret is invalid. Ask whether any authorised devices need updated details after the provider’s action.

1. Stop sharing the exposed material.
2. Use the established private provider contact.
3. Request the applicable service-side containment.
4. Record what was confirmed and what remains pending.

Review related accounts proportionately

If the exposed password was reused elsewhere, change those accounts’ passwords through their own official routes. If an email account or password manager was involved, secure that account as a separate priority. Enable additional authentication protection where the relevant account offers it. Do not claim that Dream provides a particular security control unless it has been confirmed for that account.

Close the incident truthfully

Confirm the intended account still works through supported steps after any authorised change. Remove obsolete copies from the places you control. Mark unresolved items as pending, including whether earlier values are invalid. The absence of a visible problem is not evidence that nobody copied the details, but a precise record prevents repeated disruptive changes and keeps the response focused.

Questions about this guide