# Keep access, data and permissions under your control

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

Protect important accounts, make recovery possible and share only the access a task needs.
Collection kind: collection
Source: https://vedokrok.com/collections/keep-access-data-and-permissions-under-your-control
Version: 1.0.0

---

## Replace password reuse with a protected manager

ID: MHC-D-RESEARCH-0145 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/replace-password-reuse-with-a-protected-manager

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- Several important accounts share the same password or a predictable variation.

### Avoid when

- A manager is not protection against every device compromise. Follow organizational rules for work accounts and verify the software's legitimate source.

### Explanation

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

### Steps

1. Use a suitable protected password manager to create a distinct password for each account that still needs one.
2. Secure the manager's own access and recovery route before depending on it.

### Example

Changing only the website name inside a repeated password leaves a pattern. Independently generated credentials remove that particular connection.

### Check

Could exposure of one site's password still unlock another important account directly?

### Limits

- A manager is not protection against every device compromise. Follow organizational rules for work accounts and verify the software's legitimate source.

### Evidence and sources

- supports: A protected password manager can generate and retain unique passwords; credentials should not be saved on shared devices. — ncsc-password-managers. Claim basis: guidance. Claim limit: The manager and its recovery route also require protection.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Password managers; shared devices; protecting the manager"].
Source note: The article body reports an update on 21 May 2026; its older footer review date is not treated as the only freshness signal.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Password-manager uses; shared devices)
- ncsc-password-managers: Managing your passwords — https://www.ncsc.gov.uk/collection/top-tips-for-staying-secure-online/password-managers

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (useful_with): https://vedokrok.com/knowledge/keep-personal-trivia-out-of-a-memorable-password

---

## Keep personal trivia out of a memorable password

ID: MHC-D-RESEARCH-0146 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/keep-personal-trivia-out-of-a-memorable-password

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- You must remember a password that cannot simply be generated and stored for you.

### Avoid when

- Do not use an example printed in a guide as a real password. A supported passkey or protected manager may remove the need to invent one.

### Explanation

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

### Checklist

- Avoid names, dates, familiar quotations and patterns that someone could predict.
- Choose adequate length and unpredictability within the service's requirements, and keep the result unique.

### Example

A long phrase copied from a popular song may be memorable and still predictable. Length alone does not make a public phrase secret.

### Check

Is the credential independent of discoverable facts and familiar examples?

### Limits

- Do not use an example printed in a guide as a real password. A supported passkey or protected manager may remove the need to invent one.

### Evidence and sources

- supports: Memorable passwords should avoid predictable personal information and familiar patterns. — ncsc-memorable-passwords. Claim basis: guidance. Claim limit: Length and unpredictability matter; a published example is not a password to reuse.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Memorable passwords; avoiding predictable personal information"].
Source note: The draft does not claim every three-word phrase meets every service's requirements or threat model.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Creating a memorable password)
- ncsc-memorable-passwords: Three random words — https://www.ncsc.gov.uk/collection/top-tips-for-staying-secure-online/three-random-words

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z

---

## Add another sign-in check before the password is exposed

ID: MHC-D-RESEARCH-0147 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/add-another-sign-in-check-before-the-password-is-exposed

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- An important account relies only on a password.

### Avoid when

- Authentication methods differ; a text code is not equivalent to a phishing-resistant passkey. Do not disable workplace controls to simplify access.

### Explanation

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

### Steps

1. Review the account's supported security options and enable a suitable stronger sign-in method or second factor.
2. Prepare the legitimate recovery method at the same time so losing one device does not become your only exit.

### Example

An email account gains an additional sign-in check, while recovery details are verified rather than left attached to an abandoned phone number.

### Check

Does the account require more than possession of its reusable password, with a recovery route you understand?

### Limits

- Authentication methods differ; a text code is not equivalent to a phishing-resistant passkey. Do not disable workplace controls to simplify access.

### Evidence and sources

- supports: Two-factor authentication adds a check beyond a password, and verification codes should not be given to callers. — ftc-two-factor. Claim basis: guidance. Claim limit: Methods provide different protection; codes can still be phished.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Authentication methods; protecting verification codes"].
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Methods and code safety)
- ftc-two-factor: Use Two-Factor Authentication To Protect Your Accounts — https://consumer.ftc.gov/articles/use-two-factor-authentication-protect-your-accounts

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (useful_with): https://vedokrok.com/knowledge/use-a-passkey-for-its-protection-not-as-a-magic-badge

---

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

ID: MHC-D-RESEARCH-0148 · Version: 0.1.0 · Kind: concept
Source: https://vedokrok.com/knowledge/use-a-passkey-for-its-protection-not-as-a-magic-badge

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- A service offers passkey sign-in and you want to understand what changes.

### Avoid when

- Passkey storage and synchronization differ. Follow the provider's current instructions and protect devices and credential-manager access.

### Explanation

A passkey can replace a reusable typed password with phishing-resistant sign-in. Check where the credential is held, how you unlock it and what happens when a device is lost. Other recovery paths remain part of the account's security.

### Example

A passkey protects the normal sign-in, but an insecure recovery mailbox can still matter. Inspect the whole account rather than declaring it unhackable.

### Check

