Gmail access: check signed-in devices and linked apps separately

A phone you no longer use and an app you tried once need different checks. For Gmail users, Google's device list is only one place to look: linked apps can have their own permissions. A useful account review asks which sessions remain signed in, which apps have access, and how you would get back in if the usual route stopped working.

Google's 30 October reminder suggests reviewing devices, old app access and recovery details. This documented guide follows those existing controls, checked on 31 October; it is not a new security-feature launch. The aim is an understood set of permissions, rather than a promise that a quick check makes an account safe. Google's reminder

Start with the right account

Open your Google Account directly through your usual trusted route and confirm the account address before changing anything. If you keep separate personal, work and project inboxes, review them separately. PING suggests making a short list of access you still need, such as the current phone and an actively used mail tool. You do not need to share that list, passwords or recovery codes with anyone to use this guide.

Read sessions before assuming a device is unfamiliar

Google's help directs users to Security & sign-in, then Your devices and Manage all devices. It explains that one device can have several sessions, created through different browsers, apps or services. The displayed time can reflect background synchronisation, and a location can be nearby rather than exact. A repeated name or recent time therefore needs inspection; neither alone proves someone else used the inbox. Device and session help

For a device you no longer own or use, Google describes selecting it and signing out. Where the same device name has multiple sessions, its guidance says to sign out of all of them to ensure that device no longer has account access. If activity remains unfamiliar, follow the provider's account-security instructions instead of treating this checklist as a diagnosis.

Check what the app is allowed to do

Next, open the account's linked-app controls. Google's current help separates Sign in with Google from access to Google Account data. Under the latter, choose the app, open See details and review its access; a filter can narrow the list by Google product. For an inbox review, inspect the actual Gmail permission rather than assuming every listed app can read mail. Linked-app controls

Google says removing account-data access stops that access and may disable app features. Stopping Sign in with Google is a different control: it stops automatic sign-in and does not delete the app's data. Before removing a sign-in link you still rely on, PING suggests checking the service's own account-access instructions so that an access tidy-up does not leave you unsure how to enter it.

Removing access is not a data-deletion receipt

Google's data-sharing help says an app may copy information to its own servers and that retention follows the developer's policy. It also distinguishes the requested Google services from the actions an app can take with that data. Read the app's privacy and deletion instructions if you want existing copies removed; a changed permission is not proof that those copies have gone. Data-sharing limits

Finish with a route back in

Check that the recovery details offered for this account are current and reachable. Google's help recommends a recovery email different from the sign-in address and warns that options vary by region, account and device; work or school users may need their administrator. Recovery options

If you travel between Lagos and London or change mobile numbers, ask whether you can still reach the recovery address or phone you have listed. Those are planning questions, not a claim about country-specific options. Finish with known devices, understood app permissions and reachable recovery details. For more practical technology guides, explore PING's Gadgets desk.