Collection

Keep access, data and permissions under your control

Protect important accounts, make recovery possible and share only the access a task needs.

Explore in any order.

What’s included

6 checklists · 2 concepts · 2 principles · 10 protocols · 4 questions

Narrow your search

24 ideas

Protocol

Replace password reuse with a protected manager

One leaked password should not become a tour of your digital life.

Read the idea
Checklist

Keep personal trivia out of a memorable password

Your favourite dog is a poor shared secret with your public profile.

Read the idea
Protocol

Add another sign-in check before the password is exposed

The best time to add the second check is before the first one leaks.

Read the idea
Concept

Use a passkey for its protection, not as a magic badge

The useful change is in the sign-in mechanism, not the new label.

Read the idea
Protocol

Store recovery codes where account lockout cannot hide them

A spare key inside the locked room has limited ambition.

Read the idea
Question

Which mailbox can reset the rest of your accounts?

Some inboxes hold more doors than messages.

Read the idea
Checklist

Recover account control beyond changing the password

Getting back in does not prove the other person is out.

Read the idea
Protocol

Inspect the rules an intruder may have left behind

The intruder can leave instructions even after losing the login.

Read the idea
Protocol

Check that the update was applied, not just announced

An update notification is a task, not a completed defence.

Read the idea
Question

Check remaining security support before buying the device

Working today and receiving fixes tomorrow are different specifications.

Read the idea
Checklist

Define the data the backup must rescue

A green tick can certify the wrong folder very efficiently.

Read the idea
Principle

Keep a backup outside the failure it is meant to survive

Two copies can still share one point of failure.

Read the idea
Protocol

Restore a sample before the original is gone

A backup becomes convincing when something comes back from it.

Read the idea
Protocol

Verify the request outside the message that created the urgency

The message should not be allowed to supply its own verification desk.

Read the idea
Principle

Keep the one-time code in the sign-in you initiated

One-time does not mean harmless to share once.

Read the idea
Protocol

Deny the sign-in prompt you did not request

The approve button is not a way to make an annoying notification stop safely.

Read the idea
Protocol

Do not let an alarming pop-up appoint its own technician

The warning and the proposed rescue may be the same trap.

Read the idea
Question

Does this app need that permission for this task?

The permission belongs to a capability, not to the friendliness of the icon.

Read the idea
Checklist

Read what the connected app can do, not just what it can see

Read access and delete access should not blur into the word connected.

Read the idea
Concept

Disconnecting an app does not retrieve every copy it received

Closing the tap does not empty the other bucket.

Read the idea
Protocol

Choose the audience before copying the sharing link

Knowing the URL is not the same as being an intended recipient.

Read the idea
Question

Does the reviewer need to edit the original?

A request for an opinion is not necessarily a request for ownership of the keyboard.

Read the idea
Checklist

Verify sign-in recovery before wiping the old phone

Your gallery can move while your account keys stay behind.

Read the idea
Checklist

Leave a shared device without leaving your account behind

Closing the page is not always the same as ending the access.

Read the idea