First aid · free · no account

If your account is at risk

Pick what is happening. Each section starts with the one thing to do first. Every step is safe even if nothing turns out to be wrong, so do it now and check afterwards.

The same steps are inside the Buoy app under Settings, and open there with no connection.

  1. 1 · Sign-in requests you didn’t start
  2. 2 · A caller asks you to approve
  3. 3 · A device you don’t recognise
  4. 4 · Someone else is in your account
  5. 5 · Your phone is lost or stolen
  6. 6 · Tell someone
  7. For administrators

1 · Sign-in requests you didn’t start

Do this firstDeny it. In Buoy that is “It wasn’t me” (on Android’s request card, “Not me — deny”). Never approve just to make the requests stop.

  1. Repeated requests mean someone may know your password. Change it where you sign in.
  2. In Buoy, open “Where you’re signed in” and end any sign-in you don’t recognise.
  3. If you think someone already got in, go to section 4.

Buoy holds at most three open requests for you at a time, so a flood of them cannot pile up. A request you deny is recorded, and your organisation’s security team can see the pattern.

2 · A caller asks you to approve, or to read out a code

Do this firstHang up. Real support staff never ask you to approve a sign-in or read out a number or code.

  1. Deny any request that arrived while you were talking.
  2. If you shared your screen, stop sharing.
  3. Call your organisation back on a number you already know, not one the caller gave you.

On Android and iPhone, Buoy shows a warning on any sign-in request that arrives while you are on a call, and a stronger one when your screen is shared too.

3 · A device or security key you don’t recognise was added

Do this firstOn Buoy’s notice, tap “This wasn’t me — remove it”. That device stops approving sign-ins for you at once.

  1. The same notice appears when a PIN or fingerprint on one of your devices is changed. If you didn’t change it, remove that device the same way.
  2. Then follow section 4: whoever added the device may also be signed in.

4 · Someone else is in your account

Do this firstLock it down. In Buoy on Android, open Settings, then “Security & devices”, and tap “Someone else is in my account”. On iPhone it is under Identity, in “Where you’re signed in”. On a computer, press “Lock down” beside the account.

  1. Every web sign-in to your account ends, including the one you are using.
  2. Any waiting account-recovery request is refused, unused recovery links are cancelled, and account recovery pauses for 3 days, so nobody can take the account over that way.
  3. Your own devices still approve sign-ins, so you can sign straight back in.
  4. Lifting the lockdown early needs you to approve it on your device.

5 · Your phone is lost or stolen

Do this firstIf you have Buoy on another Android phone, open “Security & devices” and tap “Revoke” beside the lost one.

  1. Buoy on iPhone and on computers can remove only itself, not another device. Use an Android phone, or ask your organisation’s administrator.
  2. No other device? Ask for account recovery. Your organisation’s administrator checks it is you before approving it, and where there are two administrators, both must agree.
  3. You are told about the recovery request on your devices, and can say “This wasn’t me” if you did not ask.
  4. Also lock down the account (section 4) to end every web sign-in while you recover.

Buoy has no recovery codes. Adding a second device now, while you still have the first, is the quickest way back if you lose one.

6 · Tell someone

Do this firstTell your organisation’s IT or security team. They can see sign-ins and devices that you can’t.

  1. Lost money? In India, call the National Cybercrime Helpline on 1930 or report at cybercrime.gov.in. Elsewhere, contact your police fraud reporting line, and your bank at once.
  2. Keep the time things happened and anything the caller or message said. Buoy on Android can copy an incident summary for you from “Security & devices”.

For administrators: an administrator account may be compromised

Do this firstIn the Console, open People, find “Who is signed in” and press “Sign this person out everywhere” for each affected person, administrators first.

  1. There is no button that signs out a whole organisation at once. That is deliberate, so a mistake or an attacker cannot lock everyone out with one press.
  2. If your single sign-on provider may be compromised, “Pause” it on the single sign-on page. Everyone it signed in is signed out, and its settings are kept.
  3. Raise “The factor floor” and press “Set the floor”, so approvals need a stronger factor.
  4. Refuse any account-recovery request you did not expect.
  5. Signing people out works at once. Pausing a provider, changing the floor and deciding a recovery request each ask you to approve on your own device first.
This page gives general safety steps. It is not legal advice and does not change any agreement you have with us or with your organisation. How we handle personal data is in our privacy notice. · Check a link or message · Stop a report · Home