Can you explain the sign-in and recovery paths without relying on a guarantee?

### Limits

- Passkey storage and synchronization differ. Follow the provider's current instructions and protect devices and credential-manager access.

### Evidence and sources

- supports: Passkeys can provide phishing-resistant sign-in without a reusable typed password. — ncsc-passkeys. Claim basis: guidance. Claim limit: Device security, recovery and other account access routes still matter.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["What are passkeys?; How do passkeys work?; account protection"].
Source note: Current 2026 guidance was inspected. No speed statistic or claim that every passkey is synced, recoverable or immune to every attack is adopted.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Passkey explanation and protection)
- ncsc-passkeys: Passkeys — https://www.ncsc.gov.uk/passkeys

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z

---

## Store recovery codes where account lockout cannot hide them

ID: MHC-D-RESEARCH-0149 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/store-recovery-codes-where-account-lockout-cannot-hide-them

A spare key inside the locked room has limited ambition.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- An account provides backup codes for losing the normal sign-in method.

### Avoid when

- Treat codes as secrets; do not put them in a public repository or send them to a helper. Availability and rules vary by account.

### Explanation

A spare key inside the locked room has limited ambition.

### Steps

1. Create the supported recovery codes and store them securely where the same account failure will not make them inaccessible.
2. Keep track of replacement sets and used codes according to the provider's rules.

### Example

A Google account's new backup-code set invalidates the old one. Updating the secure record matters more than keeping two confidently labelled copies.

### Check

Could you retrieve a valid recovery method without first signing into the account it is meant to recover?

### Limits

- Treat codes as secrets; do not put them in a public repository or send them to a helper. Availability and rules vary by account.

### Evidence and sources

- supports: Google backup codes are single-use recovery alternatives, and generating a replacement set invalidates the previous set. — google-backup-codes. Claim basis: technical_definition. Claim limit: Availability differs by account configuration; treat codes as secrets.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Create and save backup codes; use a code; replacement sets"].
Source note: Account eligibility and recovery options vary; Google Advanced Protection is a stated exception.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Create, save and use backup codes)
- google-backup-codes: Sign in with backup codes — https://support.google.com/accounts/answer/1187538?hl=en

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (use_before): https://vedokrok.com/knowledge/verify-sign-in-recovery-before-wiping-the-old-phone

---

## Which mailbox can reset the rest of your accounts?

ID: MHC-D-RESEARCH-0150 · Version: 0.1.0 · Kind: question
Source: https://vedokrok.com/knowledge/which-mailbox-can-reset-the-rest-of-your-accounts

Some inboxes hold more doors than messages.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- You are deciding which accounts deserve security attention first.

### Avoid when

- Do not delete or abandon a recovery address before updating dependent services through their legitimate settings. Work-managed identities may need administrator involvement.

### Explanation

Some inboxes hold more doors than messages.

### Question

Which important services use this mailbox for password resets or recovery?

Is its sign-in and recovery protection appropriate for that wider role?

### Example

An old email account appears unimportant because you rarely read it, yet several valuable services still send their reset links there.

### Check

Have you assessed the mailbox's recovery role rather than only its message volume?

### Limits

- Do not delete or abandon a recovery address before updating dependent services through their legitimate settings. Work-managed identities may need administrator involvement.

### Evidence and sources

- supports: Email compromise can expose reset routes for other accounts; recovery includes sessions, recovery details and forwarding settings. — ftc-account-recovery. Claim basis: guidance. Claim limit: Provider-specific incident instructions and organizational security support may be needed.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["After taking back control; forwarding rules; importance of email"].
Source note: Page dated August 2023. The draft uses the recovery checklist, not a guarantee that password changes alone resolve compromise.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (After taking back control; importance of email)
- ftc-account-recovery: How To Recover Your Hacked Email or Social Media Account — https://consumer.ftc.gov/articles/how-recover-your-hacked-email-or-social-media-account

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (useful_with): https://vedokrok.com/knowledge/add-another-sign-in-check-before-the-password-is-exposed

---

## Recover account control beyond changing the password

ID: MHC-D-RESEARCH-0151 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/recover-account-control-beyond-changing-the-password

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- You have regained access after a suspected account takeover.

### Avoid when

- For work accounts or suspected malware, involve the responsible security team. Preserve needed incident evidence and avoid unverified recovery services.

### Explanation

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

### Checklist

- Follow the provider's recovery instructions using an appropriately trusted device.
- Replace compromised credentials, review active sessions and remove unauthorized access.
- Verify recovery details and additional authentication before considering control restored.

### Example

A password is changed, but an unfamiliar session remains active. The recovery task includes that access route rather than ending at the confirmation banner.

### Check

Have you checked the routes by which someone could remain signed in or regain access?

### Limits

- For work accounts or suspected malware, involve the responsible security team. Preserve needed incident evidence and avoid unverified recovery services.

### Evidence and sources

