Security glossary
Plain-English definitions of important security and privacy terms.
A login code belongs in the sign-in page you opened yourself.
A code spoken in a room does not stay secret like a device PIN.
Account association and local data are two separate cleanup jobs.
A request for extra money is not automatically part of the original checkout.
The message is a claim; the account record is the first transaction check.
Removing a login key does not automatically undo everything a device saw.
Stopping one funding route may leave the service contract active.
The first disputes consent; the second disputes fulfillment.
A purchase is not a personal transfer just because a seller wants lower fees.
The request asks you to act; it does not prove funds have left.
A meeting URL and a software installer require different verification.
Revoking the URL cannot recall a file someone already saved.
Content control and audio control are separate meeting settings.
Being sent a link is not the same as satisfying an account rule.
A code permits an attempt; a host-controlled room screens admission.
Only one of these should remove a team calendar for everyone.
One handles an event; the other can affect future contact across Google.
An event flag works within its calendar's sharing rules.
Availability can be shared without exposing names, places and descriptions.
Automatic appearance is a policy choice, not proof an event is legitimate.