accounts
4 articles with this tag
How to clear browsing history, cookies and saved passwords (Chrome, Safari, Edge, Firefox on computer and phone): what to delete after a leak, and what to keep first
A guide to deleting browsing history, cookies (site data), cache, saved passwords and autofill in Chrome (Windows, Mac, Android, iPhone), Safari (Mac, iPhone, iPad), Edge and Firefox, using the labels in each vendor's official help. Deleting browsing history does not take back anything already copied and is not a defence against a threat. What reduces future harm is dealing with sign-in state (cookies) and saved passwords: change passwords and sign out of all sessions from a safe device. If you will go to the police, record the threatening email and any suspicious extensions before deleting. If sync is on, deletion also removes the data from your other devices on the same account. In the October 2026 Onamae.com Desktop Cloud case, GMO Internet's sixth notice asks customers to keep browser sync off until their device check is done.
How to check if someone accessed your account: sign-in activity, signed-in devices and forwarding settings (Google, Microsoft, Apple, LINE, Instagram, X)
A guide to checking for unauthorized access. Look in three places: (1) sign-in activity and signed-in devices (Google 'Your devices', Microsoft 'Recent activity', Apple Account device list, LINE 'Devices', Instagram and Facebook 'Where you're logged in', X 'Apps and sessions'); (2) account settings (mail forwarding and filters, connected apps, recovery email and phone); (3) the device itself (iPhone configuration profiles, Android device admin apps, browser extensions). This site's take: changing the password alone can leave signed-in sessions, forwarding rules and connected apps in place. If you find something, sign out other sessions, change the password right away, then check recovery details, two-step verification, forwarding, connected apps and payments in that order.
How to check if your password was leaked: using Have I Been Pwned safely, and the checks already built into your browser and phone
A guide to checking for leaked passwords. Have I Been Pwned (HIBP) tells you whether an email address appears in a known data breach, which service it came from and what kinds of data leaked. Its password check (Pwned Passwords) hashes the password on your device and sends only the first five characters of the hash, so the password itself is never sent (HIBP API documentation). This site's take: check your current passwords where they are already saved (Google Password Manager, the iPhone Passwords app, Edge Password Monitor, or your password manager) instead of typing them into a website, and use HIBP for email addresses. A 'not found' result is not proof that nothing leaked.
Setting up GitHub two-factor authentication (2FA): authenticator app, passkeys, recovery codes, and what to do if you lose your phone
A guide to setting up two-factor authentication (2FA) on GitHub and avoiding lockout. Since March 2023, GitHub has been requiring 2FA, group by group, for users who contribute code on GitHub.com; once selected, you get a 45-day enrollment period and a 7-day grace period, after which you cannot use GitHub.com until 2FA is on. GitHub Docs recommends a TOTP authenticator app as the primary method with a passkey or security key as backup (passkeys, security keys and GitHub Mobile can only be added after TOTP or SMS is set up). This site's take: the common 2FA failure on GitHub is not account takeover but locking yourself out, and GitHub Support cannot restore an account whose 2FA credentials and recovery methods are all lost. Save the 16 recovery codes in a password manager and register a second method on the same day. While you are there, move to expiring fine-grained tokens, prune authorized apps and SSH keys, and check push protection and Dependabot alerts.