- supports: Email compromise can expose reset routes for other accounts; recovery includes sessions, recovery details and forwarding settings. — ftc-account-recovery. Claim basis: guidance. Claim limit: Provider-specific incident instructions and organizational security support may be needed.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["After taking back control; forwarding rules; importance of email"].
Source note: Page dated August 2023. The draft uses the recovery checklist, not a guarantee that password changes alone resolve compromise.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (After taking back control; importance of email)
- ftc-account-recovery: How To Recover Your Hacked Email or Social Media Account — https://consumer.ftc.gov/articles/how-recover-your-hacked-email-or-social-media-account

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (useful_with): https://vedokrok.com/knowledge/inspect-the-rules-an-intruder-may-have-left-behind

---

## Inspect the rules an intruder may have left behind

ID: MHC-D-RESEARCH-0152 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/inspect-the-rules-an-intruder-may-have-left-behind

The intruder can leave instructions even after losing the login.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- An email account has been recovered but its settings have not been reviewed.

### Avoid when

- Do not indiscriminately delete legitimate organizational rules. Ask the appropriate administrator when you cannot establish what belongs there.

### Explanation

The intruder can leave instructions even after losing the login.

### Steps

1. Review forwarding, filters, delegation and relevant account settings for changes you did not authorize.
2. Use the provider's recovery guidance to remove unauthorized rules and check affected sent or deleted messages.

### Example

An unfamiliar forwarding rule keeps copying future mail elsewhere. A new password does not explain or remove that rule by itself.

### Check

Does the account's behaviour match your intended configuration, not just your ability to sign in?

### Limits

- Do not indiscriminately delete legitimate organizational rules. Ask the appropriate administrator when you cannot establish what belongs there.

### Evidence and sources

- supports: Email compromise can expose reset routes for other accounts; recovery includes sessions, recovery details and forwarding settings. — ftc-account-recovery. Claim basis: guidance. Claim limit: Provider-specific incident instructions and organizational security support may be needed.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["After taking back control; forwarding rules; importance of email"].
Source note: Page dated August 2023. The draft uses the recovery checklist, not a guarantee that password changes alone resolve compromise.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (After taking back control; importance of email)
- ftc-account-recovery: How To Recover Your Hacked Email or Social Media Account — https://consumer.ftc.gov/articles/how-recover-your-hacked-email-or-social-media-account

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z

---

## Check that the update was applied, not just announced

ID: MHC-D-RESEARCH-0153 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/check-that-the-update-was-applied-not-just-announced

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- You repeatedly postpone a security update or trust a message that says one is available.

### Avoid when

- An alarming web page is not the device's updater. Back up as instructed and follow organizational change requirements for managed systems.

### Explanation

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

### Steps

1. Use the device or application's legitimate update settings and official instructions.
2. Complete the required process and confirm the resulting status; enable suitable automatic updates where available.

### Example

A downloaded update still awaits an installation step. The useful check is the installed status, not whether the download finished yesterday.

### Check

Can you verify the software's current update state through its own trusted controls?

### Limits

- An alarming web page is not the device's updater. Back up as instructed and follow organizational change requirements for managed systems.

### Evidence and sources

- supports: Security updates should be applied through appropriate official routes, and unsupported devices no longer receive the manufacturer's security fixes. — ncsc-software-updates. Claim basis: guidance. Claim limit: An update or current support status cannot guarantee the absence of every vulnerability.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Automatic updates; official manufacturer instructions; end of support"].
Source note: Model support must be checked at the purchase or use date; historical links are not a current compatibility list.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Updates and end of support)
- ncsc-software-updates: Install the latest software and app updates — https://www.ncsc.gov.uk/collection/top-tips-for-staying-secure-online/install-the-latest-software-and-app-updates

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (useful_with): https://vedokrok.com/knowledge/check-remaining-security-support-before-buying-the-device

---

## Check remaining security support before buying the device

ID: MHC-D-RESEARCH-0154 · Version: 0.1.0 · Kind: question
Source: https://vedokrok.com/knowledge/check-remaining-security-support-before-buying-the-device

Working today and receiving fixes tomorrow are different specifications.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- A cheap older device looks adequate because its hardware still works.

### Avoid when

- Support policies change, and the most expensive model is not automatically necessary. Verify current manufacturer information and the whole task's compatibility.

### Explanation

Working today and receiving fixes tomorrow are different specifications.

### Question

Does this exact model still receive security updates from its manufacturer?

How does the remaining support fit the intended use period and the sensitivity of the tasks?

### Example

A used phone has a bright screen and good battery life, but its support has ended. That limitation belongs in the purchase decision, not in a surprise after setup.

### Check

Is support status verified for the exact model rather than inferred from the brand?

### Limits

- Support policies change, and the most expensive model is not automatically necessary. Verify current manufacturer information and the whole task's compatibility.

### Evidence and sources

- supports: Security updates should be applied through appropriate official routes, and unsupported devices no longer receive the manufacturer's security fixes. — ncsc-software-updates. Claim basis: guidance. Claim limit: An update or current support status cannot guarantee the absence of every vulnerability.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Automatic updates; official manufacturer instructions; end of support"].
Source note: Model support must be checked at the purchase or use date; historical links are not a current compatibility list.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Updates and end of support)
- ncsc-software-updates: Install the latest software and app updates — https://www.ncsc.gov.uk/collection/top-tips-for-staying-secure-online/install-the-latest-software-and-app-updates

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z

---

## Define the data the backup must rescue

ID: MHC-D-RESEARCH-0155 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/define-the-data-the-backup-must-rescue

A green tick can certify the wrong folder very efficiently.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- A backup is running but nobody has checked whether the important files are included.

### Avoid when

- Do not copy confidential work data to unauthorized storage. Retention, encryption and access requirements remain part of the backup design.

### Explanation

A green tick can certify the wrong folder very efficiently.

### Checklist

- Identify the data needed to resume the important activities, including less obvious settings or exports where relevant.
- Check that the backup actually includes those locations and a sufficiently recent usable copy.

### Example

Documents are protected, but the local application's working database sits elsewhere. The backup job's success does not cover a location it never read.

### Check

Can you map each critical item to a real recoverable copy?

### Limits

- Do not copy confidential work data to unauthorized storage. Retention, encryption and access requirements remain part of the backup design.

### Evidence and sources

- supports: Backups should cover important data, be protected from the same failure and have a known restoration method. — ncsc-backups-2026. Claim basis: guidance. Claim limit: A small restoration check does not prove every file or disaster scenario is covered.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Data coverage; external storage; restoring backups"].
Source note: Reviewed 21 July 2026. A cloud folder is not automatically assumed to provide a particular retention or recovery guarantee.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Data coverage; external storage; restoring backups)
- ncsc-backups-2026: Small organisations guide to cyber security: Backing up your data — https://www.ncsc.gov.uk/collection/small-organisations-guide-to-cyber-security/backing-up-your-data

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (useful_with): https://vedokrok.com/knowledge/keep-a-backup-outside-the-failure-it-is-meant-to-survive

---

## Keep a backup outside the failure it is meant to survive

ID: MHC-D-RESEARCH-0156 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/keep-a-backup-outside-the-failure-it-is-meant-to-survive

Two copies can still share one point of failure.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- Every copy can be altered or lost through the same device or account.

### Avoid when

- Isolation must still allow a usable, maintained recovery process. Do not disable organizational backup systems or invent guarantees about a provider's retention.

### Explanation

Consider what could destroy or deny access to both copies. Protect backup access and, for ordinary external-drive backups, disconnect the device when it is not in use as appropriate. Check cloud retention and deletion behaviour rather than assuming synchronization is sufficient.

### Example

A permanently connected backup drive may be affected alongside an infected computer. Its different drive letter does not make it independent.

### Check

Which failure can the backup survive that the original cannot?

### Limits

- Isolation must still allow a usable, maintained recovery process. Do not disable organizational backup systems or invent guarantees about a provider's retention.

### Evidence and sources

- supports: Backups should cover important data, be protected from the same failure and have a known restoration method. — ncsc-backups-2026. Claim basis: guidance. Claim limit: A small restoration check does not prove every file or disaster scenario is covered.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Data coverage; external storage; restoring backups"].
Source note: Reviewed 21 July 2026. A cloud folder is not automatically assumed to provide a particular retention or recovery guarantee.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Data coverage; external storage; restoring backups)
- ncsc-backups-2026: Small organisations guide to cyber security: Backing up your data — https://www.ncsc.gov.uk/collection/small-organisations-guide-to-cyber-security/backing-up-your-data

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (useful_with): https://vedokrok.com/knowledge/restore-a-sample-before-the-original-is-gone

---

## Restore a sample before the original is gone

ID: MHC-D-RESEARCH-0157 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/restore-a-sample-before-the-original-is-gone

A backup becomes convincing when something comes back from it.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- You have never used the recovery procedure for a supposedly reliable backup.

### Avoid when

- A sample test is not a complete disaster-recovery certification. Avoid destructive restore options and involve the responsible team for production systems.

### Explanation

A backup becomes convincing when something comes back from it.

### Steps

1. Use the documented restoration process on a safe sample, restoring to a separate location where possible.
2. Open the result and check that the content and necessary access are usable without overwriting the working original.

### Example

A restored archive exists but cannot be opened because its key is unavailable. Discovering that during a harmless rehearsal is better than during a loss.

### Check

Did you recover usable information, not merely create another file with the right name?

### Limits

- A sample test is not a complete disaster-recovery certification. Avoid destructive restore options and involve the responsible team for production systems.

### Evidence and sources

- supports: Backups should cover important data, be protected from the same failure and have a known restoration method. — ncsc-backups-2026. Claim basis: guidance. Claim limit: A small restoration check does not prove every file or disaster scenario is covered.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Data coverage; external storage; restoring backups"].
Source note: Reviewed 21 July 2026. A cloud folder is not automatically assumed to provide a particular retention or recovery guarantee.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Data coverage; external storage; restoring backups)
- ncsc-backups-2026: Small organisations guide to cyber security: Backing up your data — https://www.ncsc.gov.uk/collection/small-organisations-guide-to-cyber-security/backing-up-your-data

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z

---

## Verify the request outside the message that created the urgency

ID: MHC-D-RESEARCH-0158 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/verify-the-request-outside-the-message-that-created-the-urgency

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- An unexpected message asks you to log in, pay or change sensitive information.

### Avoid when

- Good spelling, a logo or a familiar sender name is not sufficient authentication. For workplace messages, use the established reporting process.

### Explanation

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

### Steps

1. Pause the requested action and avoid using the message's link, attachment or supplied callback number.
2. Open a known legitimate service route or contact the organization through independently established details.

### Example

A bank-branded text asks for immediate account confirmation. Opening the bank's known app is a different verification path from following the text's link.

### Check

Did your verification rely on information independent of the suspicious request?

### Limits

- Good spelling, a logo or a familiar sender name is not sufficient authentication. For workplace messages, use the established reporting process.

### Evidence and sources

- supports: A suspicious message should be verified through a known independent contact route rather than its supplied link or number. — ftc-phishing. Claim basis: guidance. Claim limit: A polished message or familiar sender name does not establish authenticity.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Recognizing phishing; independent contact; responding to a suspicious message"].
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Responding to suspicious messages)
- ftc-phishing: How To Recognize and Avoid Phishing Scams — https://consumer.ftc.gov/articles/how-recognize-and-avoid-phishing-scams

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (useful_with): https://vedokrok.com/knowledge/do-not-let-an-alarming-pop-up-appoint-its-own-technician

---

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

ID: MHC-D-RESEARCH-0159 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/keep-the-one-time-code-in-the-sign-in-you-initiated

One-time does not mean harmless to share once.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- A caller or message asks you to read out a verification code.

### Avoid when

- Do not paste codes into a chatbot, shared document or public support thread. Contact the provider through a trusted route when uncertain.

### Explanation

A verification code can authorize access or a sensitive action. Do not hand it to someone claiming to be support. Use it only in the legitimate process you intentionally started, after checking what the code is for.

### Example

A caller says a code proves you own your account. It may instead let them complete a sign-in they initiated. Their explanation does not change the code's authority.

### Check

Do you know which action the code authorizes and who is actually performing it?

### Limits

- Do not paste codes into a chatbot, shared document or public support thread. Contact the provider through a trusted route when uncertain.

### Evidence and sources

- supports: Two-factor authentication adds a check beyond a password, and verification codes should not be given to callers. — ftc-two-factor. Claim basis: guidance. Claim limit: Methods provide different protection; codes can still be phished.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Authentication methods; protecting verification codes"].
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Methods and code safety)
- ftc-two-factor: Use Two-Factor Authentication To Protect Your Accounts — https://consumer.ftc.gov/articles/use-two-factor-authentication-protect-your-accounts

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (compare_with): https://vedokrok.com/knowledge/deny-the-sign-in-prompt-you-did-not-request

---

## Deny the sign-in prompt you did not request

ID: MHC-D-RESEARCH-0160 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/deny-the-sign-in-prompt-you-did-not-request

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- Your phone asks you to approve an account sign-in that you did not start.

### Avoid when

- Location displays can be approximate. Do not use proximity alone to approve a request, and do not follow a separate suspicious message to review the account.

### Explanation

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

### Steps

1. Deny an unexpected approval request rather than guessing that it belongs to something routine.
2. Review account activity through the legitimate settings and follow the provider's security instructions.

### Example

Several prompts arrive during dinner. Approving one to silence the sequence can authorize the very access the extra check was intended to block.

### Check

Can every approved prompt be tied to your own intended sign-in?

### Limits

- Location displays can be approximate. Do not use proximity alone to approve a request, and do not follow a separate suspicious message to review the account.

### Evidence and sources

- supports: An unexpected Google sign-in prompt should be denied and the account activity reviewed through its legitimate settings. — google-signin-prompts. Claim basis: guidance. Claim limit: A displayed location is approximate and should not be the only identity check.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Unexpected prompts; reviewing sign-in activity"].
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (You get a prompt but didn't sign in)
- google-signin-prompts: Sign in with Google prompts — https://support.google.com/accounts/answer/7026266?hl=en&ref_topic=7189145

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z

---

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

ID: MHC-D-RESEARCH-0161 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/do-not-let-an-alarming-pop-up-appoint-its-own-technician

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- A page or unexpected caller says your device is infected and requests remote access or payment.

### Avoid when

- Legitimate remote support should follow a verified authorized process. If access was already granted, seek trusted incident help rather than continuing with the same caller.

### Explanation

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

### Steps

1. Do not call the pop-up's number, install its tool or grant remote control in response to the warning.
2. Use your known device-support or workplace IT route to assess a genuine concern.

### Example

A browser page imitates a system warning and provides a support number. Its appearance does not make it the operating system or your employer's help desk.

### Check

Was the support relationship established independently of the alarming contact?

### Limits

- Legitimate remote support should follow a verified authorized process. If access was already granted, seek trusted incident help rather than continuing with the same caller.

### Evidence and sources

- supports: Unexpected support calls or alarming pop-ups can be used to obtain payment or remote access. — ftc-tech-support. Claim basis: guidance. Claim limit: Legitimate IT support exists; verify it through a previously trusted channel.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Pop-up warnings; unexpected contact; remote access requests"].
Source note: Initial retrieved article was inspected; later tool fetches failed. No claim of a successful second full-page verification is made.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Pop-up and remote-access warnings)
- ftc-tech-support: How To Recognize and Avoid Tech Support Scams — https://consumer.ftc.gov/articles/how-recognize-avoid-tech-support-scams

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z

---

## Does this app need that permission for this task?

ID: MHC-D-RESEARCH-0162 · Version: 0.1.0 · Kind: question
Source: https://vedokrok.com/knowledge/does-this-app-need-that-permission-for-this-task

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- An app requests access to location, contacts, files, camera or microphone.

### Avoid when

- Options differ by device and permission. Denying access can disable a feature; evaluate that tradeoff rather than granting everything or blindly blocking essential accessibility tools.

### Explanation

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

### Question

What requested function needs this access, and is the scope proportionate?

Is a narrower option, such as access only while using the app, available and sufficient?

### Example

A recording app needs the microphone for a recording task. That does not automatically explain why it also wants the entire contact list.

### Check

Can you connect each granted permission to an intended function?

### Limits

- Options differ by device and permission. Denying access can disable a feature; evaluate that tradeoff rather than granting everything or blindly blocking essential accessibility tools.

### Evidence and sources

- supports: Android permits reviewing app permissions, with narrower timing choices available for some permission types. — google-android-permissions. Claim basis: technical_definition. Claim limit: Controls differ between devices and versions, and denying access can affect the requested function.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Change permissions; permission types; while-using and ask options"].
Source note: Available options vary with permission type, device and Android version.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Change permissions; location, camera and microphone options)
- google-android-permissions: Change app permissions on your Android phone — https://support.google.com/android/answer/9431959?hl=en

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (compare_with): https://vedokrok.com/knowledge/read-what-the-connected-app-can-do-not-just-what-it-can-see

---

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

ID: MHC-D-RESEARCH-0163 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/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.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- You are linking a service to an account containing valuable or sensitive data.

### Avoid when

- A consent screen does not certify the developer's future behaviour. Follow organizational restrictions and do not connect confidential accounts to unapproved services.

### Explanation

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

### Checklist

- Identify the data categories and actions in the requested grant.
- Check the developer, intended task and handling policy before approving access.
- Prefer the narrow scope the task genuinely requires when that choice is available.

### Example

A tool meant to display appointments requests permission to modify unrelated files. The useful question is about that specific authority, not whether account linking is generally convenient.

### Check

Could you explain the approved actions in plain language before granting them?

### Limits

- A consent screen does not certify the developer's future behaviour. Follow organizational restrictions and do not connect confidential accounts to unapproved services.

### Evidence and sources

- supports: Linked-app grants identify data and actions available to the developer; previously copied data can remain under that developer's retention policy. — google-linked-app-data. Claim basis: technical_definition. Claim limit: The consent screen does not certify trustworthy handling after access is granted.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Access level; data retention; considerations before granting access"].
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Access level; data retention; deletion considerations)
- google-linked-app-data: How Google helps you share some of your account data with apps from other developers safely — https://support.google.com/accounts/answer/14013600

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (useful_with): https://vedokrok.com/knowledge/disconnecting-an-app-does-not-retrieve-every-copy-it-received

---

## Disconnecting an app does not retrieve every copy it received

ID: MHC-D-RESEARCH-0164 · Version: 0.1.0 · Kind: concept
Source: https://vedokrok.com/knowledge/disconnecting-an-app-does-not-retrieve-every-copy-it-received

Closing the tap does not empty the other bucket.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- You are disconnecting a linked app and need to know which access ends and which data remains.

### Avoid when

- Check the provider’s current controls and retention process. A removal confirmation is not proof of erasure or that every existing session ended; work accounts may need an administrator.

### Explanation

First identify the connection being removed. Google separates sign-in links, an app’s access to Google data, and an agent’s permission to use that app. Ending one is not a promise that all the others end. Removing a data-access grant stops that route; it does not retrieve copies already held by the developer. Account closure and data deletion need their own checks.

### Example

You stop a Google agent from using a linked planning app. The app’s account connection remains; inspect its data-access grant separately before calling it disconnected.

### Check

Can you name the access you ended, any links still present, and what must happen to the developer’s existing copies?

### Limits

- Check the provider’s current controls and retention process. A removal confirmation is not proof of erasure or that every existing session ended; work accounts may need an administrator.

### Evidence and sources

- supports: Linked-app grants identify data and actions available to the developer; previously copied data can remain under that developer's retention policy. — google-linked-app-data. Claim basis: technical_definition. Claim limit: The consent screen does not certify trustworthy handling after access is granted.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Access level; data retention; considerations before granting access"].
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Access level; data retention; deletion considerations)
- supports: Google manages sign-in links, app data-access grants and agent permissions separately. Stopping an agent does not remove the app’s account link; removing a sign-in link does not delete the app’s stored data. — google-linked-app-management. Claim basis: technical_definition. Claim limit: Each control affects its stated connection. This documentation does not establish closure of every existing app session or deletion of previously copied data.
Source access: selected_html_passages; accessed on: 2026-10-03; inspected sections: ["Sign in with Google", "Share access to your Google Account with an app from a developer other than Google", "Gemini and agent permissions"].
Source note: Selected official HTML sections read on 3 October 2026. This records current documented distinctions, not a verified feature-introduction date or a hands-on account test. The earlier source record remains in Git history.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Manage linked apps: Sign in with Google; Share access to your Google Account; Gemini and agent permissions)
- google-linked-app-data: How Google helps you share some of your account data with apps from other developers safely — https://support.google.com/accounts/answer/14013600
- google-linked-app-management: Manage links between your Google Account and apps from other developers — https://support.google.com/accounts/answer/13533235?hl=en

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z

---

## Choose the audience before copying the sharing link

ID: MHC-D-RESEARCH-0165 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/choose-the-audience-before-copying-the-sharing-link

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- A document is meant for a few people but its link may allow a much wider audience.

### Avoid when

- Drive folder owners and shared-drive managers retain access to limited-access folders. Authorized viewers may still reproduce information; do not treat a restricted audience as an erasure tool.

### Explanation

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

### Steps

1. Choose the intended audience before sending a file; inspect named people, groups, general link access and access inherited from its folder.
2. In Google Drive, a narrower audience inside a shared folder may need a limited-access subfolder. Ask the owner or responsible manager before changing the shared structure.
3. After a change, check every remaining route. A removal entry does not cancel access still supplied by a group or a general link.

### Example

A reviewer appears under Access removed for a Drive folder but still belongs to a group that can open it. Removing the individual entry did not remove the group route.

### Check

Can each person who should lose access still reach the file through a group, link or inherited grant?

### Limits

- Drive folder owners and shared-drive managers retain access to limited-access folders. Authorized viewers may still reproduce information; do not treat a restricted audience as an erasure tool.

### Evidence and sources

- supports: Google Drive distinguishes the sharing audience from viewer, commenter and editor permissions. — google-drive-sharing. Claim basis: technical_definition. Claim limit: Access controls cannot guarantee recipients will not reproduce information by other means.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Restricted and anyone-with-link access; viewer, commenter and editor roles"].
Source note: Organization policies can restrict sharing. Expiration and other advanced controls are not assumed available on every account.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (General access and role selection)
- supports: In Google Drive, a file cannot assign less access than a person inherits from its parent folder. A limited-access folder is a documented way to narrow access within that structure. — google-drive-folder-inheritance. Claim basis: technical_definition. Claim limit: Changing a parent folder can affect other contents. Follow the owner’s approved arrangement; the card does not authorize changing collaborators’ access.
Source access: selected_html_passages; accessed on: 2026-10-03; inspected sections: ["More about folder sharing", "Reduce or remove folder permissions", "Reduce permissions for a specific file in a shared folder"].
Source note: Selected computer-help sections establish inheritance and scoped alternatives. No account operation, rollout-date finding or guarantee about every organization configuration is claimed.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Reduce permissions for a specific file in a shared folder)
- limits: Google Drive limited-access removal entries do not override remaining group or general access. Folder owners in My Drive and shared-drive managers retain access. — google-drive-limited-access. Claim basis: technical_definition. Claim limit: Limited access is not a guarantee of secrecy from owners, managers or recipients who already copied the information.
Source access: selected_html_passages; accessed on: 2026-10-03; inspected sections: ["Create or edit limited access to a folder", "Learn who can manage limited access folders", "Manage people removed by limited access", "Which items can have limited access?"].
Source note: Inspected explicit group/general-access exceptions, owner/manager access and folder-only manual control. Feature availability and administrative policy still need checking in the actual account.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Manage people removed by limited access; Learn who can find & access folders with limited access)
- google-drive-sharing: Share files from Google Drive — https://support.google.com/drive/answer/2494822?hl=en
- google-drive-folder-inheritance: Share folders in Google Drive — https://support.google.com/drive/answer/7166529
- google-drive-limited-access: Learn about limited access to files and folders in Google Drive — https://support.google.com/drive/answer/14254362

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (useful_with): https://vedokrok.com/knowledge/does-the-reviewer-need-to-edit-the-original

---

## Does the reviewer need to edit the original?

ID: MHC-D-RESEARCH-0166 · Version: 0.1.0 · Kind: question
Source: https://vedokrok.com/knowledge/does-the-reviewer-need-to-edit-the-original

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- Everyone invited to view a file receives editing authority by default.

### Avoid when

- Do not lower a whole team’s folder access just to restrict one file. Ask its owner to choose the right scope; a non-editing role does not prevent every form of copying.

### Explanation

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

### Question

Does this person need to read, comment or change the source directly?

Do they already inherit a higher role from a parent folder? In Google Drive, a lower file-level role does not override that access.

Can the owner provide the intended role without disrupting other collaborators, for example through a suitable limited-access folder?

### Example

A proposal is marked Commenter for a client who is already an Editor of its parent folder. That file-level choice does not make the original read-only for them.

### Check

Does the person’s effective role match the intended contribution, including inherited access?

### Limits

- Do not lower a whole team’s folder access just to restrict one file. Ask its owner to choose the right scope; a non-editing role does not prevent every form of copying.

### Evidence and sources

- supports: Google Drive distinguishes the sharing audience from viewer, commenter and editor permissions. — google-drive-sharing. Claim basis: technical_definition. Claim limit: Access controls cannot guarantee recipients will not reproduce information by other means.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Restricted and anyone-with-link access; viewer, commenter and editor roles"].
Source note: Organization policies can restrict sharing. Expiration and other advanced controls are not assumed available on every account.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (General access and role selection)
- supports: In Google Drive, a file cannot assign less access than a person inherits from its parent folder. A limited-access folder is a documented way to narrow access within that structure. — google-drive-folder-inheritance. Claim basis: technical_definition. Claim limit: Changing a parent folder can affect other contents. Follow the owner’s approved arrangement; the card does not authorize changing collaborators’ access.
Source access: selected_html_passages; accessed on: 2026-10-03; inspected sections: ["More about folder sharing", "Reduce or remove folder permissions", "Reduce permissions for a specific file in a shared folder"].
Source note: Selected computer-help sections establish inheritance and scoped alternatives. No account operation, rollout-date finding or guarantee about every organization configuration is claimed.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Reduce permissions for a specific file in a shared folder)
- google-drive-sharing: Share files from Google Drive — https://support.google.com/drive/answer/2494822?hl=en
- google-drive-folder-inheritance: Share folders in Google Drive — https://support.google.com/drive/answer/7166529

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z

---

## Verify sign-in recovery before wiping the old phone

ID: MHC-D-RESEARCH-0167 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/verify-sign-in-recovery-before-wiping-the-old-phone

Your gallery can move while your account keys stay behind.

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- A device migration appears complete because photos and messages arrived on the replacement.

### Avoid when

- Do not expose transfer QR codes or recovery secrets in screenshots or chat. Work-managed accounts may require administrator-assisted migration.

### Explanation

Your gallery can move while your account keys stay behind.

### Checklist

- Identify the authenticator, passkey and recovery methods that depend on the old device.
- Follow their actual transfer or synchronization instructions and verify a safe sign-in on the new arrangement.
- Keep a legitimate recovery route before erasing or relinquishing the old device.

### Example

An authenticator used without account synchronization may require an explicit transfer. Assuming it followed the photo backup can create an avoidable lockout.

### Check

Can the important accounts be accessed without relying on the device about to be erased?

### Limits

- Do not expose transfer QR codes or recovery secrets in screenshots or chat. Work-managed accounts may require administrator-assisted migration.

### Evidence and sources

- supports: Google Authenticator supports account-based synchronization or an explicit transfer process depending on its configuration. — google-authenticator-transfer. Claim basis: technical_definition. Claim limit: Do not assume codes moved merely because other phone data did.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Transfer Authenticator codes; account synchronization and manual transfer"].
Source note: The transfer prompt is an original safety check, not an assumption that every authenticator uses Google's synchronization model.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Transfer Authenticator codes)
- supports: Google backup codes are single-use recovery alternatives, and generating a replacement set invalidates the previous set. — google-backup-codes. Claim basis: technical_definition. Claim limit: Availability differs by account configuration; treat codes as secrets.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Create and save backup codes; use a code; replacement sets"].
Source note: Account eligibility and recovery options vary; Google Advanced Protection is a stated exception.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Create, save and use backup codes)
- google-authenticator-transfer: Get verification codes with Google Authenticator — https://support.google.com/accounts/answer/1066447
- google-backup-codes: Sign in with backup codes — https://support.google.com/accounts/answer/1187538?hl=en

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z

---

## Leave a shared device without leaving your account behind

ID: MHC-D-RESEARCH-0168 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/leave-a-shared-device-without-leaving-your-account-behind

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

Knowledge source release: MHC-RPUB-20261113-0d6697fd
Source corpus commit: 0d6697fd15f7fb670cfa465c54a411e91752cae4
Source manifest SHA-256: 038080ffd768d7c1ae21ae65ea2a3b8e36664c28df759e06d19f63f6e059bf29
Source projection SHA-256: 489520d20496b8e53d4bcf37ddaae13d1b66f4405e33ae1666ce681073b24c78

### Use when

- You use a borrowed or public computer for an account task.

### Avoid when

- Private browsing does not make an untrusted device safe from monitoring or malware. Do not use it as a substitute for a trusted environment.

### Explanation

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

### Checklist

- Avoid saving passwords or enrolling the shared device as a trusted personal sign-in method.
- Sign out of the service and end the temporary browsing session when finished.
- Use a trusted personal device instead for especially sensitive tasks where possible.

### Example

A browser offers to remember a password on a shared workstation. Declining avoids turning the next user's convenience into access to your account.

### Check

Have you ended the account session without leaving saved credentials or a new trusted-device route?

### Limits

- Private browsing does not make an untrusted device safe from monitoring or malware. Do not use it as a substitute for a trusted environment.

### Evidence and sources

- supports: A protected password manager can generate and retain unique passwords; credentials should not be saved on shared devices. — ncsc-password-managers. Claim basis: guidance. Claim limit: The manager and its recovery route also require protection.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Password managers; shared devices; protecting the manager"].
Source note: The article body reports an update on 21 May 2026; its older footer review date is not treated as the only freshness signal.
Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review. (Password-manager uses; shared devices)
- ncsc-password-managers: Managing your passwords — https://www.ncsc.gov.uk/collection/top-tips-for-staying-secure-online/password-managers

Review: agent · Agent editorial and scoped source review · 2026-11-13T05:54:13Z
Published: 2026-11-13T05:54:13Z
Related (useful_with): https://vedokrok.com/knowledge/replace-password-reuse-with-a-protected-manager
